From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
Jean Louis <bugs@gnu.support>,
33007@debbugs.gnu.org
Subject: bug#33007: 27.0.50; Proposal for function to edit and return string
Date: Wed, 27 Apr 2022 19:44:54 +0300 [thread overview]
Message-ID: <86wnfascft.fsf@mail.linkov.net> (raw)
In-Reply-To: <87sfpyd8wu.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 27 Apr 2022 14:10:09 +0200")
> pop-to-buffer-same-window does allow customization via
> display-buffer-alist, but -below-selected would be a better default.
This is what could be used:
(pop-to-buffer (generate-new-buffer "*edit string*")
'(display-buffer-below-selected
(window-min-height . 10)
(window-height . fit-window-to-buffer)))
but currently its window-min-height has no effect.
Maybe because of a bug? The docstring of display-buffer-below-selected:
If ALIST contains a `window-min-height' entry, this function
ensures that the window used is or can become at least as high as
specified by that entry's value. Note that such an entry alone
will not resize the window per se. In order to do that, ALIST
must also contain a `window-height' entry with the same value.
But still the window height is less than 10 lines.
BTW, maybe read-string-from-buffer should have ###autoload cookie?
Also any chance to make it argument-wise compatible with read-string?
Currently:
(read-string PROMPT &optional INITIAL-INPUT
(read-string-from-buffer STRING &optional HELP-TEXT
HELP-TEXT could be renamed to PROMPT, and STRING really is INITIAL-INPUT.
next prev parent reply other threads:[~2022-04-27 16:44 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 20:49 bug#33007: 27.0.50; Proposal for function to edit and return string Jean Louis
2018-10-11 2:36 ` Eli Zaretskii
2018-10-11 6:33 ` Jean Louis
2018-10-11 13:31 ` Michael Heerdegen
2018-10-11 13:40 ` Jean Louis
2018-10-11 14:24 ` Eli Zaretskii
2018-10-11 20:20 ` Michael Heerdegen
2018-10-11 21:23 ` Drew Adams
2018-10-12 4:26 ` Eli Zaretskii
2018-10-12 11:26 ` Michael Heerdegen
2018-10-12 12:41 ` Eli Zaretskii
2022-04-24 13:15 ` Lars Ingebrigtsen
2022-04-25 3:00 ` Michael Heerdegen
2022-04-25 7:50 ` Lars Ingebrigtsen
2022-04-25 15:42 ` Juri Linkov
2022-04-25 22:26 ` Michael Heerdegen
2022-04-26 7:23 ` Juri Linkov
2022-04-26 9:56 ` Lars Ingebrigtsen
2022-04-26 15:36 ` Juri Linkov
2022-04-27 12:09 ` Lars Ingebrigtsen
2022-04-26 9:55 ` Lars Ingebrigtsen
2022-04-26 15:39 ` Juri Linkov
2022-04-27 12:10 ` Lars Ingebrigtsen
2022-04-27 16:44 ` Juri Linkov [this message]
2022-04-27 17:05 ` Lars Ingebrigtsen
2022-04-28 7:32 ` Juri Linkov
2022-04-28 10:19 ` Lars Ingebrigtsen
2022-05-08 18:22 ` Juri Linkov
2022-05-09 9:49 ` Lars Ingebrigtsen
2022-05-09 18:52 ` Juri Linkov
2022-05-10 1:53 ` Lars Ingebrigtsen
2022-04-25 22:46 ` Michael Heerdegen
2022-04-26 9:58 ` Lars Ingebrigtsen
2018-10-11 13:55 ` Eli Zaretskii
2018-10-11 14:01 ` Michael Heerdegen
2018-10-11 14:08 ` Jean Louis
2018-10-11 14:16 ` Michael Heerdegen
2018-10-11 14:27 ` Eli Zaretskii
2018-10-11 14:36 ` Jean Louis
[not found] ` <<87lg74zk2k.fsf@web.de>
[not found] ` <<834ldsy31m.fsf@gnu.org>
2018-10-11 14:41 ` Drew Adams
2018-10-11 16:40 ` Eric Abrahamsen
2018-10-15 20:34 ` Juri Linkov
2018-10-15 22:07 ` Drew Adams
2018-10-16 22:12 ` Juri Linkov
2018-10-16 23:05 ` Drew Adams
2018-10-17 15:39 ` Michael Heerdegen
[not found] <<86pnwh4je8.fsf@protected.rcdrun.com>
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=86wnfascft.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=33007@debbugs.gnu.org \
--cc=bugs@gnu.support \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
/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.