Andreas Röhler <andreas.roehler(a)online.de> writes:
while I'm following that rationale not to delete formfeeds: user might
do still different considerations.
What about a customizable chars-list specifying what as whitespace
should be considered?
Indicating chars in a list is much easier than changing syntax for most
of users IMO.
This is the exact code from Emacs 23, weaknesses and all.
I could generate a patch for Emacs, but I can't do the formal copyright
assignment due to my job. In practice, deleting syntactic spaces covers
a very high percentage of usage. I've never seen anyone complain.
(Although I haven't gone looking.)
> + (save-match-data
> + (if (looking-at ".*\f")
> + (goto-char (match-end 0))))
It might mean: whitespaces followed by a formfeed will be preserved.
Seems not reasonable.
You're right. The emacs practice seems to a single formfeed on a line
to break a file into sections. The real problem is that you can't
contruct a regexp for \s- minus formfeed.
And it gets more complicated with Unicode whitespace:
http://en.wikipedia.org/wiki/Whitespace_character#Unicode
I'd like to include for sure. Do syntax-tables support Unicode?
Not in XEmacs, but apparently in Emacs. Unicode has bunch of different
sized spaces! And punctuation. For XEmacs, We'd probably have to wait
until we use only unicode internally. Doing syntax for all possible
charsets is a lot of work.
I'm going to go with the Emacs definition, and avoid the higher levels
of correctness.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta