New answers tagged

0

This is how its done in .inputrc: set editing-mode vi $if mode=vi # these are for vi-command mode set keymap vi-command # unbind space " ": "" # bind space-a, space-; " a":beginning-of-line " ;":"$" $endif


0

Have you tried to hashbang the script_X with the path of the right interpreter(wrapper_script). #!/bin/wrapper_script (...blabla contents of script_X) where /bin is of course, the right path to the wrapper_script. With that will just need to: chmod +x script_X ./script_X This can solve your problem?


5

One thing you can try is to recover your .bashrc from the memory of a running instance of bash. On Linux, run gcore PID to make a memory dump of a process specified by its PID. Whether this has a chance of working depends on how bash manages its memory; I haven't checked the source code to see if it's at all possible. It doesn't work for me on Debian jessie ...


2

You can get the default .bashrc from /etc/skel/.bashrc . Also there is a way to recover files opened by a certain process from /proc/PID/fd/<files>, but it is not the case for .bashrc as it is not permanently opened by the bash process.



Top 50 recent answers are included