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.

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

LIST FILENAMES OF FILES CREATED TODAY IN CURRENT DIRECTORY

Terminal - LIST FILENAMES OF FILES CREATED TODAY IN CURRENT DIRECTORY
TODAY=`date +"%b %d"`;ls -l | grep "$TODAY" | awk '{print $9}'
2010-07-29 02:28:27
Functions: awk grep
-3
LIST FILENAMES OF FILES CREATED TODAY IN CURRENT DIRECTORY

Alternatives

There are 2 alternatives - vote for the best!

Terminal - Alternatives
ls -l --time-style=+%Y-%m-%d | awk "/$(date +'%Y-%m-%d')/ {print \$7}"
2010-07-29 05:30:29
Functions: awk ls
1

This version eliminates the grep before the awk, which is always good. It works for GNU core utils and ensures that the date output of ls matches the format in the pattern match, regardless of locale, etc.

On BSD-based systems, you can easily eliminate both the grep and the awk:

find . -maxdepth 1 -Btime -$(date +%kh%lm) -type f

find -maxdepth 1 -mtime 0 -type f
2010-07-30 01:56:34
User: adeverteuil
Functions: find
Tags: find today mtime
1

Then pipe to 'xargs ls' for a familiar listing, possibly using find's -print0 and xarg's -0 options.

ls -la | grep $(date +%Y-%m-%d) | egrep -v -e '\.{1,2}' | sed "s/.*\:[0-9]\{2\} \(.\+\)$/\\1/g"

Know a better way?

If you can do better, submit your command here.

What others think

Just so you know, the +%b %d date format is not consistent across all systems. for example, mine is '+%F %R', which displays like "2010-07-28 15:35" Also, you may end up with a system that only has one time field, for example, just +%F, and not get any output at all, because awk would be printing nonexistent fields

Comment by camocrazed 222 weeks ago

Your point of view

You must be signed in to comment.

Related sites and podcasts