S
Simon Arame
Guest
I stumbled upon the worst line i've ever type:
Should'nt there be some kind of protection for that file not to be confused with .bashrc ?
by chance, i quickly hit Ctrl-C and verify i had not break anything.
Any historical command that points by full path is going to hit when such an auto-completion accident happens.
Maybe just adding a warning:
The feature request process for linux is going to take years !
I just hope the legal aspect was less complex for committers in the "gnu's not Unix" community.
Code:
[simon@localhost]> . .bash_history
by chance, i quickly hit Ctrl-C and verify i had not break anything.
Any historical command that points by full path is going to hit when such an auto-completion accident happens.
Maybe just adding a warning:
Code:
[simon@localhost]> . .bash_history
You enter the re-execution of the bash command history,
This born again shell history.
Are you sure that this is what you want to do ? [y/N]
The feature request process for linux is going to take years !
I just hope the legal aspect was less complex for committers in the "gnu's not Unix" community.