unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Auto-fill-mode bug: unbreakable space lost
Date: Wed, 23 Mar 2005 14:57:46 -0500	[thread overview]
Message-ID: <jwvsm2mkulu.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <qlkmzsuw4os.fsf@clipper.ens.fr> (Gaetan Leurent's message of "Wed, 23 Mar 2005 20:19:31 +0100")

> The current behavior annoys me because I make the French quotation mark
> '«' insert '«  »' and put the point between the NBSP, because french
> quotations should be « like this », and if auto-fill mode gets in my way
> while I fill the quotation, I loose the NBSP.

I find NBSP to be a source of too many problems, so I think it should be
kept for those rare cases where the unbreakability of a space isn't obvious
from context.

Try (add-hook 'fill-nobreak-predicate 'fill-french-nobreak-p)
Note that fill-french-nobreak-p is new in Emacs-CVS.
   
> Concerning whitespace, a quick 'fgrep '" \t"' -r .' in the emacs source
> shows quite lot of place where this is still used to match whitespace
> instead of using the whitespace syntax, even in fill.el, so it's a bit
> confusing...

Indeed, it's messy.


        Stefan

  reply	other threads:[~2005-03-23 19:57 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 [this message]
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
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=jwvsm2mkulu.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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).