all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Reynaldo Baquerizo <reynaldomic@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 11830@debbugs.gnu.org
Subject: bug#11830: 24.1; "scroll-bar-mode disabled" not honored when emacs started as daemon
Date: Sun, 1 Jul 2012 14:54:57 -0500	[thread overview]
Message-ID: <20120701145457.069f7ceb@gmail.com> (raw)
In-Reply-To: <rnbojz9uam.fsf@fencepost.gnu.org>

> > In my .emacs file I keep this
> >
> > (if (fboundp 'menu-bar-mode) (menu-bar-mode -1))
> > (if (fboundp 'tool-bar-mode) (tool-bar-mode -1))
> > (if (fboundp 'scroll-bar-mode) (scroll-bar-mode -1))
> >
> > - I start emacs as a daemon. emacs --daemon
> > - I create a new frame. emacsclient -c
> >
> > I expect:
> > A frame with no scroll-bar
> 
> Works for me. I tried both Gtk and Lucid toolkit builds.

I left only those lines in my .emacs file and it did work.
Later I found that messing with default-frame-alist produced the unwanted result.

(setq default-frame-alist '((font . "Monaco-11"))

If instead I use:
(add-to-list 'default-frame-alist '(font . "Monaco-11"))

then it's OK.

It's a bit confusing the behaviour of frame related parameterers when used --daemon.

With the .emacs working file the value of default-parameter-list is

Its value is ((width . 112)
 (height . 30)
 (font . "Monaco-11")
 (vertical-scroll-bars))

I know that when --daemon is used initial-parameter-list has no effect, but
default-parameter-list does. 

Then, that (vertical-scroll-bars) shouldn't make new frames have a scroll-bar?






  reply	other threads:[~2012-07-01 19:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-01  1:14 bug#11830: 24.1; "scroll-bar-mode disabled" not honored when emacs started as daemon Reynaldo Baquerizo
2012-07-01 19:05 ` Glenn Morris
2012-07-01 19:54   ` Reynaldo Baquerizo [this message]
2012-07-02  0:49     ` Glenn Morris
2012-07-02  1:56       ` Reynaldo Baquerizo

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=20120701145457.069f7ceb@gmail.com \
    --to=reynaldomic@gmail.com \
    --cc=11830@debbugs.gnu.org \
    --cc=rgm@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.