all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>
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 21:05:57 -0700	[thread overview]
Message-ID: <9F2CC237A7D44E1AAA9000F1C6B72180@us.oracle.com> (raw)
In-Reply-To: <jwvwqzyfw8g.fsf-monnier+emacs@gnu.org>

> >> Because this way we'd have a consistent interface: The 
> >> presence of a frame parameter would signal "leave this
> >> frame alone".
> >
> > That's inconsistent with the convention that absence of a frame
> > parameter is equivalent to its presence with a nil value.  It is
> > similar to proposing that we give some  special signification to the
> > absense of a key in an alist, as opposed to a key with value nil.
> 
> Agreed.  That means, all frames should have a `menu-bar-lines'
> parameter, set to `default' in most of them.

Sounds reasonable.  The devil might be in the details of what you want to do
with/about it.  But yes, that sounds like a start.






      reply	other threads:[~2012-09-13  4:05 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
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 [this message]

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=9F2CC237A7D44E1AAA9000F1C6B72180@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=12406@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.