Hide

What's this?

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/

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

OpenID
or
Sign in Register

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

World cup college
Hide

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:

Hide

News

2010-03-03 - Commandlinefu @ SXSW 2010
Am going to be at SXSW this year, in case you want to submit any CLI nuggets or suggestions to me in person. Ping me on the @codeinthehole Twitter account.
2009-09-12 - Email updates now available
You can now enable email updates to let you know each time you're command is commented on.
2009-07-11 - API and javascript blog widget now available
A simple API has been released, allowing commands to be retrieved in various formats. This also allows commands to be embedded on blogs/homepages.
2009-05-17 - Added duplicate suggestions to the new command form
When adding a new command, a quick background search is performed to make sure you're not duplicating a command already in the system.
Hide

Tags

Hide

Functions

Hide

Credits

Site by David Winterbottom (user root).

Relocate a file or directory, but keep it accessible on the old location throug a simlink.

Terminal - Relocate a file or directory, but keep it accessible on the old location throug a simlink.
mv $1 $2 && ln -s $2/$(basename $1) $(dirname $1)
2009-05-25 08:54:36
User: svg
Functions: basename dirname ln mv
16
Up
Down
Relocate a file or directory, but keep it accessible on the old location throug a simlink.

Used for moving stuff around on a fileserver

Add to favourites | Report as malicious

Know a better way?

If you can do better, submit your command here.

What others think

sweet. i've made it a function in all my .bash_profiles.

function lmv(){

[ -e $1 -a -e $2 ] && mv $1 $2 && ln -s $2/$(basename $1) $(dirname $1);

}

Comment by thebillywayne 41 weeks and 5 days ago

It only works, if $2 is a directory, though.

Comment by jxy 41 weeks and 4 days ago

Also does not play nice with files that have spaces or meta-characters in the names.

Comment by TheMightyBuzzard 41 weeks and 4 days ago

Always _quote_ the variables!

Comment by jxy 41 weeks and 3 days ago

from AlvinaSimpson over on lifehacker.com:

lmv() { [ -e "$1" -a -e "$2" ] && mv "$1" "$2" && ln -s "$2"/"$(basename "$1")" "$(dirname "$1")"; }

Me, I'd add one more bit and say go from

[ -e "$1" -a -e "$2" ]

to

[ -e "$1" -a -d "$2" ]

and from

mv "$1" "$2"

to

mv "$1" "$2"/

That should take care of any accidental file overwrites from trying to use wildcards with this command as it requires $2 be a directory and appends a trailing / so we don't accidentally try to overwrite the directory $2

Comment by TheMightyBuzzard 41 weeks and 3 days ago

By default, you shouldn't be trying to symlink when you do this; you only need to use symlinks when you're going from one physical drive to another.

The files that we see in the filesystem are pointers to the actual data on the drive. By creating a hard link, we have two real pointers to the same data; if one is removed, the other exists still, and the data is still "found" by the filesystem. If the original hardlink disappears but the symlink still exists, the symlink won't work.

When trying to do a "safe move" using links, hard links is what you should use.

Comment by adamskinner 41 weeks and 3 days ago

great suggestions for improving the function! i love this place!

Comment by thebillywayne 41 weeks and 2 days ago

Any recommendations to make this usable on directories with spaces or special characters? I want to use it to relocate bittorrent files regularly to another disk and they rarely have proper filenames.

by recommendations I mean a simpler way than writing/stealing code to escape all the special characters. I'm lazy and slow!

Comment by awoodby 39 weeks ago
lmv(){for a in ${@:1:$(expr $#-1)};do [ -e "$a" -a -e "${@:$#:1}" ] && mv "$a";"${@:$#:1}" && ln -s "${@:$#:1}"/"$(basename "$a")";"$(dirname "$a")";done}

for multiple folders (e.g. lmv files/* newfolder would move file/* to newfolder while symlinking them)

Comment by matthewbauer 11 weeks and 6 days ago
lmv(){for a in ${@:1:$(expr $#-1)};do [ -e "$a" -a -e "${@:$#}" ] && mv "$a";"${@:$#}" && ln -s "${@:$#}"/"$(basename "$a")";"$(dirname "$a")";done}
Comment by matthewbauer 11 weeks and 6 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts