From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 23093@debbugs.gnu.org, nljlistbox2@gmail.com
Subject: bug#23093: 25.0.92; Change for the worse: minibuffer completion window splits below rather that right
Date: Wed, 23 Mar 2016 17:20:24 +0200 [thread overview]
Message-ID: <83twjx2pc7.fsf@gnu.org> (raw)
In-Reply-To: <56F24F33.5070904@gmx.at> (message from martin rudalics on Wed, 23 Mar 2016 09:09:23 +0100)
> Date: Wed, 23 Mar 2016 09:09:23 +0100
> From: martin rudalics <rudalics@gmx.at>
> CC: nljlistbox2@gmail.com, 23093@debbugs.gnu.org
>
> > Hmm... I see neither temp-buffer-resize-mode nor
> > temp-buffer-max-height are documented in the manual.
>
> Both are documented in section 37.8 "Temporary Displays" of the Elisp
> manual. Do you mean they should be documented in the Emacs manual too?
Yes, I meant the user manual. These are user-level features.
> If so, where?
"Displaying Buffers" sounds like a good place. Maybe add a new
subsection there, which talks specifically about temporary pop-up
buffers.
Thanks.
next prev parent reply other threads:[~2016-03-23 15:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 17:37 bug#23093: 25.0.92; Change for the worse: minibuffer completion window splits below rather that right N. Jackson
2016-03-22 18:47 ` martin rudalics
2016-03-22 19:02 ` Eli Zaretskii
2016-03-23 8:09 ` martin rudalics
2016-03-23 15:20 ` Eli Zaretskii [this message]
2016-03-23 18:53 ` martin rudalics
2016-03-23 19:43 ` Eli Zaretskii
2016-03-23 20:17 ` N. Jackson
2016-03-24 7:42 ` martin rudalics
2016-03-25 7:42 ` martin rudalics
2016-03-25 8:05 ` Eli Zaretskii
2016-03-25 8:37 ` martin rudalics
2016-03-25 10:39 ` Eli Zaretskii
2020-08-24 18:21 ` Lars Ingebrigtsen
2016-03-22 19:45 ` N. Jackson
2016-03-23 8:09 ` martin rudalics
2016-03-23 21:35 ` Juri Linkov
2016-03-24 7:43 ` martin rudalics
2016-03-24 22:16 ` Juri Linkov
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=83twjx2pc7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23093@debbugs.gnu.org \
--cc=nljlistbox2@gmail.com \
--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 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.