Timeline for What is the [history-expansion] tag for, and does it add any value?
Current License: CC BY-SA 4.0
19 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 20, 2019 at 2:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jun 22, 2019 at 2:00 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jun 4, 2019 at 21:00 | history | tweeted | twitter.com/StackUnix/status/1136014985589592064 | ||
| May 23, 2019 at 1:03 | history | edited | Braiam | CC BY-SA 4.0 |
edited title
|
| May 14, 2019 at 15:03 | comment | added | Philippos |
I agree with @StephenKitt: Typically, bash users get strange error messages due to the broken implementation and will never guess that history expansion is the reason
|
|
| May 10, 2019 at 16:46 | answer | added | 0xSheepdog | timeline score: 1 | |
| May 10, 2019 at 8:58 | comment | added | Kusalananda Mod | @mosvy Well, I would call event designators "shortcuts" as they are used to avoid typing a full command (or part of a longer command). | |
| May 10, 2019 at 8:21 | comment | added | user313992 |
@StephenKitt I suggest that the tag name should be changed to modifier-failed in order to be sure that nobody is using it by mistake ;-)
|
|
| May 10, 2019 at 7:58 | comment | added | Stephen Kitt | This seems to be one of those tags which only make sense if you already know the answer (as in, if the question author knows it’s called “history expansion”, they’d probably be able to answer their question; and by extension, editors shouldn’t add that tag to the question), or for questions about esoteric aspects of history expansion... | |
| May 10, 2019 at 6:55 | comment | added | user313992 |
+ a form of command expansion also starts by ^, and both ! and ^ are also configurable in csh. sorry.
|
|
| May 10, 2019 at 6:39 | comment | added | user313992 |
@Kusalananda No, "history expansion/substitution" is not about "shortcuts for recalling specific commands". As explained in the bash, zsh and csh manpages, it specifically refers to a specific shell syntax where ! (which could be changed to another character in bash or zsh) is interpreted in a special way (being replaced with whole or parts of previous commands). It's not about interactive shortcuts like Ctrl-P, Ctrl-N Ctrl-R in bash (when in emacs editing mode).
|
|
| May 10, 2019 at 1:45 | comment | added | slm Mod | I like the existence of this tag. I suspect this tag could be applied to many more questions, currently there's only 37. I would create a explanation stating that the use of this tag is for question that cover the expansion of history commands that is a feature provided by many shells. | |
| May 9, 2019 at 23:27 | history | edited | Jeff SchallerMod |
edited tags
|
|
| May 9, 2019 at 22:32 | comment | added | 0xSheepdog | @Kusalananda that is what meta is for I suppose. :) | |
| May 9, 2019 at 21:00 | comment | added | Kusalananda Mod | I think it's a bit pedantic, yes. We also have brace-expansion (brace-expansion works differently in different shells), and variable-substitution (again, different in different shells). On the other hand, we have the very specific bash-expansion for whatever reason. Command history is something (relatively) completely different. Command history questions generally deals with the history as a whole, e.g. saving it, viewing it etc., while history expansion are more about how to interactively work with shortcuts for recalling specific commands. | |
| May 9, 2019 at 20:38 | comment | added | Jeff Schaller Mod | Of course I find it after commenting: unix.meta.stackexchange.com/a/1234/117549 | |
| May 9, 2019 at 20:36 | comment | added | Jeff Schaller Mod | I'm failing to find the previous discussion I'm thinking of, it my opinion at this point is to consider whether we'd have a set of history-expansion experts that are distinct from $SHELL experts who would follow the tag. I'm not sure it's worthwhile. I would recommend $SHELL + command-history. | |
| May 9, 2019 at 18:26 | comment | added | 0xSheepdog | Or, maybe I'm just too pedantic today? ;) | |
| May 9, 2019 at 18:26 | history | asked | 0xSheepdog | CC BY-SA 4.0 |