Ar an chéad lá is fiche de mí Méan Fómhair, scríobh Stephen J. Turnbull:
> Aidan Kehoe writes:
>
> > It should be possible to avoid this in VM. AIUI it’s a result of
> > doing coding system and base64, quoted-printable decoding on
> > displayed text, which will always cause a redisplay flash if the
> > relevant text is being shown. (Text is inserted, more text is
> > deleted). It would make more sense to do all the decoding somewhere
> > that's not being redisplayed, and only show the text when the
> > decoding is finished.
>
> I guess you could double buffer, have one buffer for the current view
> (or preview) and another where the work is being done. Is that what
> you have in mind?
Yeah. I’ve experimented a little but haven’t yet got it to work.
--
On the quay of the little Black Sea port, where the rescued pair came once
more into contact with civilization, Dobrinton was bitten by a dog which was
assumed to be mad, though it may only have been indiscriminating. (Saki)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

In article <18149.58079.498563.234436(a)puma.r.npc.de> Joachim Schrod <jschrod(a)acm.org> writes:
>>>>>> "MS" == Michael Sperber <sperber(a)informatik.uni-tuebingen.de> writes:
>MS> So before I sink more work into this: Can you confirm that the
>MS> "flicker" problem seen on 21.5 also occurs with the new VM?
>
>I don't know if I fully understood what Julian's "flicker" problem
>is actually... Thus, let me rephrase the situation as I observe it.
>
>When one moves from one message to another (i.e., evaluates
>#'vm-next-message), the frame goes completely white and is then
>rebuild. Is that the "flicker" problem of Julian? This is the same in
>VM 7.17/7.19 and VM 8.0. I'd think that this behaviour was already
>there when I still used XEmacs 21.4; I don't remember any change here.
>AFAIU, that's done during the construction of the mail's presentation
>(MIME decoding and so).
Yes, I guess that's what I mean. On 21.5, it is very visible, and very
annoying - even on a tty frame, even on a very fast machine. On 21.4,
it's not visible at all on any machine I use, as far as I can see, so
I don't know whether it even happens.
I suppose I could put them under xscope to see what's actually
happening to the window!
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

Hello
Unfortunately it seems no longer possible to search the mailing list,
for I am sure that issue has been discussed.
It is as follows, I run ediff-regions-wordwise and I want to print
the resulting buffers via ps-print-buffer-with-faces, the buffers are
print, but the faces don't appear.
What might be the problem?
regards
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

Hello,
After three and half years of snail-pace porting work, I think the new vc from
the unsupported area is now in a state where it makes sense to start pushing
it towards the regular XEmacs packages tree.
For those unfamiliar with it, the new vc consists of vc*.el and log-edit.el
from GNU Emacs 22, and mercurial.el and vc-git.el from respective upstreams.
Compared to the current vc package, new supported backends are GNU Arch, GIT,
Meta-CVS, Mercurial, and Subversion.
I've been using the new vc package exclusively for quite some time now, but as
I'm not a hardcore vc user and use only CVS, Subversion, Mercurial and GIT
(two latter only now and then), it is expected that there are some rough
edges here and there. Additionally, the current pcl-cvs, vc-cc and
prog-modes (p4.el) packages have been only compile tested against the new vc.
I've done most of the testing with XEmacs 21.5, but have tried to be careful
to get it to work with 21.4 too.
The diff against the old vc is so large that I don't think it would be useful
to post a diff here or to xemacs-patches.
I suggest we proceed like this:
1) Commit the new vc to xemacs-packages/vc (AI: me)
2) Clean up no longer needed stuff from diff-mode.el (AI: me)
3) Push the new package to the experimental area (AI: Norbert)
4) Let it stay in the experimental area until issues with pcl-cvs, vc-cc, and
p4.el have been ironed out or reported to work as-is
(AI: users/developers/hackers of pcl-cvs, vc-cc and p4.el, I'm available to
help out to the extent I can)
I've prepared steps 1 and 2, they're just a "cvs ci" away. Thoughts?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta