Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Mastering Bash and Terminal

blockloop.io

Post reply on HN
Print view View original

131–140 of 186 posts

Re: Mastering Bash and Terminal

#131

Post by JepZ »

renlo wrote: post #97
Normal_gaussian wrote: post #2

Rather than temporarily suspend vim to use the terminal you can get vim to suspend and resume itself with the exclamation mark command. This has the benefit of not wreaking havoc on your vim session and allowing you to read data into vim by prefixing with r. For example :!ls will execute ls and show you the result (press enter to return) :r!ls will read the result of ls in for you More usefully :r!sed -n5,10p that/ot…

tmux is a good alternative to the whole paradigm of 'running shell commands within a text editor like vim'. Why run a shell command within vim when one can run the shell command in an actual shell? It seems to me that running a shell command in vim is using vim outside of its intended scope. It might be able to do it but it won't be able to do it well, which is where something like tmux comes in. I might be in the mi…

I use vim and tmux too. I use this combination, because I can also use 'watch' and 'tail -f' commands to deploy files or watch logs while I code.

Re: Mastering Bash and Terminal

#132

Post by ajsalminen »

bitserf wrote: post #52
teddyh wrote: post #40

Earlier quoted context omitted.

It would indeed be in the best interest of its users, but Apple has apparently decided that it would not be in its own best interest: http://meta.ath0.com/2012/02/05/apples-great-gpl-purge/ […] Anyway, the message is pretty obvious: Apple won’t ship anything that’s licensed under GPL v3 on OS X. Now, why is that? There are two big changes in GPL v3. The first is that it explicitly prohibits patent lawsuits against pe…

Or, it could just switch the default shell to Z shell. First thing I do on a new Mac, is chsh -> zsh. Ships with an up to date (enough) version of that.

It could, but "just" switching shells is definitely an inconvenience to your users as well.

Re: Mastering Bash and Terminal

#133

Post by 77pt77 »

frahs wrote: post #85
Normal_gaussian wrote: post #2

Rather than temporarily suspend vim to use the terminal you can get vim to suspend and resume itself with the exclamation mark command. This has the benefit of not wreaking havoc on your vim session and allowing you to read data into vim by prefixing with r. For example :!ls will execute ls and show you the result (press enter to return) :r!ls will read the result of ls in for you More usefully :r!sed -n5,10p that/ot…

You actually don't have to put ! In front of make. Vim has makefile integration. If all you're doing is typing make, you can do :make. For a custom build command, you can set the variable makeprg, and :make will execute that instead. On my phone so it's hard to type examples, this blog post gives more info: https://jbernard.io/2011/09/30/vim-makeprg.html

not only that but it also interprets the errors and goes to the correct line

have a look at :cw[indow]

Re: Mastering Bash and Terminal

#134

Post by bigbugbag »

erikb wrote: post #113
oblio wrote: post #20

Earlier quoted context omitted.

