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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

short option name for read --shell conflicts with planned --silent #2166

Closed
zanchey opened this issue Jul 3, 2015 · 4 comments
Closed

short option name for read --shell conflicts with planned --silent #2166

zanchey opened this issue Jul 3, 2015 · 4 comments

Comments

@zanchey
Copy link
Member

zanchey commented Jul 3, 2015

Apropos of #838, I think the short name for read --shell to should be something that isn't -s, and I think this change should be made before 2.2.0 to avoid backward-incompatible change in the future. read -s is a reasonably common construct from other shells and a conflict is not helpful to migrants.

How about read -S?

@zanchey zanchey added this to the fish 2.2.0 milestone Jul 3, 2015
@zanchey zanchey added the invalid label Jul 3, 2015
@zanchey zanchey removed this from the fish 2.2.0 milestone Jul 3, 2015
@zanchey
Copy link
Member Author

zanchey commented Jul 3, 2015

Why did I think --shell wasn't released yet? It's been in fish for forever.

@zanchey zanchey closed this as completed Jul 3, 2015
@cben
Copy link
Contributor

cben commented Feb 12, 2016

I presume this is closed because we can't break backward compatibility?

For the record, another read option that'd be nice if it were bash-compatible is -p.
It's named exactly the same, but unlike bash where it takes a string, in fish it executes it as a command.
It's also confusing the long form is called --prompt; it should have been --prompt-cmd or --prompt-command. Then there could also be a separate -p, --prompt which takes a string (I dare say --prompt-cmd behavior is esoteric enough to not deserve a short form).

The thing with bash's read is that it has only short options. If bash had cmd --some-opt and fish had cmd --another-opt, that's great; when both have cmd -o but behave differently, that's confusing.

@ghost
Copy link

ghost commented Feb 12, 2016

@cben https://github.com/fisherman/get

get

get

get

get

@Pysis868
Copy link

GitHub - fish-shell/fish-shell - fish 2.6.0 (released June 3, 2017):

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants