51–60 of 78 posts
Earlier quoted context omitted.
esc-. is my biggest miss as well. There are discussions on this but still havent been able to fix it on osx in iterm2 myself. Did get option-. to work for now but esc-. has 20+ years of pure reflex action burned into my brain.
Can you post your solution (or give a pointer)?
There is a thread about it here
Earlier quoted context omitted.
Simplified example: mkdir foo, cd foo. I type in mkdir foo then press enter, type "cd esc-.". Doesn't work. Command completion in fish doesn't help here. In real life this is of course mostly more complicated than a simple "foo".
function mkcd () { mkdir -p "$1" && cd "$1" }
set foo this that "the other"
echo $faux; echo $faux[1]
echo $foo[4]
Also, writing autocompletes for functions is both far simpler than in bash, but I'm also missing some of tools that bash provides.
Earlier quoted context omitted.
Can you post your solution (or give a pointer)?
function fish_user_key_bindings bind \e. 'history-token-search-backward' end There is a thread about it here https://github.com/fish-shell/fish-shell/issues/89
Earlier quoted context omitted.
I am a year-or-two-old fishshell convert who is reasonably well versed in bash and tried using zsh and bash with a big .bashrc. A few things stand out to me as huge pluses: - It has a lot of cool functionality out of the box such as highlighting, smarter autocomplete (type in a partial word at the prompt and hit up instead of the cumbersome bash ctrl r/s history prompt that loves to beep at you), directory history (a…
Do you know anyone with a 10k .bashrc?
$ ls -lh .bashrc
-rw-r--r-- 1 10k Jul 26 13:31 .bashrc
It's also remarkably fast because I took great effort to optimize the parts that happen the most. Shell is actually pretty fast if you don't fork and exec all the time...
Earlier quoted context omitted.
Do you know anyone with a 10k .bashrc?
I just checked, for fun: $ ls -lh .bashrc -rw-r--r-- 1 10k Jul 26 13:31 .bashrc Yep. It's also remarkably fast because I took great effort to optimize the parts that happen the most. Shell is actually pretty fast if you don't fork and exec all the time...
A few things I occasionally run into: You can't just paste somebodies setup instructions into your shell anymore (you can temporarily invoke bash for that though). And when writing setup instructions yourself, sh is still pretty much the standard. VirtualEnv generates an activate.fish out of the box - nice! I still occasionally type !grep by accident. And I do miss &&.