all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: zijianyue@163.com, 16045@debbugs.gnu.org,
	Michael Albinus <michael.albinus@gmx.de>
Subject: bug#16045: 24.3.50; rgrep can't work
Date: Fri, 06 Dec 2013 10:12:17 +0100	[thread overview]
Message-ID: <874n6mibri.fsf@igel.home> (raw)
In-Reply-To: <83fvq72ndc.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 05 Dec 2013 19:55:59 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

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

The shell interprets the \n\\ sequence.  Whether it is removed is
dependent on the quoting state.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."





  parent reply	other threads:[~2013-12-06  9:12 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                   ` bug#16045: 回复: " zijianyue
2013-12-09  7:20                     ` Michael Albinus
2013-12-06  9:12         ` Andreas Schwab [this message]
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=874n6mibri.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=16045@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=michael.albinus@gmx.de \
    --cc=zijianyue@163.com \
    /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.