unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Harald Hanche-Olsen <hanche@math.ntnu.no>
Subject: Re: replacing endline
Date: Fri, 21 Apr 2006 08:52:49 +0200	[thread overview]
Message-ID: <pcohd4n773y.fsf@shuttle.math.ntnu.no> (raw)
In-Reply-To: mailman.671.1145571606.9609.help-gnu-emacs@gnu.org

+ Lennart Borgman <lennart.borgman.073@student.lu.se>:

| AFAICS the same escape syntax that are used for strings in elisp
| could be used for strings read in the minibuffer. In princip I mean,
| not now of course.

Sure, in principle you could choose any escape convention you please.

| To me it is not unnatural at all. But maybe it is very inconvenient?
| Could you please explain what you mean from that point of view?

Well, if backslash was an escape character in string reads in the
minibuffer, any latex user who wants to replace \foo by \bar would
have to type those strings as \\foo and \\bar.  That would confuse
newbies, and be inconvenient to more experienced folk.  It gets worse
if you need to use query-replace-regexp, which also uses backslashes
for an escape convention, so you might end up having to type a
quadruple backslash in place of a single one.  Ouch!

Besides, the C-q escape convention is not only for the minibuffer.
It's for every kind of buffer!  Once you realise that there is nothing
that special about the minibuffer - it's just an ordinary buffer with
a peculiar mode - you will see that this is very logical indeed.

(I think I am going to bow out of this discussion now.  I have said
all I have to say on the topic, and can't think of a way to state it
more clearly.)

-- 
* Harald Hanche-Olsen     <URL:http://www.math.ntnu.no/~hanche/>
- It is undesirable to believe a proposition
  when there is no ground whatsoever for supposing it is true.
  -- Bertrand Russell

  parent reply	other threads:[~2006-04-21  6:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-20  0:18 replacing endline sarah.dzion
2006-04-20  1:15 ` Katsumi Yamaoka
2006-04-20  1:17 ` Ye Wenbin
2006-04-20  1:22 ` Fredrik Bulow
2006-04-20  1:44 ` Fredrik Bulow
2006-04-20  1:56 ` Fredrik Bulow
2006-04-20  6:32   ` Thien-Thi Nguyen
2006-04-20 14:43     ` Fredrik Bulow
2006-04-20 16:11       ` Lennart Borgman
2006-04-20 18:16       ` Eli Zaretskii
     [not found]       ` <mailman.650.1145549499.9609.help-gnu-emacs@gnu.org>
2006-04-20 19:25         ` Harald Hanche-Olsen
2006-04-20 22:19           ` Lennart Borgman
2006-04-21  7:38             ` Eli Zaretskii
     [not found]           ` <mailman.671.1145571606.9609.help-gnu-emacs@gnu.org>
2006-04-21  6:52             ` Harald Hanche-Olsen [this message]
2006-04-21  0:53         ` Thien-Thi Nguyen
2006-04-20 23:38       ` B. T. Raven
2006-04-20 10:21   ` Peter Dyballa
2006-04-20 18:54 ` kgold

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pcohd4n773y.fsf@shuttle.math.ntnu.no \
    --to=hanche@math.ntnu.no \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).