>>>> "vin" == Vin Shelton
<acs(a)alumni.princeton.edu> writes:
> tall in my current instance. This would hardly be noticable,
> except that the whole area doesn't necessarily get cleared,
> leaving some turds (presumably from before a resize or
> something like that). See attached PNG.
vin> Stephen -
vin> I don't see anything like this in my 21.4 XEmacsen. So I
vin> have a few questions: Do you get this with a -vanilla XEmacs?
I'm sorry, but I don't know about the -vanilla XEmacs yet. I strongly
suspect it depends on my init file, which manipulates frame size. I
don't know what else it depends on, as a number of files and
corresponding modes were loaded by desktop.el. I was using Gnus at
the time.
I'm not going to have much time to try to replicate until Monday or
Tuesday (the box is at work, I'll try a remote X window later), I'm
afraid, although I'll try to get to it. The reason for reporting at
this stage is that such screen artifacts tend to be transient and
intermittent, so I wanted it in the list archives where I know how to
find it, rather than somewhere on my hard drive which is at the moment
a rather chaotic place.
vin> In your screenshot, what's the cross-hatched section to the
vin> left of the minibuffer? Is that a scrollbar?
The cross-hatched region is just a very boring root window
background. My Emacs frame configuration was something like this:
+----------------+
| |
| +---------------+
| | |
| | |
| | |
| :::|:::::: |
+----------|:::::: |
:::|:::::: |
:::+---------------+
::::::::::
with the screen shot area covered by colons. I probably should have
made the screen shot bigger.
--
School of Systems and Information Engineering
http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.