Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve user ergonomics of brew link --overwrite help #16645

Merged
merged 1 commit into from
Feb 12, 2024

Commits on Feb 12, 2024

  1. Improve user ergonomics of brew link --overwrite help

    When a Keg is unlinked, brew-link gives a helpful message for how to proceed: adding the `--overwrite` flag.
    
    For safety, it also recommends running in `--dry-run` mode first to see what would be deleted.
    
    So a user's common flow would be:
    
    1. run `brew link foo`
    2. get error message with guidance
    3. run `brew link --overwrite --dry-run foo`
    4. inspect
    5. run `brew link --overwrite foo`
    
    In this flow, steps 3-5 are likely very common. Common enough that a user may use their shell history to re-populate their prompt with step 3's command, delete the `--dry-run` flag, and re-run. (The end goal, of course, is to link `foo`.)
    
    The `--dry-run` flag needs to be removed from the command, of course. If it had been at the _end_ of the command, it would make the subsequent  modification easier.
    
    Instead of "up arrow, left-arrow a bunch, then backspace over --dry-run, hopefully not backspacing over the formula name", it would be easier for the user if the dry-run flag were already at the end of the command. Then the user can "up arrow, backspace a few times and hit enter".
    
    What's more, if the last arg were `--dry-run`, a more advanced bash user could even use `!:-` to re-run the link command with all-but-the-last-arg.
    jasonkarns committed Feb 12, 2024
    Configuration menu
    Copy the full SHA
    79a8279 View commit details
    Browse the repository at this point in the history