all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Backslash-escaped brackets in string literals
Date: Sun, 26 Jan 2020 18:00:25 +0200	[thread overview]
Message-ID: <83blqqp5ra.fsf@gnu.org> (raw)
In-Reply-To: <CE040B8C-ECF0-46BA-97EE-766B2FFEBEF9@acm.org> (message from Mattias Engdegård on Sun, 26 Jan 2020 12:24:11 +0100)

> From: Mattias Engdegård <mattiase@acm.org>
> Date: Sun, 26 Jan 2020 12:24:11 +0100
> Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
> 
> > I thought I've just shown you that disregarding this issue entirely is
> > still premature.  I'm okay with maybe making the text less mandatory
> > and more a recommendation, perhaps even mentioning older Emacs
> > versions.  But removing it entirely? what's the rush?
> 
> And I thought I just showed you that 'C-x 4 a' had actually been fixed... Let's shake hands.

🤝

> It's perfectly normal to adjust the documentation to match the implementation; no need for foot-dragging. Your point about being nice to users of older versions is taken, though. Would this patch do? It retains the recommendation while being clear about its purpose.

Fine with me, thanks.



  reply	other threads:[~2020-01-26 16:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-24 15:12 Backslash-escaped brackets in string literals Mattias Engdegård
2020-01-24 15:39 ` Eli Zaretskii
2020-01-24 17:36 ` Stefan Monnier
2020-01-24 22:22   ` Mattias Engdegård
2020-01-25  7:44     ` Eli Zaretskii
2020-01-25 10:34       ` Mattias Engdegård
2020-01-25 13:33         ` Eli Zaretskii
2020-01-25 15:32           ` Mattias Engdegård
2020-01-25 17:15             ` Eli Zaretskii
2020-01-26 11:24               ` Mattias Engdegård
2020-01-26 16:00                 ` Eli Zaretskii [this message]
2020-01-25 17:16             ` Drew Adams

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=83blqqp5ra.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mattiase@acm.org \
    --cc=monnier@iro.umontreal.ca \
    /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.