[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] attach
From: |
Oliver Kiddle |
Subject: |
Re: [Nmh-workers] attach |
Date: |
Sat, 15 Sep 2012 19:08:08 +0200 |
Ralph Corderoy wrote:
> > David Levine <address@hidden> writes:
> > > Note that whatnow's attach will continue to allow attachment of
> > > directories because it expands those out to their contents. It
> > > doesn't check what the contents are, though. That's why we needed
> > > to add this check.
>
> I wonder if whatnow's `attach foo' attaching foo/* when it's a directory
> is surprising and it would be better to error, forcing the user to
Does it actually do that? From my tests, it seemed more broken:
% mkdir foo
% touch foo/{one,two}
% comp
...
What now? attach foo
What now? list
From:
...
Nmh-Attachment: /home/opk/one
Nmh-Attachment: /home/opk/two
The files are actually /home/opk/foo/one etc. This occurs because of the
use of ls: ls isn't prefixing the current directory so presumably that's
done by nmh.
Oliver
- Re: [Nmh-workers] I'm confused, (continued)