all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'martin rudalics'" <rudalics@gmx.at>
Cc: 12406@debbugs.gnu.org
Subject: bug#12406: 24.2.50; frame parameter `menu-bar-lines' and `menu-bar-mode'
Date: Wed, 12 Sep 2012 07:13:45 -0700	[thread overview]
Message-ID: <95E595BA09D247A9BD45F52A304A471B@us.oracle.com> (raw)
In-Reply-To: <50504320.7030908@gmx.at>

>  > A user should be able, as now,
>  > to set the mode and have it (1) update all existing frames
> 
> IMHO it should update a frame iff that frame has no `menu-bar-lines'
> frame parameter.'

Why?  Why shouldn't a user be ABLE to turn on/off showing the menu bar in all
existing frames?

One way or the other, we should find ways for users to alternatively easily do
that (affecting all existing frames) OR protect some frames from that toggling.

IOW, both should be possible and easy for the user to control interactively (not
just in Lisp; e.g., using a prefix arg or a different command).

>  > and (b) affect future
>  > frames by setting the default behavior, i.e., unless overridden.






  reply	other threads:[~2012-09-12 14:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-10 17:59 bug#12406: 24.2.50; frame parameter `menu-bar-lines' and `menu-bar-mode' Drew Adams
2012-09-10 20:39 ` Stefan Monnier
2012-09-10 21:41   ` Drew Adams
2012-09-12  8:09     ` martin rudalics
2012-09-12 14:13       ` Drew Adams [this message]
2012-09-12 15:08         ` martin rudalics
2012-09-12 15:33           ` Drew Adams
2012-09-12 16:48             ` martin rudalics
2012-09-12 17:42               ` Drew Adams
2012-09-12 17:53                 ` martin rudalics
2012-09-12 18:02                   ` Drew Adams
2012-09-13  3:17             ` Stefan Monnier
2012-09-13  4:05               ` Drew Adams

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=95E595BA09D247A9BD45F52A304A471B@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=12406@debbugs.gnu.org \
    --cc=rudalics@gmx.at \
    /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.