From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, martin rudalics <rudalics@gmx.at>
Cc: 6280@debbugs.gnu.org
Subject: bug#6280: 24.0.50; (elisp) Dedicated Windows
Date: Sun, 9 Feb 2014 19:32:34 -0800 (PST) [thread overview]
Message-ID: <e072ecda-d5e5-4aa2-8af1-9d7de26a1418@default> (raw)
In-Reply-To: <87txc7hcxw.fsf@building.gnus.org>
> > Dedicated windows have an entire section in the Elisp manual.
> > What is not sufficiently clear there?
>
> Looks clear enough to me. Closing.
Did you read the bug report? It was NOT saying that node
`Dedicated Windows' in (elisp) is unclear. It said nothing of
the kind.
So that reason for closing this bug (which is not about that)
is 100% a red herring.
To repeat what I said before:
> I was clear about what is needed for the doc about this topic:
>
> 1. Put something in the Emacs manual about how to make windows
> dedicated.
>
> 2. In the Elisp manual, mention `special-display' buffers in node
> `Dedicated Windows'.
>
> See the original bug report for details.
There is NOTHING in the Emacs manual about dedicated windows,
except for this mention in passing (in node `Minibuffer Edit'),
which offers no explanation and has not even a cross reference
to the Elisp manual for the topic:
When not active, the minibuffer is in `minibuffer-inactive-mode',
and clicking `Mouse-1' there shows the `*Messages*' buffer. If
you use a dedicated frame for minibuffers, Emacs also recognizes
certain keys there, for example `n' to make a new frame.
The bug is still a bug. There is nothing in the Emacs manual
about how to make windows dedicated. And there is no mention of
`special-display' buffers in (elisp) `Dedicated Windows'.
next prev parent reply other threads:[~2014-02-10 3:32 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 [this message]
2014-02-10 8:15 ` martin rudalics
2014-02-10 16:52 ` Stefan Monnier
2014-02-10 17:02 ` Drew Adams
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=e072ecda-d5e5-4aa2-8af1-9d7de26a1418@default \
--to=drew.adams@oracle.com \
--cc=6280@debbugs.gnu.org \
--cc=larsi@gnus.org \
--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).