Linked by Thom Holwerda on Fri 13th Jun 2008 21:50 UTC, submitted by pkrumins
General Development Peteris Krumins has written a three-part article series on his blog about using Bash effectively. The three parts are Editing commands in Emacs editing mode, Editing commands in Vi editing mode, and Definitive guide to Bash command line history. All three articles come with 'cheat sheets' in .pdf and .txt format so you can memorise the commands and shortcuts easier.
Thread beginning with comment 318473
To read all comments associated with this story, please click here.
Comment by moleskine
by moleskine on Sat 14th Jun 2008 09:08 UTC
moleskine
Member since:
2005-11-05

Always good to see an idea that may help folks by making something easier to use. It may be of more practical, day-to-day value than a bigger deal.

I wonder if there's a bash adaptation for the joe editor, though? I find joe easier than vi for simple tasks. In addition, joe's magic key is Ctrl, which I find easier and quicker to hit from the keyboard (with my little finger) than vi's Esc key.

RE: Comment by moleskine
by Doc Pain on Sat 14th Jun 2008 14:48 in reply to "Comment by moleskine"
Doc Pain Member since:
2006-10-08

I wonder if there's a bash adaptation for the joe editor, though? I find joe easier than vi for simple tasks. In addition, joe's magic key is Ctrl, which I find easier and quicker to hit from the keyboard (with my little finger) than vi's Esc key.


Joes own editor? Wow, I thought I've been the only person using it! :-) Yes, joe was my favourite editor until I got familiar with the Midnight Commander's editor mcedit. But still, joe has many useful features that mcedit hasn't, it even supports syntax highlighting, ^KE along with ^KN, and ^KR, Meta key combinations, the versatile block selection method, and finally it's very lightweight.

Great article, by the way, I didn't know that bash's interactive features had been designed so intelligent and helpful. I'd like to know which of these features are bash exclusively and which are available in standard sh, too (because sh is UNIX's standard scripting shell - interoperability). It seems that bas has incorporated parts of sed and awk. :-)

On my BSD systems, csh (i. e. tcsh) is my favourite shell for dialog use. A little bit customization (lines 'set promptchars = "%#"', 'set prompt = "%n@%m:%~%# "' and 'set autolist' into /etc/csh.cshrc) and it's much more comfortable than the standard settings.

^KX

Reply Parent Bookmark Score: 2