From: Richard Stallman <rms@gnu.org>
Cc: juri@jurta.org, monnier@iro.umontreal.ca, gaetan.leurent@ens.fr,
emacs-devel@gnu.org
Subject: Re: Auto-fill-mode bug: unbreakable space lost
Date: Sat, 26 Mar 2005 22:52:47 -0500 [thread overview]
Message-ID: <E1DFOpT-00008X-69@fencepost.gnu.org> (raw)
In-Reply-To: <200503251723.j2PHNQln009118@beta.mvs.co.il> (ehud@unix.mvs.co.il)
I second that. May be we should define the shift space (S-SPC) key to
produce the non-breaking space in the current charset (I did it for
Hebrew - iso8859-8).
That could be a good idea, but it could also conceivably cause
problems. Maybe some people type spaces while holding down the shift
key and expect it to be an ordinary space (such as, between words that
are all caps).
I don't know whether this will turn out to be a real problem or not.
I just see that it could be one.
You can use C-x 8 SPC and C-x 8 - to produce these characters, which
together with unify-8859-on-encoding-mode (which is the default) gives you
the right characters for your charset.
I was thinking that C-x 8 is obsolete, but if this is the best way to
do that, maybe it means C-x 8 is not obsolete. What do people think?
next prev parent reply other threads:[~2005-03-27 3:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 20:08 Auto-fill-mode bug: unbreakable space lost Gaetan Leurent
2005-03-22 20:29 ` Stefan Monnier
2005-03-23 0:30 ` Kevin Rodgers
2005-03-23 0:44 ` David Kastrup
2005-03-23 13:34 ` Stefan
2005-03-23 19:19 ` Gaetan Leurent
2005-03-23 19:57 ` Stefan Monnier
2005-03-24 12:10 ` Gaetan Leurent
2005-03-24 13:52 ` Stefan
2005-03-24 14:05 ` Stefan
2005-03-24 21:33 ` Juri Linkov
2005-03-25 17:23 ` Ehud Karni
2005-03-25 18:08 ` Andreas Schwab
2005-03-25 18:22 ` Stefan Monnier
2005-03-27 3:52 ` Richard Stallman [this message]
2005-03-27 5:30 ` Miles Bader
2005-03-28 16:25 ` Richard Stallman
2005-03-28 18:45 ` David Kastrup
2005-03-27 5:34 ` Miles Bader
2005-03-28 16:25 ` Richard Stallman
2005-03-28 20:52 ` Miles Bader
2005-03-27 10:56 ` Eli Zaretskii
2005-03-29 0:51 ` Gaetan Leurent
2005-03-29 14:51 ` Evil Boris
2005-03-29 15:55 ` Gaetan Leurent
2005-03-30 0:04 ` Richard Stallman
2005-03-26 2:17 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2005-04-03 18:56 EvilborisNet
2005-04-04 19:05 Stefan Monnier
2005-04-05 4:22 ` 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=E1DFOpT-00008X-69@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gaetan.leurent@ens.fr \
--cc=juri@jurta.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 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).