[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#16045: 24.3.50; rgrep can't work
From: |
Michael Albinus |
Subject: |
bug#16045: 24.3.50; rgrep can't work |
Date: |
Fri, 06 Dec 2013 17:15:28 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) |
Eli Zaretskii <eliz@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.
- bug#16045: 24.3.50; rgrep can't work, (continued)
- bug#16045: 24.3.50; rgrep can't work, Michael Albinus, 2013/12/05
- bug#16045: 24.3.50; rgrep can't work, Eli Zaretskii, 2013/12/05
- bug#16045: 24.3.50; rgrep can't work, Michael Albinus, 2013/12/05
- bug#16045: 24.3.50; rgrep can't work, Eli Zaretskii, 2013/12/05
- bug#16045: 24.3.50; rgrep can't work, Michael Albinus, 2013/12/05
- bug#16045: 24.3.50; rgrep can't work, Stefan Monnier, 2013/12/05
- bug#16045: 24.3.50; rgrep can't work, Michael Albinus, 2013/12/06
- bug#16045: 24.3.50; rgrep can't work, Eli Zaretskii, 2013/12/06
- bug#16045: 24.3.50; rgrep can't work,
Michael Albinus <=
- bug#16045: 回复: Re: bug#16045: 24.3.50; rgrep can't work, zijianyue, 2013/12/09
- bug#16045: 24.3.50; rgrep can't work, Michael Albinus, 2013/12/09
- bug#16045: 24.3.50; rgrep can't work, Andreas Schwab, 2013/12/06
- bug#16045: 24.3.50; rgrep can't work, Andreas Schwab, 2013/12/06
bug#16045: 24.3.50; rgrep can't work, Michael Albinus, 2013/12/05