From: zijianyue <zijianyue@163.com>
To: "Michael Albinus" <michael.albinus@gmx.de>,
"Eli Zaretskii" <eliz@gnu.org>
Cc: 16045 <16045@debbugs.gnu.org>
Subject: bug#16045: 回复: Re: bug#16045: 24.3.50; rgrep can't work
Date: Mon, 9 Dec 2013 13:23:16 +0800 [thread overview]
Message-ID: <201312091323110156731@163.com> (raw)
In-Reply-To: <201312041357404213761@163.com>
[-- Attachment #1: Type: text/plain, Size: 850 bytes --]
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@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.
[-- Attachment #2: Type: text/html, Size: 2934 bytes --]
next prev parent reply other threads:[~2013-12-09 5:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 5:57 bug#16045: 24.3.50; rgrep can't work zijianyue
2013-12-04 17:24 ` Eli Zaretskii
2013-12-04 19:10 ` Stefan Monnier
2013-12-04 19:36 ` Eli Zaretskii
2013-12-04 20:52 ` Stefan Monnier
2013-12-05 15:10 ` Michael Albinus
2013-12-05 17:55 ` Eli Zaretskii
2013-12-05 19:58 ` Michael Albinus
2013-12-05 20:23 ` Eli Zaretskii
2013-12-05 20:50 ` Michael Albinus
2013-12-05 21:09 ` Stefan Monnier
2013-12-06 15:39 ` Michael Albinus
2013-12-06 15:58 ` Eli Zaretskii
2013-12-06 16:15 ` Michael Albinus
2013-12-09 5:23 ` zijianyue [this message]
2013-12-09 7:20 ` Michael Albinus
2013-12-06 9:12 ` Andreas Schwab
2013-12-06 9:16 ` Andreas Schwab
2013-12-05 15:14 ` Michael Albinus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201312091323110156731@163.com \
--to=zijianyue@163.com \
--cc=16045@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael.albinus@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.