From: steve@miranova.com (Steven L. Baur)
Subject: Re: Latest XEmacs lossage in sgnus 0.15
Date: 25 Nov 1995 20:12:55 -0800 [thread overview]
Message-ID: <m2ybt4f1yw.fsf@diana.miranova.com> (raw)
In-Reply-To: Jens Lautenbacher's message of 25 Nov 1995 17:45:00 -0800
> c) you can not browse a group of the killed list.
I verified that. Probably related is the new bug (from 0.1[345])
where nnvirtual groups cannot be created.
Adding to your list: (In no particular order)
The dribble file never gets autosaved (new with 0.13). The loser with
this one is the erroneous (for XEmacs) (setq buffer-file-name ...)
replacing the valid (set-visited-file-name ...) in
gnus-dribble-read-file.
nnheader-insert-head (used by all the local file routines) exercises
an XEmacs GC bug. I have a patch for this, but it breaks ange-ftp
stuffs.
Entry to topics mode fails, at least with a gnus-group-topics string
that used to work with 0.14. Of course, since the text-properties get
screwed up by an XEmacs bug, gnus-topics has never completely worked.
Nnvirtual groups have failed to behave in any reasonable fashion since
0.12. (Probably some wierd XEmacs problem since they work for Lars).
Pseudo-article/dummy article default format strings do not contain the
necessary magic to have mouse highlight enabled.
> Any help or suggestions where to start debugging?
The easiest would be problems introduced since 5.0.12. The lack of
highlighting you described in b) might be the most rewarding. I smell
an XEmacs bug there (I've noticed analogous behavior from time to
time in other places), but cannot as yet prove it.
--
steve@miranova.com baur
prev parent reply other threads:[~1995-11-26 4:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-25 19:13 William Perry
1995-11-25 21:55 ` Steven L. Baur
1995-11-25 22:30 ` Steven L. Baur
1995-11-26 0:30 ` William Perry
1995-11-26 1:45 ` Jens Lautenbacher
1995-11-26 4:12 ` Steven L. Baur [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2ybt4f1yw.fsf@diana.miranova.com \
--to=steve@miranova.com \
/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.
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 NNTP newsgroup(s).