-
-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to define the default settings #100
Comments
Detail view:
-d, --det <DETAILS>
the data points to show about each node
[default: none]
Possible values:
- dev
- ino
- nlink
- typ
- perm
- oct
- user
- uid
- group
- gid
- size
- blocks
- btime: created at
- ctime: changed at
- mtime: modified at
- atime: accessed at
- git
- none
- std
- all
-H, --header <HEADER>
show headers above columnar data
[default: true]
[possible values: true, false]
-u, --unit <UNIT>
the type of units to use for the node sizes
[default: binary]
[possible values: binary, decimal, none]
Grid view:
-g, --grid <GRID>
display node names in multiple columns
[default: false]
[possible values: true, false]
-D, --down <DOWN>
display node names column-first
[default: false]
[possible values: true, false]
Presentation:
-i, --icon <ICON>
display icons next to node names
[default: true]
[possible values: true, false]
-S, --suffix <SUFFIX>
display node type suffixes after the node name
[default: true]
[possible values: true, false]
-l, --sym <SYM>
show symlink targets
[default: true]
[possible values: true, false]
-c, --collapse <COLLAPSE>
show dependent nodes as children of their principal nodes
[default: true]
[possible values: true, false]
-a, --align <ALIGN>
align items accounting for leading dots
[default: true]
[possible values: true, false] I would expect to be able to change the default value via the configuration for any of these settings. |
I mean I want file to be reported as grid via the configuration, unless I use |
That is a shortcoming in the documentation, and I should've been more clear about this but the idea is to definitely use aliases more. For example if you prefer grids, you can alias What are your thoughts on implementing a config file like |
I find this strange. There are two main reasons:
I mean if someone want to use your tool, hr would expect to be able to change what you mention as being the default value via something else than the command line arguments. If you had no configuration, I would have said, ok an alias maybe. |
Many tools support this, yes. Some others remove the training But I would find strange you implement something like this while you already have a pls.yml config file. Or maybe I misunderstood what you where suggesting. |
The issue here is that |
Oh I didn't get that, it's clearer But at same time, I hope you understand the problem I raised. There is a config file, and there is no way to say I want to display a grid and disable icons by default. |
So except something like PLS_DEFAULTS="--grid true --icons false" I don't see a solution |
I see the value in your proposal so I'm going to triage this issue and think about an elegant solution. If you have recommendations, please post them here. In the meantime, please use aliases as a workaround for now. |
Problem
I looked at the documentation, I thought I would be able to configure the way pls would be displayed without passing some options on CLI each time.
I thought it would be documented here https://pls.cli.rs/reference/conf/#app_const
Description
I found a lot of examples on how to customize the rendering of something, but not about setting via the configuration file the value that are described on this page
Did I miss something ?
Alternatives
create an alias to launch pls=pls --grid true
Additional information
The text was updated successfully, but these errors were encountered: