I just did: echo 'some handy function definition' > ~/.config/fish/config.fish
Was in a hurry and didn't noticed the '>' instead of '>>', result: config gone! 2 questions and 1 possible request: Q1. Is there a way to recover my configuration by perusing the actual environment? I have several terms opened and machine wont go off (I hope). Already recovered my functions by doing a: functions -a > fish.functions.all.bak But I don't know an easy way to recover environment variables without going one by one. I listed the __fish_complete functions, but I were unable to find the one the completes a '$<TAB>' keystroke. If I could find a way to get all environment variable names I could save them all. Q2. Is there some way to emulate this from bash: set -o noclobber that set disables '>' to overwrite existing files (and you can bypass it also, so is pretty useful) Possible Request: if there's no way to achieve Q2, what about including it in the next fish release? I think that set is in the spirit of fish. -- Fernando Canizo - http://muriandre.homelinux.org/~conan/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users
