From: Miles Bader <snogglethorpe@gmail.com>
Cc: emacs-devel@gnu.org, miles@gnu.org
Subject: Re: non-break-space in tutorial
Date: Wed, 8 Jun 2005 11:37:37 +0900 [thread overview]
Message-ID: <fc339e4a050607193764e2c3e5@mail.gmail.com> (raw)
In-Reply-To: <87wtp5hapg.fsf@jurta.org>
On 6/8/05, Juri Linkov <juri@jurta.org> wrote:
> The new display method uses no less familiar notation. The underlined
> space looks very like the underscore character used in programming
> languages to represent a space between inseparable words inside identifiers.
Huh? Such a representation is hardly "familiar" as a way of
representing funny characters in Emacs. It may not be unreasonable
once it's explained, but that's not what I'm disputing.
> I never claimed it to be undisputed fact. On the contrary, in the
> mail I sent after installing the patch I asked all people to try the
> new highlighting for some time period with the intention to hear all
> opinions about it afterwards.
The standard method for dealing with potentially controversial changes
is to suggest a change, and solicit feedback until a reasonable
concensus is reached, or the maintainer makes a decision. This is
annoying, I know, but there's a reason for it: if everyone just
installed their disputed patches "for people to try out", there would
be chaos, something which we especially want to avoid at the moment.
Changes once made have a way of sticking around even if they were
originally deemed temporary.
-Miles
--
Do not taunt Happy Fun Ball.
next prev parent reply other threads:[~2005-06-08 2:37 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 23:19 non-break-space in tutorial Stefan Monnier
2005-05-27 11:57 ` Juri Linkov
2005-05-27 13:07 ` Paul Pogonyshev
2005-05-28 11:53 ` Richard Stallman
2005-05-29 16:08 ` Juri Linkov
2005-05-29 17:40 ` Eli Zaretskii
2005-05-30 8:48 ` Juri Linkov
2005-05-30 16:08 ` Eli Zaretskii
2005-05-31 4:18 ` Richard Stallman
2005-05-31 5:17 ` Miles Bader
2005-05-31 8:56 ` Kim F. Storm
2005-05-31 17:47 ` Richard Stallman
2005-06-06 12:52 ` Juri Linkov
2005-06-06 14:07 ` Stefan Monnier
2005-06-07 0:17 ` Miles Bader
2005-06-07 15:33 ` Juri Linkov
2005-06-07 17:12 ` Daniel Brockman
2005-06-08 0:59 ` Juri Linkov
2005-06-08 2:22 ` Henrik Enberg
2005-06-07 22:31 ` Miles Bader
2005-06-07 23:12 ` Gaëtan LEURENT
2005-06-07 23:53 ` Miles Bader
2005-06-08 0:01 ` Luc Teirlinck
2005-06-08 0:17 ` Miles Bader
2005-06-08 23:29 ` Gaëtan LEURENT
2005-06-08 23:57 ` Juri Linkov
2005-06-07 23:52 ` Juri Linkov
2005-06-08 0:17 ` Miles Bader
2005-06-08 0:57 ` Juri Linkov
2005-06-08 2:37 ` Miles Bader [this message]
2005-06-08 8:35 ` Kim F. Storm
2005-06-08 8:53 ` Miles Bader
2005-06-08 16:05 ` Stefan Monnier
2005-06-08 20:47 ` Juri Linkov
2005-06-08 21:25 ` Kim F. Storm
2005-06-08 22:53 ` Stefan Monnier
2005-06-09 14:40 ` Richard Stallman
2005-06-09 15:29 ` David Kastrup
2005-06-09 16:44 ` Juanma Barranquero
2005-05-28 11:53 ` Richard Stallman
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=fc339e4a050607193764e2c3e5@mail.gmail.com \
--to=snogglethorpe@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=miles@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).