:r! reply-body --top '/tmp/Re1BDLjSqOg3'
On Tue, 25 May 2021, Andre Tann wrote:
> I repeatedly have the following situation, and wonder how it can be
> handled better than I do it now. These lines must be merged
>
> /path;text
> /path;text
> /path;text
>
> with these:
>
> /subdir
> /longsubdir
> /
Hi all,
I repeatedly have the following situation, and wonder how it can be
handled better than I do it now. These lines must be merged
/path;text
/path;text
/path;text
with these:
/subdir
/longsubdir
/longlongsubdir
Result:
/path/subdir;text
/path/longsubdir;text
/path/longlongsubdir;text
On 26.05.21 15:49, aroc...@vex.net wrote:
That assumption is probably reasonable, but a semi-colon is a legal
character in a Unix/Linux filename. (But should be reagarded as evidence
of a psychopath loose in the department.) The only character not legal in
a filename is "/".
...and the null
> this applies only to the first semi-colon on each line (which
> will always exist in your situation and by assumption won't be
> found in the paths).
>
That assumption is probably reasonable, but a semi-colon is a legal
character in a Unix/Linux filename. (But should be reagarded as evidence
o
On 5/25/21 4:54 PM, Andre Tann wrote:
> I repeatedly have the following situation, and wonder how it
> can be handled better than I do it now. These lines must be
> merged
>
> /path;text
> /path;text
> /path;text
>
> with these:
>
> /subdir
> /longsubdir
> /longlongsubdir
>
> Result:
>
> /path/subd
