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

Previous Next

Package: emacs;

Reported by: zijianyue <zijianyue <at> 163.com>

Date: Wed, 4 Dec 2013 10:06:02 UTC

Severity: normal

Found in version 24.3.50

Done: Michael Albinus <michael.albinus <at> gmx.de>

Bug is archived. No further changes may be made.

Full log


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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Michael Albinus <michael.albinus <at> gmx.de>
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 19:55:59 +0200
> From: Michael Albinus <michael.albinus <at> gmx.de>
> Cc: Eli Zaretskii <eliz <at> gnu.org>,  zijianyue <zijianyue <at> 163.com>,  16045 <at> debbugs.gnu.org
> Date: Thu, 05 Dec 2013 16:10:26 +0100
> 
> Hard for Tramp. It gets a long string as argument of
> `start-file-process-shell-command', which looks like the example in
> <http://thread.gmane.org/gmane.emacs.tramp/8233/focus=8244>. How shall
> Tramp parse it?

Why should it parse it?  Isn't \n\ removed on the remote end before
the shell there interprets it?

> Where does it know from, how long a command line in the remote shell
> could be?

How do you know that in grep.el?




This bug report was last modified 11 years and 168 days ago.

Previous Next


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