Re: The future of XEmacs
Mike Kupfer writes:
Stephen J. Turnbull wrote:
> people who are still using 21.4 and change to 21.5 experience a lot of
> small regressions.
Are these regressions related to multilingual support?
Some are, most are not. The ones that bite me most frequently are the
coding system defaults issue and some issues with window configurations
(Mike says they're due to programs depending on undefined or wrong
behavior, but users will perceive them as regressions), including
cursor vs current message desynchronization in VM and a redisplay bug
such that resizing the initial frame bigger in the init file leaves it
half-blank.
There are a bunch of others that might or might not be regressions, I
don't use 21.4 enough to remember its behavior. Specifically the
annoying "wrong type error: stringp, nil" that pops up all over the
place, and the startup noise about loading the "Guide".
The only regression I notice is the occasional rendering glitch
with Xft, but I wouldn't propose enabling Xft by default.
It's really not acceptable to not have antialiased fonts for Unicode
support anymore, at least not for Asian fonts character sets. I guess
it's OK for those who only occasionally see Asian characters, but I
can't use a non-Xft XEmacs anymore; it's just too painful.
Oh, and there's a lot more noise at startup about package
shadows.
Noise about shadows is a user issue. There shouldn't be any shadows
in a normal user's configuration. Only developers should have shadows
(and maybe the occasional shadow due to mission critical packages
where user follows upstream).
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta