From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: bugs@gnu.support, 33007@debbugs.gnu.org
Subject: bug#33007: 27.0.50; Proposal for function to edit and return string
Date: Thu, 11 Oct 2018 17:24:21 +0300 [thread overview]
Message-ID: <834ldsy31m.fsf@gnu.org> (raw)
In-Reply-To: <87lg74zk2k.fsf@web.de> (message from Michael Heerdegen on Thu, 11 Oct 2018 15:31:15 +0200)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: Eli Zaretskii <eliz@gnu.org>, 33007@debbugs.gnu.org
> Date: Thu, 11 Oct 2018 15:31:15 +0200
>
> Some minor thoughts: The input buffer should be more controllable: modes
> and keymap shouldn't be fixed. Also, it should be possible to prefill
> the buffer with a string describing what the user is expected to do, and
> which is ignored after the user has finished.
Don't we already have something like that in Customize and/or in EWW,
where they allow the user to fill fields in a form?
next prev parent reply other threads:[~2018-10-11 14:24 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 [this message]
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
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=834ldsy31m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33007@debbugs.gnu.org \
--cc=bugs@gnu.support \
--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.