unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juanma Barranquero'" <lekktu@gmail.com>,
	"'Chong Yidong'" <cyd@stupidchicken.com>
Cc: 'Emacs developers' <emacs-devel@gnu.org>
Subject: RE: [Emacs-diffs] /srv/bzr/emacs/trunk r100650: Change default-frame-alist and menu/tool-bar-mode interaction (Bug#2249).
Date: Sun, 27 Jun 2010 07:06:59 -0700	[thread overview]
Message-ID: <CBFADEF54CB74694A78BAB69629CD0FA@us.oracle.com> (raw)
In-Reply-To: <AANLkTik2d2uswBgvlsynJWte4eHn3lHJUx4_qv2fRI7l@mail.gmail.com>

>  Change default-frame-alist and menu/tool-bar-mode 
> interaction (Bug#2249).  Don't add entries for `menu-bar-lines'
> and `tool-bar-lines' to `default-frame-alist' and
> `initial-frame-alist' at startup.  Instead, use X resources
> to update the `menu-bar-mode' and `tool-bar-mode' variables
> at startup, and use them as defaults during frame creation.

I haven't followed this and cannot check the new effect.  But I hope this does
not mean that a user's customizations of, say, `default-frame-alist' will no
longer be respected wrt `menu-bar-lines' and `tool-bar-lines'.

When you say "use X resources", do you mean that Emacs now sets X resources or
only that users can use X resources to set these parameters? (You say "use X
resources" the same way you say "don't add entries", so it's unclear what the
subject of the sentence is: Emacs code or the user.)

---

FWIW: Over the past few major releases there has been considerable fiddling with
initial menu-bar and tool-bar settings and how they're established. I hope this
will settle down and reach a fixed point. ;-)  As an example, I have code that
fits the frame to a buffer, and it has to calculate the frame height differently
for different Emacs versions, because of the different treatment of these
parameters.




  parent reply	other threads:[~2010-06-27 14:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1OSgUt-0007A9-6N@internal.in.savannah.gnu.org>
2010-06-27 10:39 ` [Emacs-diffs] /srv/bzr/emacs/trunk r100650: Change default-frame-alist and menu/tool-bar-mode interaction (Bug#2249) Juanma Barranquero
2010-06-27 11:59   ` martin rudalics
2010-06-27 14:22     ` Juanma Barranquero
2010-06-27 14:43       ` martin rudalics
2010-06-27 15:11         ` Juanma Barranquero
2010-06-27 18:11           ` Chong Yidong
2010-06-27 14:06   ` Drew Adams [this message]
2010-07-03 19:30     ` [Emacs-diffs] /srv/bzr/emacs/trunk r100650: Changedefault-frame-alist " 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

  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=CBFADEF54CB74694A78BAB69629CD0FA@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    /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).