12:50 a.m.
cvs updated the latest beta about an hour ago...
no i have a vm session going, and at one point the progress gauge came
up (fontifying)
now I'm left with some odd remnants of the gauge as shown in the attachment
this is redhat linux 6.1, pretty much just did a ./configure
Jeff
11:01 p.m.
At 07:50 PM 8/19/00 -0400, Jeff Miller wrote:
now I'm left with some odd remnants of the gauge as shown in the
attachment
This looks to be the same as the tab display oddities. This patch should
fix most of the problems although I am still seeing some strangeness when
selecting a tab.
andy
2000-08-21 Andy Piper <andy(a)xemacs.org>
* glyphs-x.c (x_map_subwindow): Minor optimization - only map the
window if it is not already displayed.
* glyphs-msw.c (mswindows_map_subwindow): only map the window if
it is not already displayed.
* window.c (Fset_window_configuration): don't reset the frame
cache.
* glyphs.c (unmap_subwindow_instance_cache_mapper): only remove
instances from the frame cache if we are actually finalizing them.
(reset_frame_subwindow_instance_cache): reset frame cache only
after unmapping everything.
(map_subwindow): set displayed flag after mapping.
--------------------------------------------------------------
Dr Andy Piper
Principal Consultant, BEA Systems Ltd
4:13 a.m.
>>>> "AP" == Andy Piper <andy(a)xemacs.org>
writes:
AP> At 07:50 PM 8/19/00 -0400, Jeff Miller wrote:
> now I'm left with some odd remnants of the gauge as shown in
the attachment
AP> This looks to be the same as the tab display oddities. This patch should
AP> fix most of the problems although I am still seeing some strangeness when
AP> selecting a tab.
that did seem to fix most of it. but i was still getting some of the
same lossage when a very large file was fontified.
jeff
8:22 a.m.
At 11:13 PM 8/21/00 -0400, Jeff Miller wrote:
that did seem to fix most of it. but i was still getting some of the
same lossage when a very large file was fontified.
Do you mean outside of VM? What's "very large"?
Thanks
andy
--------------------------------------------------------------
Dr Andy Piper
Principal Consultant, BEA Systems Ltd
2:38 a.m.
>>>> "AP" == Andy Piper <andy(a)xemacs.org>
writes:
AP> At 11:13 PM 8/21/00 -0400, Jeff Miller wrote:
> that did seem to fix most of it. but i was still getting some of
the
> same lossage when a very large file was fontified.
Hello Andy,
AP> Do you mean outside of VM?
yes, outside of vm. I have not gotten any within vm since i added
your patch.
here is the scenario. I have saved of 2 two web pages which have one
uuencoded file split between them.
so i bring each into a buffer, remove the html from the top and bottom
of each file.
then i "insert-buffer" the 2nd file into the first.
then i do several "replace-strings" to change things like & ->
&
and so on.
finally, i do a "kill-rectangle" on about a 4 character indentation of
the whole uuencoded data.
i am not sure if it's order i'm doing things in, but usually at some
point I will have remnants of the progress gauge at the bottom of the
buffer. This particular file is coming up in Fundamental mode, but i
have font-lock turned on for just about all editing modes.
AP> What's "very large"?
looks like it starts at 421k and by the time I've down all the
replacing and snipping, it's 312k.
Jeff
11:53 a.m.
At 09:38 PM 8/22/00 -0400, Jeff Miller wrote:
yes, outside of vm. I have not gotten any within vm since i added
your patch.
Although I have not see this it made me think about why it might be
happening and I found a logic error in the window config code. Please
update from CVS and see if it still occurs. If it still occurs please
recompile window.c with BROKEN_SUBWINDOW_REDISPLAY defined and see if that
fixes it.
Thanks
andy
--------------------------------------------------------------
Dr Andy Piper
Principal Consultant, BEA Systems Ltd
1:39 a.m.
>>>> "AP" == Andy Piper <andy(a)xemacs.org>
writes:
AP> At 09:38 PM 8/22/00 -0400, Jeff Miller wrote:
> yes, outside of vm. I have not gotten any within vm since i
added
> your patch.
AP> Although I have not see this it made me think about why it might
AP> be happening and I found a logic error in the window config
AP> code. Please update from CVS and see if it still occurs.
cvs updated around 2300 GMT. I still get the problem, in fact, worse
than with the patch you had sent before.
AP> If it still occurs please recompile window.c with
AP> BROKEN_SUBWINDOW_REDISPLAY defined and see if that fixes it.
Tried this, and no effect.
In fact, it doesn't seem to be related to size of the fontified buffer
at all. I can just bring the small (3.1k) file into the (new xemacs)
buffer and it triggers the remnant. I can bring the larger of the
two files (420k) into a buffer and it doesn't trigger it at all.
my crazy hypothesis: there is some crazy mix of characters in the
uuencoded mess that is tripping up font lock and it bails. Perhaps
some error condition occurs then that freaks out the progress gauge.
i don't claim to know how that all interacts, but maybe font lock
bails before the widget is fully realized?
just my wild ass guess.... :-)
jeff
9:05 p.m.
Can you send me the file that cause the problem?
Thanks
andy
At 08:39 PM 8/23/00 -0400, Jeff Miller wrote:
>>>>> "AP" == Andy Piper
<andy(a)xemacs.org> writes:
AP> At 09:38 PM 8/22/00 -0400, Jeff Miller wrote:
>> yes, outside of vm. I have not gotten any within vm since i added
>> your patch.
AP> Although I have not see this it made me think about why it might
AP> be happening and I found a logic error in the window config
AP> code. Please update from CVS and see if it still occurs.
cvs updated around 2300 GMT. I still get the problem, in fact, worse
than with the patch you had sent before.
AP> If it still occurs please recompile window.c with
AP> BROKEN_SUBWINDOW_REDISPLAY defined and see if that fixes it.
Tried this, and no effect.
In fact, it doesn't seem to be related to size of the fontified buffer
at all. I can just bring the small (3.1k) file into the (new xemacs)
buffer and it triggers the remnant. I can bring the larger of the
two files (420k) into a buffer and it doesn't trigger it at all.
my crazy hypothesis: there is some crazy mix of characters in the
uuencoded mess that is tripping up font lock and it bails. Perhaps
some error condition occurs then that freaks out the progress gauge.
i don't claim to know how that all interacts, but maybe font lock
bails before the widget is fully realized?
just my wild ass guess.... :-)
jeff
--------------------------------------------------------------
Dr Andy Piper
Principal Consultant, BEA Systems Ltd
5:04 a.m.
>>>> "AP" == Andy Piper <andyp(a)bea.com>
writes:
AP> Can you send me the file that cause the problem?
i had deleted it.
but i have come up with a simply recipe... and found another bug.
this is with about a week old xemacs from cvs... so maybe some of this
has been fixed. Basically everything is enabled, this is a
./configure, make beta
xemacs -vanilla
Options->Customize->Faces ( i selected default face)
now i have a customize buffer.
M-x font-lock-mode (the customize buffer)
i see the progress gauge come up for a split second and am left with
remmnants of the progress bar and the stop button
now, switch to the scratch buffer
now I have the set, save & done widgets, along with the progress bar
remmnants in the *scratch buffer*
Installation files attached
uname -a: Linux 24-216-39-123.hsacorp.net 2.2.17 #3 SMP Wed Sep 6 18:43:42 EDT 2000 i686
unknown
./configure '--package-path=/usr/local/lib/xemacs/packages-21.0'
XEmacs 21.2-b35 "Nike" configured for `i686-pc-linux'.
Compilation / Installation:
Source code location: /cvs/xemacs/xemacs
Installation prefix: /usr/local
Operating system description file: `s/linux.h'
Machine description file: `m/intel386.h'
Compiler: gcc -g -O3 -Wall -Wno-switch -Wpointer-arith -Winline
-Wmissing-prototypes -Wshadow
Relocating allocator for buffers: no
GNU version of malloc: yes
- Using Doug Lea's new malloc from the GNU C Library.
Window System:
Compiling in support for the X window system:
- X Windows headers location: /usr/X11R6/include
- X Windows libraries location: /usr/X11R6/lib
- Handling WM_COMMAND properly.
Using Lucid menubars.
Using Lucid scrollbars.
Using Motif dialog boxes.
Using Motif native widgets.
TTY:
Compiling in support for ncurses.
Compiling in support for GPM (General Purpose Mouse).
Images:
Compiling in support for GIF images (builtin).
Compiling in support for XPM images.
Compiling in support for PNG images.
Compiling in support for JPEG images.
Compiling in support for TIFF images.
Compiling in support for X-Face message headers.
Sound:
Compiling in support for sound (native).
Compiling in support for ESD (Enlightened Sound Daemon).
Databases:
Compiling in support for Berkeley database.
Compiling in support for LDAP.
Compiling in support for PostgreSQL.
- Using PostgreSQL header file: pgsql/libpq-fe.h
Internationalization:
Mail:
Compiling in support for "dot-locking" mail spool file locking method.
Other Features:
Compiling in support for dynamic shared object modules.
Compiling in support for extra debugging code.
WARNING: ---------------------------------------------------------
WARNING: Compiling in support for runtime error checking.
WARNING: XEmacs will run noticeably more slowly as a result.
WARNING: Error checking is on by default for XEmacs beta releases.
WARNING: ---------------------------------------------------------
5:41 a.m.
>>>> "Jeff" == Jeff Miller
<jmiller(a)cablespeed.com> writes:
Jeff> this is with about a week old xemacs from cvs... so maybe
Jeff> some of this has been fixed. Basically everything is
Jeff> enabled, this is a ./configure, make beta
Jeff> xemacs -vanilla
Options-> Customize->Faces ( i selected default face)
Jeff> now i have a customize buffer.
Jeff> M-x font-lock-mode (the customize buffer)
Jeff> i see the progress gauge come up for a split second and am
Jeff> left with remmnants of the progress bar and the stop button
Jeff> now, switch to the scratch buffer
Jeff> now I have the set, save & done widgets, along with the
Jeff> progress bar remmnants in the *scratch buffer*
I can't replicate this. The obvious difference between my setup and
yours is I use Lucid widgets, you're using motif. I think I can
probably do a Motif test but it'll be a day or two; I may not have the
libs installed.
Which variety and version of Motif?
My Installation follows.
uname -a: Linux tleepslib 2.2.10 #2 Thu Jun 24 19:22:23 JST 1999 i686 unknown
/coda/Projects/XEmacs/21.2-HEAD/configure
'--srcdir=/coda/Projects/XEmacs/21.2-HEAD' '--with-widgets=athena'
'--with-athena=3d' '--with-sound=none,nas' '--with-mule'
'--with-xim=xlib' '--with-xfs' '--use-union-type'
'--pdump'
XEmacs 21.2-b35 "Nike" configured for `i686-pc-linux'.
Compilation / Installation:
Source code location: /coda/Projects/XEmacs/21.2-HEAD
Installation prefix: /usr/local
Operating system description file: `s/linux.h'
Machine description file: `m/intel386.h'
Compiler: gcc -g -O3 -Wall -Wno-switch -Wpointer-arith -Winline
-Wmissing-prototypes -Wshadow
Relocating allocator for buffers: no
GNU version of malloc: yes
- Using Doug Lea's new malloc from the GNU C Library.
Window System:
Compiling in support for the X window system:
- X Windows headers location: /usr/X11R6/include
- X Windows libraries location: /usr/X11R6/lib
- Handling WM_COMMAND properly.
Compiling in support for the Athena widget set:
- Athena headers location: X11/Xaw3d
- Athena library to link: Xaw3d
Using Lucid menubars.
Using Lucid scrollbars.
Using Athena dialog boxes.
Using Athena native widgets.
TTY:
Compiling in support for ncurses.
Images:
Compiling in support for GIF images (builtin).
Compiling in support for XPM images.
Compiling in support for PNG images.
Compiling in support for JPEG images.
Compiling in support for TIFF images.
Sound:
Compiling in support for NAS (network audio system).
Databases:
Compiling in support for Berkeley database.
Compiling in support for PostgreSQL.
- Using PostgreSQL header file: postgresql/libpq-fe.h
- Using PostgreSQL V7 bindings.
Internationalization:
Compiling in support for Mule (multi-lingual Emacs).
Compiling in support for XIM (X11R5+ I18N input method).
- Using raw Xlib to provide XIM support.
- Using XFontSet to provide bilingual menubar.
Compiling in support for Canna on Mule.
Compiling in support for the WNN input method on Mule.
Mail:
Compiling in support for "dot-locking" mail spool file locking method.
Other Features:
Compiling in support for dynamic shared object modules.
Using the union type for Lisp_Objects.
Using the new portable dumper.
Compiling in support for extra debugging code.
WARNING: ---------------------------------------------------------
WARNING: Compiling in support for runtime error checking.
WARNING: XEmacs will run noticeably more slowly as a result.
WARNING: Error checking is on by default for XEmacs beta releases.
WARNING: ---------------------------------------------------------
--
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."
11:51 p.m.
>>>> "SJT" == Stephen J Turnbull
<turnbull(a)sk.tsukuba.ac.jp> writes:
SJT> Which variety and version of Motif?
Lesstif. Looks like 0.89.4 It's at least date stamped Nov 5 1999.
hmm, i see i'm at least 2 releases behind on lesstif.
I'll wait on upgrading in case Andy would like me to try a patch or
something.
Jeff
4:56 p.m.
>>>> "Jeff" == Jeff Miller
<jmiller(a)cablespeed.com> writes:
Jeff> i see the progress gauge come up for a split second and am
Jeff> left with remmnants of the progress bar and the stop button
Jeff> now, switch to the scratch buffer
Jeff> now I have the set, save & done widgets, along with the
Jeff> progress bar remmnants in the *scratch buffer*
>>>> "Stephen" == Stephen J Turnbull
<turnbull(a)sk.tsukuba.ac.jp> writes:
Stephen> I can't replicate this. The obvious difference between
Stephen> my setup and yours is I use Lucid widgets, you're using
Stephen> motif. I think I can probably do a Motif test but it'll
Stephen> be a day or two; I may not have the libs installed.
OK, I've done this, with lesstif 0.91.4. No anomolies.
Maybe a lesstif 0.89 bug?
--
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."
12:15 a.m.
>>>> "SJT" == Stephen J Turnbull
<turnbull(a)sk.tsukuba.ac.jp> writes:
Jeff> now I have the set, save & done widgets, along with the
Jeff> progress bar remmnants in the *scratch buffer*
>>>> "Stephen" == Stephen J Turnbull
<turnbull(a)sk.tsukuba.ac.jp> writes:
Stephen> I can't replicate this. The obvious difference between
Stephen> my setup and yours is I use Lucid widgets, you're using
Stephen> motif. I think I can probably do a Motif test but it'll
Stephen> be a day or two; I may not have the libs installed.
SJT> OK, I've done this, with lesstif 0.91.4. No anomolies.
SJT> Maybe a lesstif 0.89 bug?
No, I think I have found my problem though. I did retest with
widgets=athena and though I thought it had gotten rid of the progress
bar orphans, in reality it did not. I realized I had not followed my
recipe exactly. I had just run xemacs, not xemacs -vanilla. Using
-vanilla, I do get the progress bar orphans, just the athena versions.
so.... I did a cvs diff and found that windows.c & glyphs.c had some
differences vs the current cvs. In particular, code mentioning
widget caching and broken subwindows.
I moved those two files out of the way, and cvs updated, and
recompiled. I retested 3 times and I cannot repeat the problem. So
it looks like I had some old remnants of some previously hand applied
patches.
I have also recompiled with the motif (lesstif ) widgets and can
report that they do not produce any orphans either.
So, looks like a dirty src tree on my part, that is now clean. Problem
solved. (hopefully no new ones started :-) )
Jeff
8633
days inactive
8659
days old
12 comments
4 participants
participants (4)
-
Andy Piper -
Andy Piper -
Jeff Miller -
Stephen J. Turnbull