From: Ihor Radchenko <yantar92@posteo.net>
To: "Rudolf Adamkovič" <salutis@me.com>
Cc: Salih Muhammed <lr0@gmx.com>, emacs-orgmode@gnu.org
Subject: Re: Consider removing newlines from org-insert-link help message
Date: Fri, 20 Oct 2023 12:30:48 +0000 [thread overview]
Message-ID: <87fs25bhmv.fsf@localhost> (raw)
In-Reply-To: <m2h6mllfq8.fsf@me.com>
Rudolf Adamkovič <salutis@me.com> writes:
>> What about replacing it with shorter description?
>
> +1 for making the message shorter,
>
> ... and while on it, perhaps also a bit clearer.
Patches welcome.
> - the key bindings are not propertized, and
> - the entire buffer is writable.
I see no obvious downsides. May as well.
>> Insert a link.
>
> How about we say "Insert link:" in the minibuffer and drop this sentence
> altogether? Grammatically, the minibuffer prompt would be similar to
> 'C-x b', which says "Switch to buffer".
Currently, the minibuffer message is simply "Link: ". "Insert link:" is
also ok.
>> Use TAB to complete link prefixes, then RET for type-specific
>> completion support.
>
> How about:
>
> Type TAB to complete link types, then RET to complete destinations.
Maybe "Press" rather than "Type".
>> Stored links are available with <up>/<down> or M-p/n (most recent with
>> RET):
>
> Could we show the default value in the minibuffer, as
>
> Insert link (default [...]):
>
> and then drop the "(most recent with RET)" comment?
We may, but the default link might sometimes be long. Not sure how it
will look like.
> As for the rest of the message, ... actually let me stop here and zoom
> out a bit. The optimal solution here would be to remove this entire UI
> and leverage standard Emacs completions. Org could simply ask
>
> Insert link (default [...]):
>
> in the minibuffer and then provide intelligent completions based on the
> current input. If that can be done, then Emacs can handle the rest. It
> can show completion candidates, handle past/future history, and more.
AFAIK, this is already done. We already use `completing-read'. The UI is
there historically and in addition to the normal Emacs completion.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-10-20 12:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 6:00 Consider removing newlines from org-insert-link help message Salih Muhammed
2023-10-17 10:53 ` Ihor Radchenko
2023-10-17 21:44 ` Salih Muhammed
2023-10-18 10:43 ` Ihor Radchenko
2023-10-20 11:01 ` Rudolf Adamkovič
2023-10-20 12:30 ` Ihor Radchenko [this message]
2023-12-10 0:22 ` Rudolf Adamkovič
2023-12-10 14:07 ` Ihor Radchenko
2023-12-10 23:25 ` Rudolf Adamkovič
2023-12-11 11:30 ` Ihor Radchenko
2023-12-17 23:36 ` Rudolf Adamkovič
2024-01-18 5:13 ` Salih Muhammed
2024-01-18 12:41 ` Ihor Radchenko
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fs25bhmv.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=lr0@gmx.com \
--cc=salutis@me.com \
/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/org-mode.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).