commandlinefu.com is the place to record those command-line gems that you return to again and again.
Delete that bloated snippets file you've been using and share your personal repository with the world. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.
If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/
You can sign-in using OpenID credentials, or register a traditional username and password.
First-time OpenID users will be automatically assigned a username which can be changed after signing in.
Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.
Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):
Subscribe to the feed for:
also works in vim
1. Get name of task by task=$(basename "$(pwd)")
2. Check whether "$task.c" exists as a file
3. open "$task.c", "$task.in", "task.out" in vim with such layout.
| | $task.in |
| | |
| | $task.out |
| | |
In this case, we'll be editing every PHP file from the current location down the tree.
You can show all the files in the vim buffer with :buffers which outputs something like,
1 %a "./config/config.php" line 1
2 "./lib/ws-php-library.php" line 0
3 "./lib/css.php" line 0
4 "./lib/mysqldb.class.php" line 0
5 "./lib/config.class.php" line 0
6 "./lib/actions.php" line 0
Press ENTER or type command to continue
If you'd like to edit ./lib/mysqldb.class.php for example, enter :b4 anytime you're editing a file. You can switch back and forth.
The sample command searches for PHP files replacing tabs with spaces.
-u NONE # don't use vimrc
one may pass
Look at this http://susepaste.org/69028693 also
This will skip all initializations. Especially useful when your ~/.vimrc has something wrong.
in command mode, navigate your cursor to the line where you want the command output to appear, and hit "!!". No need to enter edit mode or even type a ":" (colon).
I always add this to my .profile rc so I can do things like: "vim *.c" and the files are opened in tabs.
python is indent sensitive, after command
you may see your codes are mixed with tab and space
ret can help you to convert space to tab or tab to space
Faster and more convinent than [Esc]
This function returns TRUE if the application supports tcp-wrapping or FALSE if not by reading the shared libraries used by this application.
Add this to .vimrc to automatically give scripts with a shebang (e.g., #!/usr/bin/perl) executable permissions when saving.
This is assuming that you're editing some file that has not been wrapped at 80 columns, and you want it to be wrapped. While in Vim, enter ex mode, and set the textwidth to 80 columns:
to get to the top of the file, and:
to wrap every line from the top to the bottom of the file at 80 characters.
Of course, this will lose any indentation blocks you've setup if typing up some source code, or doing type setting. You can make modifications to this command as needed, as 'gq' is the formatting command you want, then you could send the formatting to a specific line in the file, rather than to the end of the file.
Will apply the format from your current cursor location to the 49th row. And so on.
In case the line you want to join start with a char different than ", you may use \n.*"\n as regex.
This will save and execute your python script every time your press the F5 function key.
It can also be added to your .vimrc:
autocmd BufRead *.py nmap :w^M:!python %
NOTE: the ^M is not just caret-M, it can be created by type: ctrl-v ctrl-m
Only under linux.
Requires Gvim compiled with "clientserver" functionality and
wmctrl command installed on system.
Instead of servername can be used the current edited file name.
Put it in a function and map it for get rid of "Press a key" after execution.
this line ends here
but must be concatenated with this one
"this line ends here"
and should NOT be concatenated with this one
Like the http://www.commandlinefu.com/commands/view/6327/open-file-with-sudo-when-there-is-no-write-permission, but works (in zsh; my commandlinefu is not strong enough to understand why bash don't like it) with vim options, like -O, and many input files.
There could be other mistakes.
this avoids several VIM warnings, which I seem too stupid to disable: warning, readonly! and: file and buffer have changed, reload?!
And in case you want to migrate back to, err.. MS-DOS: ":set ff=dos" does the opposite.