zsh was quite popular when I first went spelunking in *NIX-land (2005). oh-my-zsh, which was a decent boost to zsh popularity, seems to have been around since 2009 ( http://ohmyz.sh/ ). zsh has always been held back by the "default browser"-syndrome: Linux and Mac OS both come with "good enough" default shells, so few people actually want to go through the effort of switching. Especially since there is a bit of a lea…

Also, when you use a lot of scripts that only work with bash (there are more than you'd expect, despite zsh saying it is bash compatible) then you have the choice of either rewriting these scripts or using bash. Most ppl will choose not to rewrite.

Many scripts are not written to be portable, bash or otherwise. The main reason those scripts rely on bashisms is that bash has long been the default shell in most distro.

IIRC debian provides a checkbashisms to know which scripts will pose problems when ran against /bin/sh

Re: Mastering Bash and Terminal

#135

Post by JdeBP »

kovek wrote: post #25
oblio wrote: post #14

The article is nice but a small part of it rubs me the wrong way: > I know there are some cool newcomers out there like zsh and fish, but after trying others out I always found that some of my utilities were missing or ill-replaced. First of all bash was first released in 1989 and zsh arrived just 1 year later so zsh is in no way a newcomer. Secondly zsh is almost strictly a bash superset so I don't know what he was…

On my version of zsh I was not able to do the following which is available on bash: http://unix.stackexchange.com/a/203075

On both version 4.3.12 on Interix and version 5.2 on FreeBSD, "f" followed by a character works perfectly fine in "vi" mode and Control-X Control-F followed by a character, as per the zshzle manual, works perfectly fine in "emacs" mode. What were you doing wrong?

Re: Mastering Bash and Terminal

#137

Post by bigbugbag »

blockloop wrote: post #18
oblio wrote: post #14

The article is nice but a small part of it rubs me the wrong way: > I know there are some cool newcomers out there like zsh and fish, but after trying others out I always found that some of my utilities were missing or ill-replaced. First of all bash was first released in 1989 and zsh arrived just 1 year later so zsh is in no way a newcomer. Secondly zsh is almost strictly a bash superset so I don't know what he was…

I wasn't so much commenting on the release date when I said "newcomers." Mostly commenting on my personal experience. I've been using bash for a long time and only recently have I seen zsh get so popular. It's entirely possible that only the people I know have only recently taken an interest in it. I would have to run zsh again to remember the pieces that I didn't like. I might have been able to configure my way arou…

The piece you didn't like about zsh is probably the usual: it comes with no preconception of how you want to use it , i.e. with no default settings.

It requires some work to build zsh settings to one's personal preferences but once done you are at home. Alternatively you can use one of the many settings you can find around, it is faster and simpler but now you're living in someone else' home.

Re: Mastering Bash and Terminal

#138

Post by TheAceOfHearts »

eknkc wrote: post #128
TheAceOfHearts wrote: post #107

I've tried bash, zsh, and fish. After trying all three, I'm staying with fish. bash and zsh don't have sensible defaults, and configuring them is tedious. fish works great out of the box, and it's really fast. When I picked up zsh I used oh-my-zsh and later prezto, but it was slow and figuring out what everything all the framework did was complicated. With fish I have a setup.fish script that defines all my universal…

I use fish too but I'm thinking about switching back to zsh. Mostly due to incompatible software here and there (like nvm) and lack of completions for a lot of cli tools.

asdf [0] is a great alternative to nvm. The best part is that it supports multiple languages and it's fast. I use the plugins for elixir, erlang, nodejs, and ruby.

Many CLI tools are missing completions, but I think it's slowly getting better over time. The pros outweigh the cons for me.

[0] https://github.com/asdf-vm/asdf

[1] https://github.com/fisherman/fisherman

Re: Mastering Bash and Terminal

#139

Post by Kubuxu »

jacobmischka wrote: post #105
dotancohen wrote: post #103

Earlier quoted context omitted.

Though I understand that this is just an example of the power of `!r`, readers should know that VIM in fact can copy to the system clipboards natively. "*y "+y

Only if it's compiled with clipboard support. I don't know about in other places, but in the default Arch package it's not. So this command is a perfect solution for me.

You need to install `gvim` which provides `vim` with that feature.

Re: Mastering Bash and Terminal

#140

Post by bigbugbag »

TheAceOfHearts wrote: post #107

I've tried bash, zsh, and fish. After trying all three, I'm staying with fish. bash and zsh don't have sensible defaults, and configuring them is tedious. fish works great out of the box, and it's really fast. When I picked up zsh I used oh-my-zsh and later prezto, but it was slow and figuring out what everything all the framework did was complicated. With fish I have a setup.fish script that defines all my universal…

I tried fish and found it had some interesting new features but not worth switching from zsh, good news is others thought the same so I just had to spend 2 minutes and add 3 lines to my zsh configuration to get those fish features. tada !

https://github.com/zsh-users/zsh-syntax-highlighting

https://github.com/zsh-users/zsh-history-substring-search

https://github.com/zsh-users/zsh-autosuggestions

Post reply on HN