From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: spaces in filenames should be a crime.
Date: Sun, 26 Mar 2017 21:18:05 +0000 [thread overview]
Message-ID: <20170326211805.GA8170@fujitsu.shahaf.local2> (raw)
In-Reply-To: <0c1b9d89-edd0-a027-e2f1-d01c2d68fa4e@eastlink.ca>
Ray Andrews wrote on Sun, Mar 26, 2017 at 13:22:24 -0700:
> Gentlemen:
>
> This function:
>
> mostrecent ()
> {
> ls -l ${(f)$( find . -type f -printf "%T@ %p\n" | sort -n | cut -d'
> ' -f 2- | tail -n 1 )}
> }
You could replace the whole function with:
mostrecent() { ls -l -- **/*(.om[1]) }
That glob qualifier restricts the match to files ('.'), sorts them by
modified date ('om'), and selects the first result ('[1]').
You can then use [1,3] to select several files.
> Testing it on this dummy directory tree:
>
> ├── [ 0] a
> ├── [4.0K] absolute junk
> │ └── [ 0] junk
> ├── [ 0] b
> └── [ 0] c
>
> If the most recent file is under 'absolute junk', the function works, but it
> requires the ' ${(f) ... ' treatment, otherwise it barfs at the space in the
> directory name. However, if I change things to ' tail -n 3 " it shows me:
>
> ls: cannot access './a ./absolute junk/junk ./c': No such file or directory
>
> So whereas the ' ${(f) ' treatment fixes the one problem, it creates the
> other, which is obviously that everything is one string. Can I have it both
> ways? Protected spaces in the directory name, and still have multiple items
> for the listing? I've done stuff like this before, but using arrays.
>
> Or can printf handle the situation by itself?
As Vadim said, putting the $() in double quotes makes this example work.
Another option here is to use find -print0 with ${(0)}. That only
matter if you need to DTRT when filenames contain NL characters.
Cheers,
Daniel
next prev parent reply other threads:[~2017-03-26 21:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-26 20:22 Ray Andrews
2017-03-26 20:57 ` Vadim A. Misbakh-Soloviov
2017-03-26 21:18 ` Daniel Shahaf [this message]
2017-03-26 22:41 ` Ray Andrews
2017-03-26 23:20 ` Bart Schaefer
2017-03-27 0:47 ` Ray Andrews
2017-03-27 1:11 ` Chris ccb
2017-03-27 1:45 ` Ray Andrews
2017-03-27 1:44 ` Martijn Dekker
2017-03-27 2:17 ` Ray Andrews
2017-03-27 18:53 ` Jesper Nygårds
2017-03-27 23:18 ` Mikael Magnusson
2017-03-28 0:46 ` Ray Andrews
2017-03-28 9:08 ` Martin Richter
2017-03-28 14:29 ` Ray Andrews
2017-03-28 16:10 ` Daniel Shahaf
2017-03-28 18:01 ` Ray Andrews
2017-03-28 18:38 ` Martijn Dekker
[not found] ` <60a213ad-6cb3-bef4-9e61-f2c1611a5e71__30788.3357666016$1490694707$gmane$org@gmx.de>
2017-03-29 11:27 ` Stephane Chazelas
2017-03-29 14:50 ` Ray Andrews
2017-03-29 15:21 ` Peter Stephenson
2017-03-29 16:21 ` Ray Andrews
2017-03-30 17:36 ` Bart Schaefer
2017-03-28 16:42 ` Matthew Martin
2017-03-26 21:24 ` Peter Stephenson
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=20170326211805.GA8170@fujitsu.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--cc=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.org \
/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).