bootandy/archived-dust
1
0
Fork 0
mirror of https://github.com/bootandy/dust.git synced 2026-06-08 11:29:05 +03:00
Code Issues 21 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #168] Is it possible to configure this globally? #75

New Issue
Closed
opened 2026-06-08 11:25:34 +03:00 by zhus · 9 comments
zhus commented 2026-06-08 11:25:34 +03:00
Owner
Copy Link
Copy Source

Originally created by @IceSentry on GitHub (Aug 5, 2021).
Original GitHub issue: https://github.com/bootandy/dust/issues/168

I want to be have the reverse option on by default and I'd rather not have to remember to type -r every time.

Originally created by @IceSentry on GitHub (Aug 5, 2021). Original GitHub issue: https://github.com/bootandy/dust/issues/168 I want to be have the reverse option on by default and I'd rather not have to remember to type `-r` every time.
zhus closed this issue 2026-06-08 11:25:34 +03:00
zhus commented 2026-06-08 11:25:34 +03:00
Author
Owner
Copy Link
Copy Source

@bootandy commented on GitHub (Aug 6, 2021):

how would that work? Are you thinking of an environment variable ?

<!-- gh-comment-id:894108488 --> @bootandy commented on GitHub (Aug 6, 2021): how would that work? Are you thinking of an environment variable ?
zhus commented 2026-06-08 11:25:34 +03:00
Author
Owner
Copy Link
Copy Source

@IceSentry commented on GitHub (Aug 6, 2021):

Could be an env var, but a lot of cli tools have a config file that it then looks for at a few location.

A few examples:
https://github.com/Peltoche/lsd#configuration
https://starship.rs/config/
https://github.com/dalance/procs#configuration
https://github.com/XAMPPRocky/tokei#configuration
https://clementtsang.github.io/bottom/nightly/configuration/config-file/default-config/

<!-- gh-comment-id:894359700 --> @IceSentry commented on GitHub (Aug 6, 2021): Could be an env var, but a lot of cli tools have a config file that it then looks for at a few location. A few examples: https://github.com/Peltoche/lsd#configuration https://starship.rs/config/ https://github.com/dalance/procs#configuration https://github.com/XAMPPRocky/tokei#configuration https://clementtsang.github.io/bottom/nightly/configuration/config-file/default-config/
zhus commented 2026-06-08 11:25:34 +03:00
Author
Owner
Copy Link
Copy Source

@bootandy commented on GitHub (Aug 11, 2021):

thanks, I'll look into this.

<!-- gh-comment-id:896863949 --> @bootandy commented on GitHub (Aug 11, 2021): thanks, I'll look into this.
zhus commented 2026-06-08 11:25:34 +03:00
Author
Owner
Copy Link
Copy Source

@xenoterracide commented on GitHub (Oct 21, 2021):

alias dust="dust -r" and you could then use \dust to not use it, for posix shell only

<!-- gh-comment-id:948702574 --> @xenoterracide commented on GitHub (Oct 21, 2021): `alias dust="dust -r"` and you could then use `\dust` to not use it, for posix shell only
zhus commented 2026-06-08 11:25:34 +03:00
Author
Owner
Copy Link
Copy Source

@IceSentry commented on GitHub (Oct 21, 2021):

I'm on windows, alias are a fine workaround if you can use them easily, but having a global configuration can be much easier to read than a shell command with a bunch of flags and no comments.

<!-- gh-comment-id:948720871 --> @IceSentry commented on GitHub (Oct 21, 2021): I'm on windows, alias are a fine workaround if you can use them easily, but having a global configuration can be much easier to read than a shell command with a bunch of flags and no comments.
zhus commented 2026-06-08 11:25:34 +03:00
Author
Owner
Copy Link
Copy Source

@xenoterracide commented on GitHub (Oct 22, 2021):

I mean with Shell you can have global configurations... Unless you're trying to switch between batch, power shell and a posix shell. And obviously shell scripts, at least posix shell scripts, can have comments, also in shell scripts long options are generally preferred for readability and maintenance.

That said I'm not against a config file but for this particular scenario it doesn't seem like It's necessary in my mind. I noticed this when I opened an issue asking for an ignore config file, since an ignore file could be account global or directory local.

<!-- gh-comment-id:949084930 --> @xenoterracide commented on GitHub (Oct 22, 2021): I mean with Shell you can have global configurations... Unless you're trying to switch between batch, power shell and a posix shell. And obviously shell scripts, at least posix shell scripts, can have comments, also in shell scripts long options are generally preferred for readability and maintenance. That said I'm not against a config file but for this particular scenario it doesn't seem like It's necessary in my mind. I noticed this when I opened an issue asking for an ignore config file, since an ignore file could be account global or directory local.
zhus commented 2026-06-08 11:25:34 +03:00
Author
Owner
Copy Link
Copy Source

@IzhakJakov commented on GitHub (Mar 14, 2022):

I would love to see this happen as well
Please make it in $XDG_CONFIG_HOME by default 😊

https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html

<!-- gh-comment-id:1066883311 --> @IzhakJakov commented on GitHub (Mar 14, 2022): I would love to see this happen as well Please make it in `$XDG_CONFIG_HOME` by default 😊 <sup>https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html</sup>
zhus commented 2026-06-08 11:25:34 +03:00
Author
Owner
Copy Link
Copy Source

@bootandy commented on GitHub (Aug 19, 2022):

Can I get some feedback on if this is a sensible way to add config file support?

https://github.com/bootandy/dust/pull/243

thanks,

<!-- gh-comment-id:1220646968 --> @bootandy commented on GitHub (Aug 19, 2022): Can I get some feedback on if this is a sensible way to add config file support? https://github.com/bootandy/dust/pull/243 thanks,
zhus commented 2026-06-08 11:25:34 +03:00
Author
Owner
Copy Link
Copy Source

@bootandy commented on GitHub (Aug 23, 2022):

Added code to do this, will go out in the next release.

<!-- gh-comment-id:1223764628 --> @bootandy commented on GitHub (Aug 23, 2022): Added code to do this, will go out in the next release.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
good first issue
help wanted
pull-request
Mirrored from GitHub Pull Request
 windows help wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
zhus (Sergey Zhukov)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bootandy/archived-dust#75
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?