From: Adrian Robert <Adrian.B.Robert@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: NeXTStep port: slowness, etc.
Date: Wed, 16 Jul 2008 12:29:20 +0000 (UTC) [thread overview]
Message-ID: <loom.20080716T121902-542@post.gmane.org> (raw)
In-Reply-To: A8848DDD-04E1-4C36-B70C-C2BE8A41DC4D@gmail.com
David Reitter <david.reitter <at> gmail.com> writes:
>
> I'm experiencing a delay of almost one second when accessing on menus,
> i.e. there is a long lag between clicking on a menu title and the menu
> actually showing up. That shouldn't be.
This is due to this change:
2008-07-15 Stefan Monnier <monnier@iro.umontreal.ca>
* keyboard.c (parse_menu_item): Don't use cachelist, even under NS.
If the cache doesn't work, let's fix it, rather than work around it.
This is the right thing to do, but it means some significant work
may be needed to recover normal performance. When I looked into
this, my best guess was that further optimization needed to be
done in the ns menu code. ns_update_menubar() from line 108 in
nsmenu.m. I did my best to follow other terms as closely as
possible, and even optimize more than they do, but something is
wrong somewhere. Also see comment on line 242. There is some
profiling code that can be enabled.
It could also be that the problem has not to do with nsmenu.m,
but something with the way other code is leading to the calling
of ns_update_menubar(). Either something of the new cache
referred to in keyboard.c is hit differently by the NS port for
some reason, or ns_update_menubar() is called in some different
pattern.
I spent some time on this but could not get any further -- it
might be another pair of eyes can see what I'm missing.
BTW, the "incremental" mouse highlighting you mention has been
there for a while, another thing I could not track down. Again,
NS handles this identically to other terms as far as I've been
able to tell, but there must be a difference somewhere..
next prev parent reply other threads:[~2008-07-16 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 5:43 NeXTStep port: slowness, etc David Reitter
2008-07-16 12:29 ` Adrian Robert [this message]
2008-07-16 16:04 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20080716T121902-542@post.gmane.org \
--to=adrian.b.robert@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.