all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
	Lars Ingebrigtsen <larsi@gnus.org>
Cc: 24651@debbugs.gnu.org, Colin Fraizer <colin.fraizer@gmail.com>
Subject: bug#24651: 25.1; frame-inherited-parameters only partially works
Date: Thu, 3 Dec 2020 16:45:06 +0100	[thread overview]
Message-ID: <ed805c34-7169-e71b-78c7-19b202bf7055@gmx.at> (raw)
In-Reply-To: <jwvblfakj6h.fsf-monnier+emacs@gnu.org>

 >>> When a val is nil, it
 >>> won't override a default parameter whose value is non-nil.  But I never
 >>> figured out what inherited parameters are useful for in the first place
 >>> so maybe this is of no importance.
 >
 > They were introduced so as to associate specific frames with specific emacsclients.

And there a non-nil parameter in 'default-frame-alist' is supposed to
override a nil parameter in 'frame-inherited-parameters'.  Such that
with emacs -Q setting

(setq default-frame-alist '((alpha . 50)))
(setq frame-inherited-parameters '(alpha))

in *scratch*, C-x 5 2 will produce a semi-transparent frame.

martin





  reply	other threads:[~2020-12-03 15:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-08 19:29 bug#24651: 25.1; frame-inherited-parameters only partially works Colin Fraizer
2020-11-30 12:05 ` Lars Ingebrigtsen
2020-11-30 17:30   ` martin rudalics
2020-12-02  9:57     ` Lars Ingebrigtsen
2020-12-02 10:31       ` martin rudalics
2020-12-02 17:00       ` Stefan Monnier
2020-12-03  9:53         ` martin rudalics
2020-12-03 10:28           ` Lars Ingebrigtsen
2020-12-03 15:26             ` Stefan Monnier
2020-12-03 15:45               ` martin rudalics [this message]
2022-02-08  6:38               ` Lars Ingebrigtsen

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=ed805c34-7169-e71b-78c7-19b202bf7055@gmx.at \
    --to=rudalics@gmx.at \
    --cc=24651@debbugs.gnu.org \
    --cc=colin.fraizer@gmail.com \
    --cc=larsi@gnus.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.