On Sat, 21 Nov 2020 17:02:05 +0100, Alexander Hall wrote:
> So this is it. Any other objections? OK?
OK millert@
- todd
On Tue, Nov 17, 2020 at 01:11:42PM +0100, Paul de Weerd wrote:
> On Tue, Nov 17, 2020 at 01:06:05AM +0100, Alexander Hall wrote:
...
> | The more I read and think about it, I feel the original error message is
> | actually correct in that there is no terminating ";" or "+", since the
> |
On Mon, Nov 16, 2020 at 09:15:11AM +0100, Paul de Weerd wrote:
> Hi Andreas,
>
> On Mon, Nov 16, 2020 at 08:53:36AM +0100, Andreas Kusalananda Kähäri wrote:
> | On Thu, Nov 12, 2020 at 08:51:22PM +0100, Paul de Weerd wrote:
> | > Hi all,
> | >
> | > I misread find(1) and did:
> | >
> | >
On Thu, Nov 19, 2020 at 03:26:28PM -0800, Jordan Geoghegan wrote:
>
>
> On 11/16/20 12:15 AM, Paul de Weerd wrote:
> > Hi Andreas,
> >
> > On Mon, Nov 16, 2020 at 08:53:36AM +0100, Andreas Kusalananda Kähäri wrote:
> > | On Thu, Nov 12, 2020 at 08:51:22PM +0100, Paul de Weerd wrote:
> > | > Hi
On 11/16/20 12:15 AM, Paul de Weerd wrote:
Hi Andreas,
On Mon, Nov 16, 2020 at 08:53:36AM +0100, Andreas Kusalananda Kähäri wrote:
| On Thu, Nov 12, 2020 at 08:51:22PM +0100, Paul de Weerd wrote:
| > Hi all,
| >
| > I misread find(1) and did:
| >
| > [weerdpom] $ find path/to/cam -name
On November 17, 2020 1:11:42 PM GMT+01:00, Paul de Weerd
wrote:
>On Tue, Nov 17, 2020 at 01:06:05AM +0100, Alexander Hall wrote:
>| On Mon, Nov 16, 2020 at 09:04:53AM +0100, Paul de Weerd wrote:
>| > Hi Alexander,
>| >
>| > On Sun, Nov 15, 2020 at 10:22:32PM +0100, Alexander Hall wrote:
>| >
On Tue, Nov 17, 2020 at 01:06:05AM +0100, Alexander Hall wrote:
| On Mon, Nov 16, 2020 at 09:04:53AM +0100, Paul de Weerd wrote:
| > Hi Alexander,
| >
| > On Sun, Nov 15, 2020 at 10:22:32PM +0100, Alexander Hall wrote:
| > | I googled for "POSIX find", and hit this:
| > |
| > |
On Mon, Nov 16, 2020 at 09:04:53AM +0100, Paul de Weerd wrote:
> Hi Alexander,
>
> On Sun, Nov 15, 2020 at 10:22:32PM +0100, Alexander Hall wrote:
> | I googled for "POSIX find", and hit this:
> |
> | https://pubs.opengroup.org/onlinepubs/009695399/utilities/find.html
> |
> | => "Only a plus
Hi Andreas,
On Mon, Nov 16, 2020 at 08:53:36AM +0100, Andreas Kusalananda Kähäri wrote:
| On Thu, Nov 12, 2020 at 08:51:22PM +0100, Paul de Weerd wrote:
| > Hi all,
| >
| > I misread find(1) and did:
| >
| > [weerdpom] $ find path/to/cam -name \*.JPG -exec cp {} path/to/store +
| > find: -exec
Hi Alexander,
On Sun, Nov 15, 2020 at 10:22:32PM +0100, Alexander Hall wrote:
| I googled for "POSIX find", and hit this:
|
| https://pubs.opengroup.org/onlinepubs/009695399/utilities/find.html
|
| => "Only a plus sign that follows an argument containing the two
| characters "{}" shall
On Thu, Nov 12, 2020 at 08:51:22PM +0100, Paul de Weerd wrote:
> Hi all,
>
> I misread find(1) and did:
>
> [weerdpom] $ find path/to/cam -name \*.JPG -exec cp {} path/to/store +
> find: -exec no terminating ";" or "+"
Not really what you're asking for, but...
What you seem to want to do can
On Sun, Nov 15, 2020 at 07:19:07PM +0100, Paul de Weerd wrote:
> Hi all,
>
> It was pointed out to me off-list that I introduced a regression for
> the case that has '+' as one of its arguments, e.g.:
>
> [weerd@pom] $ find /var/empty -exec echo + {} +
> find: -exec: "+" should
Hi all,
It was pointed out to me off-list that I introduced a regression for
the case that has '+' as one of its arguments, e.g.:
[weerd@pom] $ find /var/empty -exec echo + {} +
find: -exec: "+" should follow {}
Updated diff fixes that case:
[weerd@pom]
Hi all,
I misread find(1) and did:
[weerdpom] $ find path/to/cam -name \*.JPG -exec cp {} path/to/store +
find: -exec no terminating ";" or "+"
That was somewhat surprising - there is a terminating "+". The error
really is that the "+" doesn't follow immediately after the "{}"
(which the
14 matches
Mail list logo
