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.

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

2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.
Hide

Tags

Hide

Functions

Hide

Credits

Site by David Winterbottom (user root).

Open windows executable, file, or folder from cygwin terminal

Terminal - Open windows executable, file, or folder from cygwin terminal
explorer $( cygpath "/path/to/file_or_exe" -w )
2009-07-22 17:00:21
User: Highwayman
-2
Up
Down
Open windows executable, file, or folder from cygwin terminal

This executes faster than

cygstart.exe

I put this in a script and added it to my path:

cat `which explore.sh`

#!/bin/bash

if [ $# -eq 0 ]; then

explorer.exe $( cygpath `pwd` -w ) &

else

explorer.exe $( cygpath $1 -w ) &

fi;

Using the script you just type

explore.sh file_or_executable

Note: you can do this for any file that has an associated executable in the windows registry. This is quite handy if you want to open pictures or movies from xterm.

Show sample output | Add to favourites | Report as malicious

Know a better way?

If you can do better, submit your command here.

What others think

explorer.exe often chooses the wrong app when opening files, whereas cygstart is usually more accurate. I also have never noticed cygstart to be especially slow. Since I'm used to working on a Mac, I use a function to map open to cygstart:

open () { echo 'Using Windoze cygstart.exe instead.'; cygstart "$*" ; }
Comment by patrickben 132 weeks and 2 days ago

If it opens the wrong app, then it is because you have the wrong app in your windows registry. You should update your registry with the correct app. You can quickly update it using the "Open with..." option from windows explorer.

I can safely confirm that cygstart is slow on Windows Vista. It takes much longer than using explorer.exe! Its the same speed as double clicking a file from windows explorer.

Comment by Highwayman 132 weeks and 1 day ago

Cygstart uses the same mechanism as Explorer... and shouldn't be any slower.

Comment by romulusnr 121 weeks and 1 day ago

Your point of view

You must be signed in to comment.

Related sites and podcasts