From: Max Nikulin <manikulin@gmail.com>
To: Anthony Carrico <acarrico@memebeam.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-store-link on document title
Date: Fri, 14 Jul 2023 18:59:51 +0700 [thread overview]
Message-ID: <b8092291-2584-fb18-3009-9e81ec31baf0@gmail.com> (raw)
In-Reply-To: <87bkgyw9fc.fsf@localhost>
On 29/06/2023 22:54, Ihor Radchenko wrote:
> Anthony Carrico writes:
>
>> On 6/29/23 09:20, Ihor Radchenko wrote:
>>> Sure. And if it were a plain file link, there would be no reason to
>>> assign TITLE as description. Because the link would be to a generic line
>>> in file.
>>
>> What? The title is the perfect description for the file!
>
> That's because you expect Org to create a link to file.
> But what Org does (by default) is a link to specific _line_ in file.
I find expectation to use the title property reasonable. Text search
links are not created for lines after first heading. Current behavior is
not documented and (if I understand it correctly) was introduced in
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=12c09be3a
2020-02-19 18:03:53 +0100 Nicolas Goaziou: Refactor context part in file
links
However there is a number of unit tests, so it was certainly an intended
change.
So my vote is for [[file:document.org][title property]] when the
document has at least on heading.
prev parent reply other threads:[~2023-07-14 12:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 19:31 [BUG] org-store-link on document title Anthony Carrico
2023-06-28 19:56 ` Ihor Radchenko
2023-06-28 20:05 ` Anthony Carrico
2023-06-28 20:16 ` Ihor Radchenko
2023-06-29 13:06 ` Anthony Carrico
2023-06-29 13:20 ` Ihor Radchenko
2023-06-29 15:43 ` Anthony Carrico
2023-06-29 15:54 ` Ihor Radchenko
2023-06-29 16:11 ` Anthony Carrico
2023-07-14 11:59 ` Max Nikulin [this message]
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=b8092291-2584-fb18-3009-9e81ec31baf0@gmail.com \
--to=manikulin@gmail.com \
--cc=acarrico@memebeam.org \
--cc=emacs-orgmode@gnu.org \
/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).