This seems like a good place to once again plug fish[1]. Exactly those goodies I want in a shell and the autocomplete is so convenient I no longer know how I lived without it.
And there's all the other cruft removal.
Love Your Terminal
81–90 of 137 posts
Re: Love Your Terminal
#82I am curious what terminal people use on Windows. I find MSYS to be very good, since it lets me work just as I would on Linux with Emacs-style editing.
I'm using Console2 (http://www.hanselman.com/blog/Console2ABetterWindowsCommandP...) and Powershell. Not as nice as a real Linux environment, but Console2 has tabs which makes it bearable.
Re: Love Your Terminal
#83YA post about making fancy prompts - at least its not about how to make a ssh tunnel ;-) Personally I'm never using anything, or adding any fancy setting, if it doesn't serve any direct purpose and/or is not clear, simple and efficient. It's not because I believe "simple" and "efficient" are "cool" or "better". It's just because it's always what made _me_ efficient. I don't lose much time digging configs either, and…
I'm largely the same. The only terminal app I did play around with the configs for was tmux because I really hated the defaults on that. And as I only ever need to run tmux from my client PC (it's a bit pointless running tmux inside of tmux), i don't have to arse about with copying config files about.
Re: Love Your Terminal
#84This seems like a good place to once again plug fish[1]. Exactly those goodies I want in a shell and the autocomplete is so convenient I no longer know how I lived without it. And there's all the other cruft removal. [1] http://ridiculousfish.com/shell/
I'd just like to second this. Though bear in mind that many things assume you're running bash on OS X, e.g. the homebrew installation one-liner doesn't work with fish.
Also, note that you can easily copy across your bash settings using:
/usr/local/share/fish/tools/import_bash_settings.py (from http://ridiculousfish.com/shell/faq.html )
Re: Love Your Terminal
#85Earlier quoted context omitted.
> A whole extra line above the working prompt? Because it's frequently useful, and thus the tradeoff of a bit of space for simplicity, speed and familiarity is worth it. > If you need that info at any particular moment, make a command. Right, so your prompt is composed of nothing but the hardcoded character `>`? (you obviously don't need the $/# toggle as you can use `whoami`, and you don't need the previous command'…
My prompt is usually the system default, because I work across multiple systems, some of which don't even have bash (let alone zsh), and changing it seems unnecessary. 'wi' is just there to remind me where I am once in a while. My general philosophy is to deal with whatever is the default and not become reliant on customisations because other systems I'll be required to use won't have any of them set up.
> My prompt is usually the system default, because I work across multiple systems,
Unless you get new systems everyday, multiple systems just mean copying ssh keys followed by scp of dotfiles.
> some of which don't even have bash (let alone zsh),
If it has bash, .bashrc gets executed. If it has neither, I use the system default. Just because sometimes there won't be a shell I use or configure(1%) doesn't mean I am going to put up with whatever the system throws at me(99%).
> 'wi' is just there to remind me where I am once in a while.
Any my "once in a while" is frequent. Multiple machines, multiple projects, multiple branches.
> My general philosophy is to deal with whatever is the default and not become reliant on customisations because other systems I'll be required to use won't have any of them set up.
If I have customized my vim to hell, it generally means I am familiar enough with vim to understand how vim works. Same goes for bash, screen, zsh, what have you. It isn't like when once in an eternity, I am forced to use a machine where I have to type "git branch" instead of "gitb", I am going to forget it.
Re: Love Your Terminal
#86Yet another article proclaiming bash as garbage and zsh as the best thing since sliced bread.
Meh. I use bash on my laptop and zsh on my VM, and barely notice a difference between the two other than my different prompt. That tells me I'm not getting the most out of it, but it also tells me that the out-of-the-box improvements are pretty minimal. Given how many machines I need to attempt to keep my customizations in sync across (git is barely an option, let alone something like dropbox - this is inside a PCI L…
I'm in exactly the same boat as you (except we're at PCI level 2).
tmux on my local machine does me fine. And as loading tmux inside of tmux is pointless, I don't need to copy configs across.
though what I do have is a number of cheat sheets for each type of server, so I have copy and paste code (most of it is simple enough stuff, but sometimes having a visual reminder is helpful when you're up against tight, stressful, deadlines)
Re: Love Your Terminal
#87This seems like a good place to once again plug fish[1]. Exactly those goodies I want in a shell and the autocomplete is so convenient I no longer know how I lived without it. And there's all the other cruft removal. [1] http://ridiculousfish.com/shell/
I've just installed fish and it doesn't support bang (!) history nor some basic scripting tools (eg $?) which makes it pretty useless for power users.
I can see how the colours and suggestions are great to those who are new to the command line though and there were some cool features (eg highlight search phrases from grep). But most of that stuff is just emphasising stuff you'd learn to spot anyway, after using the CLI for years.
So as cool as it is, I really would find it more of a hindrance than a help.
Re: Love Your Terminal
#88Whatever the terminal you are using, configure it so that it doesn't eat your alt/ctrl key and then learn readline bindings.
Kinda weird that the author mentions Ctrl-R but not readline. History searching actually works for everything that supports readline, e.g. bash, ipython, psql, henplus, etc, although personally I use page-up / page-down with:
"\e[5~": history-search-backward
"\e[6~": history-search-forward
Re: Love Your Terminal
#89I am curious what terminal people use on Windows. I find MSYS to be very good, since it lets me work just as I would on Linux with Emacs-style editing.
Cygwin, with mintty and all the trimmings. Or Clink - https://code.google.com/p/clink/
Wow! I didn't know there is readline support for cmd.exe. This is great.
Re: Love Your Terminal
#90This seems like a good place to once again plug fish[1]. Exactly those goodies I want in a shell and the autocomplete is so convenient I no longer know how I lived without it. And there's all the other cruft removal. [1] http://ridiculousfish.com/shell/
I've just installed fish and it doesn't support bang (!) history nor some basic scripting tools (eg $?) which makes it pretty useless for power users. I can see how the colours and suggestions are great to those who are new to the command line though and there were some cool features (eg highlight search phrases from grep). But most of that stuff is just emphasising stuff you'd learn to spot anyway, after using the C…
Fish is not a POSIX shell. For example, instead of $? there is $status.