zsh-users
 help / color / mirror / code / Atom feed
From: Meino Christian Cramer <Meino.Cramer@gmx.de>
To: zsh@dervishd.net
Cc: zsh-users@sunsite.dk
Subject: Re: Sorting files
Date: Fri, 05 Aug 2005 16:01:01 +0200 (CEST)	[thread overview]
Message-ID: <20050805.160101.59466185.Meino.Cramer@gmx.de> (raw)
In-Reply-To: <20050805125243.GB105@DervishD>

From: DervishD <zsh@dervishd.net>
Subject: Re: Sorting files
Date: Fri, 5 Aug 2005 14:52:43 +0200

Hi Raúl !   :)

 (sorry, if your name comes out somehow -- hrmm -- "encrypted"...
 my Emacs seems to handle everything other than plain ascii a little 
 weird... ;)

 Hmmm...interesting.. as soon as you mailed me that it works for you
 my zsh seems to be that impressed, that s/he decided also to work
 correctly....mysterious ! ;O)

 More seriously... I dont know what's happening here. May be I
 mispelled an option or forget a "-" somewhere...

 More important: It WORKS ! :)   (even for me! ;)

 Another question in this context:
 To check the options, I had to construct this one:

    for i in  **/*(.oL) 
    do
		ls -ld $i
    done | less
 
 Is there any other more shorter way to achieve the same results with
 less code -- especially without calling any other "tool" like
 zsh/stat or xargs or such ? But I insist on getting filenames AND
 sizes ! ;O) Not only the filename should be shown!

 Ok, now this is more like a "coding contest" for me than a practical
 excurse....but I like to tune things :O))


 Have a nice weekend !
 Meino


 
 


>     Hi Meino :)
> 
>  * Meino Christian Cramer <Meino.Cramer@gmx.de> dixit:
> >  I would understand this, if I had submitted something like:
> >    print -l **/*(oL) 
> 
>     print -l -- **/*(.oL) works for me, tested in my root directory.
> It's a good idea to use '-r' too, as suggested in the thread, just in
> case there is any weird filename.
> 
>     Raúl Núñez de Arenas Coronado
> 
> -- 
> Linux Registered User 88736 | http://www.dervishd.net
> http://www.pleyades.net & http://www.gotesdelluna.net
> It's my PC and I'll cry if I want to...
> 

  reply	other threads:[~2005-08-05 14:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-04 18:38 Meino Christian Cramer
2005-08-04 18:48 ` Mikael Magnusson
2005-08-04 19:10   ` Meino Christian Cramer
2005-08-04 19:18     ` Danek Duvall
2005-08-04 20:41       ` Stephane Chazelas
2005-08-05  3:01         ` Meino Christian Cramer
2005-08-05 10:47           ` Stephane CHAZELAS
2005-08-04 19:14 ` Christian Schneider
2005-08-04 21:19   ` Jens Kubieziel
2005-08-05  3:06   ` Meino Christian Cramer
2005-08-04 19:51 ` Christian Taylor
2005-08-05 10:51   ` zzapper
2005-08-05 12:57     ` Christian Taylor
2005-08-05 14:41     ` Meino Christian Cramer
2005-08-06  5:38     ` Summary: " Meino Christian Cramer
2005-08-06  9:22       ` Christian Taylor
2005-08-05 12:52 ` DervishD
2005-08-05 14:01   ` Meino Christian Cramer [this message]
2005-08-05 14:29     ` Mikael Magnusson

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=20050805.160101.59466185.Meino.Cramer@gmx.de \
    --to=meino.cramer@gmx.de \
    --cc=zsh-users@sunsite.dk \
    --cc=zsh@dervishd.net \
    /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).