6:50 p.m.
Off the http://www.xemacs.org/ page there is a link to Bill P's site
for GTK-Xemacs. That page is quite old and in no way reflects what I
know the status to be. Is there a better link to see what the status
is?
I'm considering switching from Athena to GTK. I'm just not sure what
isn't going to work right. Since this will be for daily/production
use I'd like to know without going through the effort of building and
installing. I can certainly live with some bugs/missing features; I
just need to know what they are.
On a related note, is there a bug list for xemacs? The main site has
a "search for problems" that just points to this list. Would setting
up something like bugzilla be usefull?
--
(__) Doug Alcorn (mailto:doug＠lathi.net http://www.lathi.net)
oo / PGP 02B3 1E26 BCF2 9AAF 93F1 61D7 450C B264 3E63 D543
|_/ If you're a capitalist and you have the best goods and they're
free, you don't have to proselytize, you just have to wait.
9:38 p.m.
Doug Alcorn wrote:
Off the http://www.xemacs.org/ page there is a link to Bill P's site
for GTK-Xemacs. That page is quite old and in no way reflects what
I know the status to be. Is there a better link to see what the
status is?
Les Schaffer has a page dedicated to fixing some GTK XEmacs bugs:
http://folks.astrian.net/godzilla/gtk-bugs.html
If it is worthwhile to maintain a page of known issues and
workarounds, yet no-one else wants to do it, then I volunteer.
I'm considering switching from Athena to GTK. I'm just not
sure
what isn't going to work right.
Setting gutter-buffers-tab-visible-p to nil in my custom-set-variables
form was about the only thing I've set because of GTK. There are
occaisional glitches in redisplay, but they are very minor. Hmm.
I've just noticed visible bell isn't.
Ultimately, the best way to find out what doesn't work right is to try
it.
On a related note, is there a bug list for xemacs? The main site
has a "search for problems" that just points to this list. Would
setting up something like bugzilla be usefull?
That's a good idea. I think simply having seperate bug-reporting
lists would be useful too (eg: xemacs-bugs and xemacs-beta-bugs).
--
John Paul Wallington
2:50 a.m.
>>>> "jpw" == John Paul Wallington
<jpw(a)shootybangbang.com> writes:
jpw> Doug Alcorn wrote:
> Off the http://www.xemacs.org/ page there is a link to Bill
P's
> site for GTK-Xemacs. That page is quite old and in no way
> reflects what I know the status to be. Is there a better link
> to see what the status is?
The basic status is that GTK is still experimental, and is not getting
much attention from the core team. Bill is apparently busy with day
job, but I'll be getting in touch with him, now that I'm less busy
with day job.
jpw> Les Schaffer has a page dedicated to fixing some GTK XEmacs
jpw> bugs: http://folks.astrian.net/godzilla/gtk-bugs.html
Right. We should link this on the home page ... done.
jpw> If it is worthwhile to maintain a page of known issues and
jpw> workarounds, yet no-one else wants to do it, then I
jpw> volunteer.
This is a "core" thing that I've fallen down on. I'll be standing
back up early next week. But since you've mentioned the V-word,
you'll be hearing from me. Don't go changing your e-mail address or
anything like that ;-)
> On a related note, is there a bug list for xemacs? The main
> site has a "search for problems" that just points to this list.
> Would setting up something like bugzilla be usefull?
Yes. I'm working on bugzilla, but what really needs to be done is to
put the backlog into it, and bugzilla does not seem to have an easy
way to do that.
jpw> That's a good idea. I think simply having seperate
jpw> bug-reporting lists would be useful too (eg: xemacs-bugs and
jpw> xemacs-beta-bugs).
Used to be that way. Effectively they went to /dev/null. Right now
there are about 20 user/tester-oriented addresses ＠xemacs.org, and
nobody really paying much attention to any of them[1] except xemacs-beta
and xemacs-winnt. Switching to aliasing the ones that were being
ignored to xemacs-beta at least gets them some attention.
Again, bugzilla doesn't like getting email, although I hear it's quite
persistent about _sending_ it.
Footnotes:
[1] There are good reasons for that; responding to about half of
those reports typically was profitless. Most of the rest was very
small net gain, mostly accruing to the reporters who got personal
answers to FAQs. :-( The good bug reports come from xemacs-beta &
xemacs-winnt.
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Don't ask how you can "do" free software business;
ask what your business can "do for" free software.
5:09 p.m.
John:
If it is worthwhile to maintain a page of known issues and
workarounds, yet no-one else wants to do it, then I volunteer.
lets carry on as we have and work this together. i'll promise to add
your stuff to my page more quickly. or if you wanna run it, take my
page and i'll feed you.
les schaffer
6:17 p.m.
Les Schaffer wrote:
John:
> If it is worthwhile to maintain a page of known issues and
> workarounds, yet no-one else wants to do it, then I volunteer.
lets carry on as we have and work this together. i'll promise to add
your stuff to my page more quickly. or if you wanna run it, take my
page and i'll feed you.
eek! My comment *did* come out wrong! I thought you wanted to limit
the scope of the bug hunt and concentrate on the floaty buffer tab and
other major weirdness, in which case a separate status and workarounds
page makes some sense. If you don't, it doesn't, and apologies: I
certainly *didn't* mean to suggest you didn't want to do it.
--
John Paul Wallington
6:31 p.m.
eek! My comment *did* come out wrong!
nope, no offense taken!
I thought you wanted to limit the scope of the bug hunt and
concentrate on the floaty buffer tab and other major weirdness
hmmm, hadnt thought of that ... tempting!!!! ;-)
in which case a separate status and workarounds page makes some
sense. If you don't, it doesn't, and apologies: I certainly
*didn't* mean to suggest you didn't want to do it.
i'm a big believer in "2 heads are better than 1". I think you might
be a little timelier with stuff than i might be. so i can feed you
updates on stuff i work on if you wanna handle the overall page.
otherwise, feed me stuff, and i will place it straight onto my page.
les
8397
days inactive
8398
days old
5 comments
4 participants
participants (4)
-
Doug Alcorn -
John Paul Wallington -
Les Schaffer -
Stephen J. Turnbull