From: Juanma Barranquero <lekktu@gmail.com>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: ?\ vs. ?\s
Date: Wed, 29 Jun 2005 11:48:57 +0200 [thread overview]
Message-ID: <f7ccd24b0506290248455dce8a@mail.gmail.com> (raw)
In-Reply-To: <m3ekal1s8h.fsf@kfs-l.imdomain.dk>
On 6/29/05, Kim F. Storm <storm@cua.dk> wrote:
> IMO, we should change all of them, but is this really the time?
Release-wise? That's not a destabilizing change, I think... And
certainly is not a new feature ;-)
--
/L/e/k/t/u
next prev parent reply other threads:[~2005-06-29 9:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-28 11:23 ?\ vs. ?\s Juanma Barranquero
2005-06-28 14:54 ` Kim F. Storm
2005-06-28 15:28 ` Juanma Barranquero
2005-06-28 16:07 ` Juanma Barranquero
2005-06-29 8:29 ` Kim F. Storm
2005-06-29 9:48 ` Juanma Barranquero [this message]
2005-06-29 14:09 ` Juanma Barranquero
2005-06-29 14:11 ` Kim F. Storm
2005-06-30 1:44 ` Richard M. Stallman
2005-06-29 3:58 ` Richard M. Stallman
2005-06-29 9:47 ` Juanma Barranquero
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=f7ccd24b0506290248455dce8a@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=emacs-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).