unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Brockman <daniel@brockman.se>
Subject: Re: non-break-space in tutorial
Date: Tue, 07 Jun 2005 19:12:22 +0200	[thread overview]
Message-ID: <874qca147d.fsf@wigwam.deepwood.net> (raw)
In-Reply-To: 873bruw4nw.fsf@jurta.org

Juri Linkov <juri@jurta.org> writes:

> So with the lack of support for buffer-local faces and with 
> changed treatment of `show-nonbreak-escape' we should rename 
> this variable to something like `show-no-break-space'.

You might as well make it `show-non-breaking-spaces' if you're 
going to rename it anyway.  The current name is ugly, and I think 
the name you're proposing is unnecessarily confusing.  It makes 
you wonder what the ``break space'' is.

[...]

> Since we can't predict in which context and modes users might 
> encounter non-breaking spaces, we should make their default 
> highlighting as least annoying as possible.

I read that as a typo for ``at least as annoying as possible.'' 
:-)
But now that I think about it, ``as little annoying as possible'' 
sounds slightly awkward too.  What is the correct way to say it?
                                   
-- 
Daniel Brockman <daniel@brockman.se>

  reply	other threads:[~2005-06-07 17:12 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 [this message]
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
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=874qca147d.fsf@wigwam.deepwood.net \
    --to=daniel@brockman.se \
    /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).