Skip to main content

Quickly: Command history in Linux / Shell

If you are like me, doing a lot of command line in linux (Bash) shell, there are a few commands you do very often. The following commands will make your life a lot easier to quickly go back in command history.

[!!] or better yet [sudo !!] - [!!] is an alias for last run command. One of the best use of this is - Sometimes, you type a command and the shell hits you back with a root privileges required message. You dont have to copy the command and run again. just run [sudo !!]

[history] - just spits out ~/.bash_history with line numbers. A good use of this is piping it to grep to find something. The line numbers can be used to execute the command following it. Say for example, [history | grep find] lists the previous searches (okay, it also shows all commands with "find" anywhere in the line - but a filtered, smaller list).
$history | grep find
 457  find *.wav
 462  find *.wav -exec lame --preset fast extreme '{}' '/tmp/mp3/{}' \;
 487  find *.wav -exec mp3cvbr '{}' \;

To rerun the search just type !nnn where nnn is the number of the line shown, eg: !462.

And the best one..
[CTRL+R] Dont *type* it - press control + r on your keyboard at shell prompt. It opens a prompt that will start a reverse search on history of commands. Then, Type any part of the command (or arguments) that you have done in the past, it will fill in the whole command including the arguments. Hit Enter to execute it!!

Popular posts from this blog

Javascript: Convert Strings to Binary (and representing in a nerdy way!)

I follow those GoogleDevelopers Videos . Sometime back, in one of the presentations on GoogleIO, there was this interesting string of dots at the bottom of each page of the presentation . They looked like random big and small dots. A similar bunch of dots were also on the T-shirt of a presenter was wearing in another presentation . While it seemed something in the pattern, I could not find what it was. Finally, another presenter cleared the matter that those dots are just binary representation of "GOOGLEIO" (So much for advertizing Google IO, Impressive!). So I wanna do it. Takes me back to days of those DSP classes at school. Nerdy me had to churn some old brain cells. I remember those first programming language classes in Pascal and C when you were asked to do fibonacci series and converting a binary string to ascii codes. That *experience* came handy here: Check it out! Text to Binarize: For those who came to copy the javascript code to convert string to binary,

MySql Copying Table Structures.

Some times you need to copy only table structures across databases. This article describes two ways of doing it. If the whole database schema need to be exported, mysqldump is very effective. A --nodata flag will dump all tables' schema. Like this. mysqldump --nodata -p -u username databaseName But if you want to copy a specific table, individually, you could use "create table like" feature. You could create it even from a different database. However it must be on the same mysqld instance. Like this. create table newtable like oldtable; --Or from a table in other database create table mytable like otherdatabase.tablename;

javascript maxlength for textarea with \r\n breaks in java (esp Firefox)

Textareas allow new lines to enter. These are represented by \n (1) or \r\n (2) characters. But when you save to DB you have a limit to certain length of chars. There is no maxlength attribute in HTML that will stop you from entering data. This is generally acomplished by Javascript. You do a onkeyup hook and stop event or trim after textarea.value.length > maxlength. There are many other solutions out there.. But.. Here is the problem that most of those solutions overlook, How do you deal with the count on \n and \r\n representations. Lets first see how it matters. If the text entered has new lines, the length is calculated differently in Firefox and IE. When you enter a Text like 01234 567890 You expect the textarea.value.length to be 11. (10 chars + new line).On the backend, however, java would recieve it as 12 chars (10 chars + \r\n) (this is irrespective of FF or IE). So you are effectively saving 12 chars to DB. Worse yet, IE seems to figure textarea.value.length as 12 (