From: Ihor Radchenko <yantar92@posteo.net>
To: Salih Muhammed <lr0@gmx.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Consider removing newlines from org-insert-link help message
Date: Wed, 18 Oct 2023 10:43:00 +0000 [thread overview]
Message-ID: <87wmvkdxe3.fsf@localhost> (raw)
In-Reply-To: <87h6moncj6.fsf@gmx.com>
Salih Muhammed <lr0@gmx.com> writes:
>> I am not sure. Your variant will be worse on smaller screens
>> or terminals, when the line wrap may look more ugly for longer line.
>
> What about replacing it with shorter description?
(Insert a link. Use TAB to complete link prefixes, then RET for type-specific completion support)
> "Insert a link. Use TAB for prefixes completion, RET for type-specific completion"
>
> This is only 80 characters, should be suitable for small terminals.
"then" was important in the original formulation.
I personally do not mind having a shorter variant, but we should not
make it obfuscated just for the sake of being short.
Also, if you really want to save screen space, you may consider hiding
the whole *Org Links* window by customizing `display-buffer-alist'.
--
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-18 10:42 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 [this message]
2023-10-20 11:01 ` Rudolf Adamkovič
2023-10-20 12:30 ` Ihor Radchenko
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wmvkdxe3.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=lr0@gmx.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 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.