From: Nicolas Goaziou <firstname.lastname@example.org>
To: Maxim Nikulin <email@example.com>
Subject: Re: org-store-link and help for a key
Date: Tue, 27 Apr 2021 17:52:42 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Maxim Nikulin's message of "Tue, 27 Apr 2021 21:44:09 +0700")
Maxim Nikulin <firstname.lastname@example.org> writes:
> On 27/04/2021 21:25, Bastien wrote:
>> Even though storing links to help buffers describing key bindings is
>> tempting, there is no way to recreate such buffers only based on the
>> key string, because keys are contextual.
>> In org-mode, C-h k C-a will describe org-beginning-of-line while in
>> other modes it will probably describe beginning-of-line.
>> So we cannot really write a proper handler for these links and the
>> user error is correct here.
>> I'm closing this bug report now.
> I have looked into the code storing and handling links yet, so I am
> unaware what is possible and what is not. My expectation is to get
> link to org-beginning-of-line if help is invoked from an org buffer
> and link to beginning-of-line if I came to the help page from some
> other file. I do not know whether associated function may be obtained
> for a help buffer opened for keystroke.
I did this on master. I only tested it lightly.
next prev parent reply other threads:[~2021-04-27 15:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 14:54 org-store-link and help for a key Maxim Nikulin
2020-09-10 3:32 ` Ihor Radchenko
2020-09-13 20:01 ` Bastien
2020-09-14 7:21 ` Ihor Radchenko
2021-04-27 14:25 ` Bastien
2021-04-27 14:44 ` Maxim Nikulin
2021-04-27 15:52 ` Nicolas Goaziou [this message]
2021-04-27 16:41 ` Maxim Nikulin
2021-04-27 20:01 ` Nicolas Goaziou
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).