zsh-users
 help / color / mirror / code / Atom feed
From: Aaron Davies <agdavi01@louisville.edu>
To: zsh-users@sunsite.dk
Subject: Re: zsh tips plea (tip of the day)
Date: Fri, 23 Jul 2004 18:55:09 -0400	[thread overview]
Message-ID: <593082B4-DCFB-11D8-8D29-000502631FBD@louisville.edu> (raw)
In-Reply-To: <4100F8E4.2090501@our-own.net>

On Friday, July 23, 2004, at 07:39 AM, Joakim Ryden wrote:

> Peter Stephenson wrote:
>
>> zzapper wrote:
>>
>>> As this group's been a bit quiet lately, my plea would be for you 
>>> experts to occasionally post a tip, or explain some aspect of zsh.
>
>> The usual way of getting these is to post questions...
>
> OK - here's a question... ;)  What's a really cool thing you have done 
> with zsh recently? Or if you will... a few lines about "how I was able 
> to solve my issue using zsh" (yes, I was a high school teacher in a 
> previous life).

This isn't really recent, but probably the most common thing I do in 
zsh that can't be done anywhere else is use the advanced globbing 
stuff. For instance, I have a (fairly large) directory tree that I use 
to categorize and store incoming files that need to be processed, after 
which they get moved to archival directories through symlinks located 
in each "leaf" directory. Determining whether I have any files waiting 
for processing thus involves doing a recursive check for plain files 
only below the root of this tree. In bash, this would either be a 
significant amount of shell scripting effort or a rather ugly "find" 
command. (I hate find.) In zsh, it's "ls **/*(.)". Isn't that nice?
-- 
     __                      __
    /  )                    /  )
   /--/ __. .__  ______    /  / __. , __o  _  _
  /  (_(_/|_/ (_(_) / (_  (__/_(_/|_\/ <__</_/_)_




  reply	other threads:[~2004-07-23 22:58 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-23 11:12 zzapper
2004-07-23 11:24 ` Peter Stephenson
2004-07-23 11:39   ` Joakim Ryden
2004-07-23 22:55     ` Aaron Davies [this message]
2004-07-24  7:22       ` Vincent Lefevre
2004-07-24  8:00         ` Atom 'Smasher'
2004-07-24  8:10           ` Vincent Lefevre
2004-07-24  8:32             ` Atom 'Smasher'
2004-07-24 11:23               ` Vincent Lefevre
2004-07-24 12:42                 ` Geoff Wing
2004-07-25  0:46                   ` Vincent Lefevre
2004-07-25  4:54                     ` xargs (Re: zsh tips plea (tip of the day)) Bart Schaefer
2004-07-24 17:47                 ` zsh tips plea (tip of the day) Atom 'Smasher'
2004-07-24 15:52         ` Aaron Davies
2004-07-23 12:49   ` Björn Lindström
2004-07-28 15:18     ` Felix Rosencrantz
2004-07-28 16:17       ` DervishD
2004-07-28 18:03         ` Björn Lindström
2004-07-23 16:55 ` Atom 'Smasher'
2004-07-23 20:04   ` Vincent Lefevre
2004-07-23 20:23     ` Philippe Troin
2004-07-23 20:26       ` Vincent Lefevre
2004-07-23 21:37         ` Philippe Troin
2004-07-23 21:50           ` Vincent Lefevre
2004-07-23 22:02             ` Dan Nelson
2004-07-24  7:14               ` Vincent Lefevre
2004-07-28 12:08   ` Vincent Lefevre
2004-07-24 16:42 ` zzapper
2004-07-24 18:44   ` Bart Schaefer
2004-07-24 22:45     ` zzapper
2004-07-25 10:41       ` zzapper
2004-07-25 10:53         ` zzapper
2004-07-26 14:13 ` Peter Stephenson
2004-07-26 17:01   ` Bart Schaefer
2004-07-29 15:24 ` zzapper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=593082B4-DCFB-11D8-8D29-000502631FBD@louisville.edu \
    --to=agdavi01@louisville.edu \
    --cc=zsh-users@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).