From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: obscure Emacs redisplay bug (Windows?)
Date: Wed, 09 Mar 2005 12:14:29 +0100 [thread overview]
Message-ID: <m3r7ipkr56.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <000201c52494$567b2d40$2f322f3e@v357900157> (Martin Rudalics's message of "Wed, 9 Mar 2005 08:44:21 +0100")
"Martin Rudalics" <rudalics@gmx.at> writes:
>> Do you get a menu-bar if you start emacs -q ?
>
> No.
>
No menu-bar on windows -- that's very odd.
Sounds like the version you got is hoaxed?
>>
>> If you do, something in your .emacs disables the menu-bar.
>>
>
> I don't get a menubar without any .emacs at all.
>
>>
>> I don't know what happens here.
>>
>> Can you produce a self-contained test that can demonstrate the problem?
>>
>
> I shall send you my 7000 lines code and the necessary instructions.
I will look at it...
>
>> > Finally, I noticed that my display flickers
>> > more frequently - in particular when I display a customization buffer in
>> > a subwindow.
>>
>> I'm not that familiar with the Windows port, but others have reported
>> flickering problems - especially with tooltips and the toolbar updates --
>> that still need to be investigated.
>>
>
> Customization buffers - that seems more related to widgets, buttons
> and the like. However, intuitively I would say that windows refresh
> more frequently - likely my code is responsible for it (windows
> means individual Emacs windows).
Could be...
>
>> > I shall tell you more when I have managed to get this Emacs more stable:
>> > While I wrote these lines it has crashed my Windows twice and does very
>> > strange things with my harddisk whenever it starts up. Once more,
>> > thanks for your help,
>>
>> What version of windows?
>
> Windows ME (as long as Emacs doesn't crash it)
No wonder... Windows ME is the worst version ever -- very unstable.
>
>> Where did you get the pre-built emacs ?
>
> http://nqmacs.sourceforge.net/
>
>>
>> Maybe it was built in a special way?
>>
>
> `emacs-version' gives me
>
> GNU Emacs 21.3.50.1 (i386-mingw-windows98.3000) of 2005-01-30 on NONIQPC
Anybody else tried that version with good results?
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next parent reply other threads:[~2005-03-09 11:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3y8czce15.fsf@kfs-l.imdomain.dk>
[not found] ` <25964.1110264663@www33.gmx.net>
[not found] ` <m33bv6muxe.fsf@kfs-l.imdomain.dk>
[not found] ` <000401c52401$bca4a080$f20d7b50@v357900157>
[not found] ` <m3zmxd3ly7.fsf_-_@kfs-l.imdomain.dk>
[not found] ` <000201c52494$567b2d40$2f322f3e@v357900157>
2005-03-09 11:14 ` Kim F. Storm [this message]
2005-03-09 12:43 ` obscure Emacs redisplay bug (Windows?) Stephan Stahl
2005-03-09 12:53 ` Jason Rumney
2005-03-09 12:44 Stephan Stahl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3r7ipkr56.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).