From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
martin rudalics <rudalics@gmx.at>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 6280@debbugs.gnu.org
Subject: bug#6280: 24.0.50; (elisp) Dedicated Windows
Date: Mon, 10 Feb 2014 09:02:37 -0800 (PST) [thread overview]
Message-ID: <9e569465-3107-4d63-be43-0a8b4c7bbb56@default> (raw)
In-Reply-To: <jwv1tza52w1.fsf-monnier+emacsbugs@gnu.org>
> In the above text, "dedicated frame" is not a special concept, it's
> just talking a way to say it's a frame which the user has created
> for a particular purpose.
In that case, it should use different phrasing, to avoid confusion
with dedicated windows. Say, e.g., "a frame which the user has
created for a particular purpose".
Of course, with such clearer phrasing it becomes clear that this
doesn't mean anything at all. Not unless you say what you have
in mind by "for a particular purpose". What frame creation is
not for a particular purpose?
If this is to be helpful/meaningful, it needs to actually say
something. Perhaps an example of what you have in mind would
help - an example of a frame "created for a particular purpose".
If all you mean is a standalone minibuffer frame, then say that.
Don't use the word "dedicated" at all. If you think that is
not clear enough, then say a frame whose `minibuffer' parameter
has value `only'.
prev parent reply other threads:[~2014-02-10 17:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 15:51 bug#6280: 24.0.50; (elisp) Dedicated Windows Drew Adams
2010-05-27 17:24 ` martin rudalics
2010-05-27 17:51 ` Drew Adams
2010-05-28 9:19 ` martin rudalics
2010-05-28 14:13 ` Drew Adams
2010-05-28 15:10 ` martin rudalics
2010-05-28 16:16 ` Drew Adams
2010-05-29 8:20 ` martin rudalics
2014-02-10 3:19 ` Lars Ingebrigtsen
2014-02-10 3:32 ` Drew Adams
2014-02-10 8:15 ` martin rudalics
2014-02-10 16:52 ` Stefan Monnier
2014-02-10 17:02 ` Drew Adams [this message]
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=9e569465-3107-4d63-be43-0a8b4c7bbb56@default \
--to=drew.adams@oracle.com \
--cc=6280@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=rudalics@gmx.at \
/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).