11:48 a.m.
Giacomo Boffi writes:
Norbert Koch writes:
> I have a pre-build package VM-7.26 still on my machine.
installed, now all is ok (with regard to VM of course)
imo, VM-7.26 is a better package than the stable package, VM-7.22
- is based on the last (maybe the greatest...) of Kyle's VM,
- has many xemacs specific bug fixes wrt coding systems
- has many xemacs specific bug fixes wrt windows configuration
why don't put it where it deserves, id est, among the stable packages?
are there any objection to such a simple move?
thank you all for all the helping, ciao
g
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
11:58 a.m.
New subject: VM packages
* Giacomo Boffi <giacomo.boffi(a)polimi.it>:
imo, VM-7.26 is a better package than the stable package, VM-7.22
[...]
why don't put it where it deserves, id est, among the stable packages?
are there any objection to such a simple move?
I copy a complete set of pre-released packages to the official web site.
The main reason for this is the package database which must be in sync
with the release packages. At the moment it's not possible to build all
packages, so I haven't released new packages for a long time.
From your remarks I take it some work will have to be done on VM
before
we can release it again :-)
norbert.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
6:06 p.m.
New subject: VM packages
Norbert Koch writes:
>From your remarks I take it some work will have to be done on VM
before
we can release it again :-)
No, as Giacomo says it's worth releasing 7.26 to succeed 7.22.
V8 is totally hosed, though, sad to say. It's barely usable because
it errors all over the place for signatures, window management is
badly broken, the Emacs point gets out of synch with VM's current
message all the time (literally "all"; there are only a few operations
that can be done that I know will preserve "point on current
message"). It really shouldn't have been put into XEmacs CVS trunk;
we ought to have a branch policy for major rewrites like this.
Branches aren't easy in CVS, though. Poor Uwe is having quite a time!
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
6:03 p.m.
New subject: VM packages
Stephen J. Turnbull writes:
Norbert Koch writes:
> >From your remarks I take it some work will have to be done on VM before
> we can release it again :-)
No, as Giacomo says it's worth releasing 7.26 to succeed 7.22.
V8 is totally hosed, though, sad to say. It's barely usable because
it errors all over the place for signatures, window management is
badly broken, the Emacs point gets out of synch with VM's current
message all the time (literally "all"; there are only a few operations
that can be done that I know will preserve "point on current
message").
I still contend that this point problem is a 21.5 problem and *not* a
vm problem. Vm8 works fine for me under xemacs 21.4 & emacs 22.
21.5 is still a no-starter for me because of the flashing redisplay.
It really shouldn't have been put into XEmacs CVS trunk; we
ought
to have a branch policy for major rewrites like this.
This big of a jump, yes.
--
Jeff Miller
jmiller(a)cablespeed.com
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
2:24 a.m.
New subject: VM packages
Jeff Miller writes:
Stephen J. Turnbull writes:
> V8 is totally hosed, though, sad to say. It's barely
usable because
> it errors all over the place for signatures, window management is
> badly broken, the Emacs point gets out of synch with VM's current
> message all the time (literally "all"; there are only a few operations
> that can be done that I know will preserve "point on current
> message").
I still contend that this point problem is a 21.5 problem and *not* a
vm problem. Vm8 works fine for me under xemacs 21.4 & emacs 22.
It's a VM problem because I have no clue how to debug it and don't
have time to get down and dirty with the maze of twisty little
passages all alike that is the VM object system, and nobody else
(including Robert) seems to care. The "point gets lost" problems I
suspect probably have something to do with the fact that window
configurations are no longer special objects, but that is unlikely to
be reverted. XEmacs may be able to do something to help, but I
suspect changes will need to be made in VM, too.
The problems with signatures is not a 21.5 problem, I would bet. They
are "we didn't bother to distribute implicitly loaded functionality"
issues.
21.5 is still a no-starter for me because of the flashing redisplay.
What flashing redisplay? Is it in the bug tracker?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
11:41 p.m.
New subject: VM packages
Stephen J. Turnbull writes:
It's a VM problem because I have no clue how to debug it and don't
have time to get down and dirty with the maze of twisty little
passages all alike that is the VM object system, and nobody else
(including Robert) seems to care. The "point gets lost" problems I
suspect probably have something to do with the fact that window
configurations are no longer special objects, but that is unlikely to
be reverted. XEmacs may be able to do something to help, but I
suspect changes will need to be made in VM, too.
Lot's of things went haywire in vm when the window configuration stuff
when from C -> lisp, so you may be right.
The problems with signatures is not a 21.5 problem, I would bet.
They
are "we didn't bother to distribute implicitly loaded functionality"
issues.
I guess you mean gpg signatures? I normally don't use those.
> 21.5 is still a no-starter for me because of the flashing
redisplay.
What flashing redisplay? Is it in the bug tracker?
No, it's not in the bug tracker, it doesn't look like any vm issues
are in the bug tracker.
When I go to a previous or next email, the entire frame blanks and
redraws.
jeff
--
Jeff Miller
jmiller(a)cablespeed.com
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
12:12 a.m.
New subject: VM packages
>>>> "Jeff" == Jeff Miller
<jmiller(a)cablespeed.com> writes:
Jeff> When I go to a previous or next email, the entire frame blanks and
Jeff> redraws.
I suspect this is related to the redisplay issue with dired that I
described in
http://calypso.tux.org/pipermail/xemacs-beta/2008-June/014509.html.
mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
5737
days inactive
5754
days old
6 comments
5 participants
participants (5)
-
Giacomo Boffi -
Jeff Miller -
Mike Kupfer -
Norbert Koch -
Stephen J. Turnbull