all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: Geek4AllSeasons <Geek4AllSeasons@hotmail.com>
Cc: Help-gnu-emacs@gnu.org
Subject: Re: menu-bar/menu problems and label/help text purecopy guidelines
Date: Thu, 10 Dec 2009 23:23:46 +0100	[thread overview]
Message-ID: <e01d8a50912101423j2823a0dema6ff96cdd4fb76ea@mail.gmail.com> (raw)
In-Reply-To: <26634810.post@talk.nabble.com>

On Thu, Dec 3, 2009 at 11:57 PM, Geek4AllSeasons
<Geek4AllSeasons@hotmail.com> wrote:
>
> The menu-bar started having episodes (standard menus fading out/disappearing
> when clicked; toolbar tooltips displayed on mouse-hover on menu-bar) about a
> week ago.
>
> Emacs 23.1.50.cvs090630/EmacsW32 1.58 patched installed 09/23/09 had worked
> fine previously. Upgrading to Emacs 23.1.50.cvs091103/EmacsW32 1.58 didn't
> help.


Could you please test with an unpatched Emacs? I suspect the problem
may be difficult to reproduce there because the menus are harder to
reach from the keyboard. Or are you using the mouse?

In any case please try to reproduce it with an unpatched Emacs and
send a bug report.


> A few menu text/purecopy bug reports and thread postings referencing the
> switch to gtk+ reduced the search space. Inserting purecopy wrappers for
> menu text corrects the problem menu by menu.
>
> Use of purecopy for menu text is inconsistent for core distribution and
> add-on/contributed libraries. In many, maybe, most cases GC menu text works.
> A comment in an Emacs-Dev thread indicated library pre-loading (loaddefs.el)
> building Emacs as determining the need/use of pure/GC storage.
>
> Are guidelines available? If so, corrections could be made accordingly and
> patches created/submitted.


According to the elisp manual purecopy does not do anything except
when building and dumping Emacs so it should not be the problem here,
see

  (info "(elisp) Pure Storage")


> Based on search results there seems to be an increasing number of
> potentially related issues/problems reported. Variability of symptoms makes
> searching for solutions/workarounds more difficult. Time and effort would be
> saved if general/less incident specific posting/descriptions were available.
>
> Please let me know if there is a better list.
>
> Thanks.
>
> david
> --
> View this message in context: http://old.nabble.com/menu-bar-menu-problems-and-label-help-text-purecopy-guidelines-tp26634810p26634810.html
> Sent from the Emacs - Help mailing list archive at Nabble.com.
>
>
>
>




  reply	other threads:[~2009-12-10 22:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 22:57 menu-bar/menu problems and label/help text purecopy guidelines Geek4AllSeasons
2009-12-10 22:23 ` Lennart Borgman [this message]
2009-12-14 22:10   ` Geek4AllSeasons
2009-12-14 23:49     ` Lennart Borgman

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=e01d8a50912101423j2823a0dema6ff96cdd4fb76ea@mail.gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=Geek4AllSeasons@hotmail.com \
    --cc=Help-gnu-emacs@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.