News for hackers. Stuff that matters.
Re:Mastering Bash and Terminal by whack on Saturday January 14, 2017 @05:11PM (#13400873)
Personally, I found the following to be extremely easy and powerful. A no-brainer that should be a bash default really.

  if [ -t 1 ]
  then
    #   search for commands that start off with the same characters already typed
    bind '"\e[A":history-search-backward'
    bind '"\e[B":history-search-forward'
  fi
One of my friends also recommended version-controlling your config files and storing them on gitlab, which I'm only sad I didn't do sooner. It's been such a help in keeping my aliases and configs in sync, as I make changes across numerous different machines.
Re:Mastering Bash and Terminal by antaflos on Sunday January 15, 2017 @12:18PM (#13405001)
A good starting point for versioning dotfiles is https://dotfiles.github.io/. I like to use Dotbot [1] for managing and installing my dotfiles, but there are plenty of other options listed.

[1] https://github.com/anishathalye/dotbot/

Re:Mastering Bash and Terminal by joatmon-snoo on Sunday January 15, 2017 @06:10AM (#13403506)
Having a .dotfiles/ repo makes life so much easier. Seriously.
Re:Mastering Bash and Terminal by lottin on Sunday January 15, 2017 @04:14AM (#13403177)
That these, probably the most useful Readline functions by far, are not bound to any keys by default is crazy. To me it makes more sense to bind them to M-p and M-n though.
Re:Mastering Bash and Terminal by 3131s on Saturday January 14, 2017 @09:41PM (#13402012)
Yes! This is the first thing I do in a new Linux OS.

Also, the author does not mention hitting tab for autocomplete (or displaying the remaining options that match what has been typed so far).

Re:Mastering Bash and Terminal by blockloop on Saturday January 14, 2017 @05:20PM (#13400917)
You can also put those in your ~/.inputrc
Re:Mastering Bash and Terminal by mjlangiii on Sunday January 15, 2017 @10:21AM (#13404362)
I'm sorry, can you explain how to use this?
Re:Mastering Bash and Terminal by whack on Sunday January 15, 2017 @04:30PM (#13406496)
Just stick that snippet in your .bashrc file