Setup Vim environment for USACO coding

alias viaco='task="$(basename "$(pwd)")"; if [ -f "$task.c" ]; then vi -c "set mouse=n" -c "set autoread" -c "vsplit $task.out" -c "split $task.in" -c "wincmd l" -c "wincmd H" $task.c; fi'
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.c  |-----------------| |            | $task.out  | |            |                | -------------------------------

-1
By: yolila
2011-05-13 13:35:02

These Might Interest You

What Others Think

Hmm... If you're thinking of entering a "Computing Olympiad", I think you need to do better :-) The basename can be replaced with a bit of shell: task=${PWD##*/} Next, you can simplify the one-condition if clause: [ -f $task.c ] && vi ... Then you can combine all the vi commands with | (bar) set mouse=n|set autoread|vsplit ... Personally, I'd put the mouse=n and autoread in my ~/.vimrc Then, to save a little typing we can abbreviate: "task" to "t", "set" to "se", "autoread" to "ar", "vsplit" to "vs", "split" to "sp" and "wincmd" to "winc". That leaves: alias viaco='t=${PWD##*/}; [ -f $t.c ] && vi -c "vs $t.out|sp $t.in|winc l|winc H" $t.c' A reduction from 188 to 88 characters (it's possibly a bit cryptic, now :-) Note: I've removed the quotes from around the filenames. If there's any whitespace in the filenames then your original command will fail when vi tries to open files.
flatcap · 366 weeks and 5 days ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again. 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.

Share Your Commands



Stay in the loop…

Follow the Tweets.

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.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

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: