unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: command fill-paragraph deletes leading Umlauts if line begins with space
Date: Fri, 24 Dec 2004 09:32:58 -0500	[thread overview]
Message-ID: <E1ChqV0-0006VQ-WC@fencepost.gnu.org> (raw)
In-Reply-To: <E1ChQ3r-0002bn-Kf@neutrino.iwi.uni-sb.de> (message from Ralf Angeli on Thu, 23 Dec 2004 11:19:11 +0100)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]

    A function in AUCTeX for doing indentation looks at whitespace syntax
    for finding the first non-whitespace character (and so does
    `back-to-indentation' in CVS Emacs).  That means it will skip the "Ü"
    and delete everything from the beginning of the line to and including
    the "Ü".

    I removed this code in CVS AUCTeX which now only uses
    `back-to-indentation'.  In Emacs 21.3 this function does not look at
    character syntax but simply skips spaces and tab characters at the
    beginning of a line.

If AucTeX specifically wants to skip just space and tab, it could do
that explicitly, rather than calling back-to-indentation.  That would
work in the latest Emacs.

We could look at trying to fix this by giving different syntax
values to the unibyte non-ASCII codes.  The problem is that
(I think) different non-ASCII coding systems would want different
syntax values.  However, making codes 200-377 all "word constituent"
might be better than making them all "whitespace".

       reply	other threads:[~2004-12-24 14:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1ChBF2-0004VS-00@h409.eml.org>
     [not found] ` <E1ChQ3r-0002bn-Kf@neutrino.iwi.uni-sb.de>
2004-12-24 14:32   ` Richard Stallman [this message]
2004-12-26 22:39     ` command fill-paragraph deletes leading Umlauts if line begins with space Ralf Angeli
2004-12-27  7:35       ` Eli Zaretskii
2004-12-27 10:15         ` Ralf Angeli
2004-12-27 18:06       ` Richard Stallman
2004-12-27 22:28         ` Stefan Monnier
2004-12-28  0:18           ` Kenichi Handa
2004-12-28  0:14         ` Kenichi Handa
2004-12-28 17:25           ` Richard Stallman
2004-12-29  1:17             ` Kenichi Handa
2004-12-29  9:23               ` Ralf Angeli
2005-01-06  7:50                 ` Kenichi Handa
2005-01-06  8:19                   ` Ralf Angeli
2005-01-06  8:55                     ` Kenichi Handa
2004-12-29 20:46               ` Richard Stallman
2005-01-06  7:41                 ` Kenichi Handa
2005-01-06 13:53                   ` Stefan Monnier
2005-01-07  0:00                     ` Kenichi Handa
2005-01-07 14:42                       ` Stefan Monnier
2005-01-07 16:32                         ` David Kastrup
2005-01-08  0:05                         ` Kenichi Handa
2005-01-08 23:53                           ` Stefan

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=E1ChqV0-0006VQ-WC@fencepost.gnu.org \
    --to=rms@gnu.org \
    --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).