From: Eli Zaretskii <eliz@gnu.org>
To: 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, 07 Dec 2015 20:26:24 +0200 [thread overview]
Message-ID: <83twnucdyn.fsf@gnu.org> (raw)
In-Reply-To: <61eaf86f-4a08-480e-bf3d-8f32b40152d7@default>
> Date: Mon, 7 Dec 2015 10:07:49 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 22104@debbugs.gnu.org
>
> I think that statement can just be removed.
I believe this feature is used to make "frame-local" variables. So
removing that sentence will lose information.
> No one would guess that any special, additional action would be
> undertaken for a parameter that Emacs does not recognize.
But it could well barf for such a parameter, at least in principle.
So that sentence does add useful information.
> 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.
Oh, I think we have all the technology necessary to say that in a way
that won't confuse users.
next prev parent reply other threads:[~2015-12-07 18:26 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
2015-12-07 18:26 ` Eli Zaretskii [this message]
[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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83twnucdyn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22104@debbugs.gnu.org \
--cc=drew.adams@oracle.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 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.