Reviving this thread in view of active interest in scheduling a public
release on both xemacs-beta and xemacs-review.
[Is there a Lisp function for getting the archive URL from a message
ID? Actually doing the searches by hand is kinda painful (for some
reason recently my HTTP connectivity has sucked, I think it's local
network mismanagement). If I could just queue them up to be dumped in
a buffer it would be cool.]
Since there's a lot of stuff here, I suggest that if you have issues
to add, can confirm that one has been resolved, or want to say that a
particular issue is irrelevant to a near-future release, do it in this
If you want to discuss any of the particular points, try to start a
new thread (or reply to an existing alternative thread).
Gunnar Everman has posted several BTS reports; I guess those should be
at least evaluated and presumably fixed before release.
Gunnar (if you're watching), do you have a summary handy, or should I
go filter the archives?
The John A Turner <turner(a)blueskystudios.com> list from
o the dired customize prob reported here remains:
Fixed, per Charles Waldman and Michael Sperber. A package issue,
anyway, but dired/efs are too important to the core to ignore.
I believe this fix has been applied in the current dired package?
o focus being lost after pressing Done in a Customize buffer - I still
see the problem on both Irix and win32 - I do use focus-follows-mouse
o the weirdness in Motif buttons, both in dialogs and in Customize
buffers - best report was this one, which has pics:
giacomo boffi <giacomo.boffi(a)polimi.it> in
o faces bold, italic, bold-italic don't react to size changes
Raymond Toy <toy(a)rtp.ericsson.se>:
o When fontifying a buffer, the progress bar moves very very
slowly and fontification takes forever (> many seconds).
However, if I just move the mouse around in the window, the
progress bar zips by very quickly, and fontification finishes in
less than a second.
o A possibly related problem: I start up xemacs and gnus from the
command line and have it iconified. It gets stuck somewhere
loading up something. As soon as I deiconify it, it zips
Raymond Toy's 21.2.3 on Solaris/GCC 2.95.2 crashes:
<200011072055.PAA22167(a)edgedsp4.ericsson.COM> (and thread)
My own agenda for Mule (not previously published), no particular
o Audit for synchs and feature additions that don't work with Mule
(eg, people have patched/intend to patch smtpmail and ps-print
in ways that cause data loss and other wastage under Mule)
o Fix the autodetection so that only the most common encodings for
each environment are autodetected in that environment by default;
if there is no language environment set, autodetection is not done.
This is a noticable semantic change but at the current pace of
release we should do it for the next release and hope most Mule
users set language environment.
o Partial Windows 12xx support for many values of `xx'.
o Windows 12xx graphic glyph support. (Can be done any time.)
o (Desirable) Update the fill code, partial synch to FSF 20.7, and
fix the kinsoku trailing-whitespace-is-significant bug (FSF still
has it). Probably will take time to shake out, though.
>>>> "Hrvoje" == Hrvoje Niksic
Hrvoje> I'm also worried by the portable dumping. That part seems
Hrvoje> to have reached the mythical 80%/20% border where it
Hrvoje> _appears_ to be finished, but in reality is far from that.
Hrvoje> (Specifically, there's no alternative for purespace,
Hrvoje> it seems to consume a lot more memory, and
Hrvoje> it seems to be slower.)
>>>> "Troy" == Troy Noble
<troy.noble(a)channelpoint.com> writes in
Hrvoje> The one good consequence of the core/packages separation
Hrvoje> is that releasing XEmacs is not as hard as it used to be.
Are the bad consequences relevant to the issues list, for either
fixing or improvement, or is there absolutely nothing that can be done
about them without remerging the packages into the core?
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_________________ _________________ _________________ _________________
What are those straight lines for? "XEmacs rules."