Interesting.. do you have any suggestions on making it 'safe' then ?
I could create a queue to hold the msg-id's then check for the file's
existence...
but I am still a little confused, why would I be able to read the file
before I actually call the save command (note to get it working I call
the pipe command before I call the save command)? doesn't that seem a
little too strange (or completely illogical for that matter..) ?
what I am saying is:
the pipe command is called first, but the save command has
theoretically not even be interpreted yet, so it executes first. yet
the file which is generated from the save command is magically already
there..
> The actual order of the deliveries is not defined. Your code is unsafe.
or, by the above you mean the 'delivery' is actually the commands I'm calling ?
c
On 6/18/05, Tony Finch <dot@???> wrote:
> On Fri, 17 Jun 2005, fci wrote:
> >
> > after an hour or two.. I finally figured out what the problem was. I
> > had originally thought the problem to be with my script but it was
> > with the filter.
> > The problem itself was that the file I needed from 'save' needed to be
> > before 'pipe' .. (the script would then read the saved file..)
> > to resolve the issue, I changed the order of save/pipe:
>
> Filters do not cause immediate deliveries as they are being processed:
> they simply set them up for later. The actual order of the deliveries is
> not defined. Your code is unsafe.
>
> Tony.
> --
> <fanf@???> <dot@???> http://dotat.at/ ${sg{\N${sg{\
> N\}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}\
> \N}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}
>
