unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: Emacs-Devel <emacs-devel@gnu.org>
Subject: Re: should non-breaking space chars act as whitespace for Lisp?
Date: Sat, 16 Jun 2007 22:42:50 +0200	[thread overview]
Message-ID: <85sl8rljg5.fsf@lola.goethe.zz> (raw)
In-Reply-To: <EIENLHALHGIMHGDOLMIMEEJNDCAA.drew.adams@oracle.com> (Drew Adams's message of "Sat\, 16 Jun 2007 13\:32\:49 -0700")

"Drew Adams" <drew.adams@oracle.com> writes:

> We should be able to find some way to make things clear to a user
> that s?he needs to convert nonbreakable spaces to spaces, or else we
> should treat nonbreakable spaces as whitespace for Lisp code. I
> don't have a strong opinion about the solution, but I think a
> problem has been pointed out to which we should find a good
> solution.

If we treat nonbreakable spaces as whitespace when people cut&paste
from something like KNode, this means that the mangling of spaces will
go unnoticed.  Since they can occur not only in code itself but also
in strings and character constants, this is an excessively bad idea.

It is better when the code breaks completely rather than when it works
superficially, but delivers different results.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2007-06-16 20:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-16 19:45 should non-breaking space chars act as whitespace for Lisp? Drew Adams
2007-06-16 19:51 ` David Kastrup
2007-06-16 20:32   ` Drew Adams
2007-06-16 20:42     ` David Kastrup [this message]
2007-06-17  8:54       ` Richard Stallman
2007-07-23 18:06       ` Richard Stallman
2007-06-16 21:29     ` Stephen Berman
2007-06-16 22:27       ` Drew Adams
2007-06-16 23:39         ` Stephen Berman
2007-06-17  8:54 ` 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=85sl8rljg5.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=drew.adams@oracle.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).