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

Previous Next

Full log

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

From: zijianyue <zijianyue <at> 163.com>
To: "Michael Albinus" <michael.albinus <at> gmx.de>, "Eli Zaretskii" <eliz <at> gnu.org>
Cc: 16045 <16045 <at> debbugs.gnu.org>, monnier <monnier <at> iro.umontreal.ca>
Subject: 回复: Re: bug#16045: 24.3.50; rgrep can't work
Date: Mon, 9 Dec 2013 13:23:16 +0800

[Message part 1 (text/plain, inline)]

GREAT！rgrep works well now in the 2013-12-07 version,thanks for your work!!!




zijianyue

From: Michael Albinus
Date: 2013-12-07 00:15
To: Eli Zaretskii
CC: monnier; zijianyue; 16045
Subject: Re: bug#16045: 24.3.50; rgrep can't work
Eli Zaretskii <eliz <at> gnu.org> writes:

> It's not enough to test with a remote directory, we need to test it
> when it exceeds the line-length limits, no?

Yes. According to my tests, the problem happens when you apply rgrep
(loooong parameter list of find), and Tramp uses on the remote side
ksh. For other shells like zsh or bash I haven't seen any problem.

However, Tramp does not care about the remote shell, and starts to
insert "\\\n" every 500 bytes of the command line, looking for the
next space there. Using rgrep for tests shall be sufficient, I believe.

Best regrads, Michael.

[Message part 2 (text/html, inline)]

Previous Next

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