From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 22104@debbugs.gnu.org
Subject: bug#22104: 25.1.50; doc string of `modify-frame-parameters'
Date: Mon, 7 Dec 2015 10:07:49 -0800 (PST) [thread overview]
Message-ID: <61eaf86f-4a08-480e-bf3d-8f32b40152d7@default> (raw)
In-Reply-To: <<83wpsqcfma.fsf@gnu.org>>
> > > > This part of the doc string is unclear:
> > > >
> > > > Undefined PARMs are ignored, but stored in the frame's parameter
> list
> > > > so that 'frame-parameters' will return them.
> > > >
> > > > What does "ignored" mean here? It can only mean (?) ignored by
> > > > `modify-parameters', but what does that mean, operationally?
> > >
> > > It means they have no effect beyond being stored in the parameter
> > > list. I will clarify that.
> >
> > But I still don't understand, from that description. What else
> > does `modify-frame-parameters' ever do, besides store them in the
> > parameter list?
>
> Quite a few parameters require modify-frame-parameters to call some
> API in order to put the parameter in effect. For example,
> background-color -- just storing the new value won't magically change
> the color, would it?
>
> IOW, modify-frame-parameters is not just for altering the params
> alist, it is primarily for changing the frame according to the changed
> parameters; it records the parameters in effect in the alist mostly as
> a side effect.
>
> Yes, "modify the frame parameters" is ambiguous.
OK, so I guess the point is that unrecognized (perhaps a better term than "undefined", here) parameters are simply stored in the frame's parameter
list. No extra handling is done.
I think that statement can just be removed. No one would guess that
any special, additional action would be undertaken for a parameter that
Emacs does not recognize. Talking about this just confuses readers.
Users should know that they can add any parameters they want, which
are unknown to Emacs. But because Emacs knows nothing about them it
is up to a user to provide any expected behavior for them.
It is important to say that users can add their own parameters.
And I guess it is helpful to add that Emacs does not do anything
with them (unless the user programs it to do so). But if we can't
do that without confusing readers more, then this addition should
be dropped, IMO.
next prev parent reply other threads:[~2015-12-07 18:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<f9e6f115-99eb-4e4a-80e6-67763362f0b4@default>
[not found] ` <<831taydvql.fsf@gnu.org>
2015-12-07 17:34 ` bug#22104: 25.1.50; doc string of `modify-frame-parameters' Drew Adams
2015-12-07 17:50 ` Eli Zaretskii
[not found] ` <<95bedfbe-5686-4a79-9fd3-561d927986d3@default>
[not found] ` <<83wpsqcfma.fsf@gnu.org>
2015-12-07 18:07 ` Drew Adams [this message]
2015-12-07 18:26 ` Eli Zaretskii
[not found] ` <<61eaf86f-4a08-480e-bf3d-8f32b40152d7@default>
[not found] ` <<83twnucdyn.fsf@gnu.org>
2015-12-07 19:16 ` Drew Adams
2015-12-07 3:58 Drew Adams
2015-12-07 17:17 ` Eli Zaretskii
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=61eaf86f-4a08-480e-bf3d-8f32b40152d7@default \
--to=drew.adams@oracle.com \
--cc=22104@debbugs.gnu.org \
--cc=eliz@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 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).