GNU bug report logs - #16045
24.3.50; rgrep can't work

Previous Next

Full log

Message #35 received at 16045 <at> debbugs.gnu.org (full text, mbox):

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: zijianyue <at> 163.com, 16045 <at> debbugs.gnu.org, monnier <at> iro.umontreal.ca
Subject: Re: bug#16045: 24.3.50; rgrep can't work
Date: Thu, 05 Dec 2013 21:50:10 +0100

Eli Zaretskii <eliz <at> gnu.org> writes:

> Such commands have short lines anyway, so you would never need to
> break them.  So in practice here documents should never be a problem.

I know. I just wanted to demonstrate, that you cannot enter that line
break at any arbitrary point.

> Are there any other circumstances where a command cannot be broken in
> an arbitrary place?

Don't know.

> Anyway, you could break on whitespace, to be on the safe side.

Nope, see here:

$ cat <<EO\ F
> xxx \
> yyy
> EO \
> F
> EO F
xxx \
yyy
EO \
F

Again, a very unfriendly and malicious example. But shit happens.

> The question was about the remote shell limitations, so knowing about
> the arguments doesn't help.

It doesn't help to know the exact limitations. But it helps to know
where a potential line break could be placed.

Best regards, Michael.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.