all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Anthony Carrico <acarrico@memebeam.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-store-link on document title
Date: Thu, 29 Jun 2023 15:54:47 +0000	[thread overview]
Message-ID: <87bkgyw9fc.fsf@localhost> (raw)
In-Reply-To: <0b1fb992-0d0b-326f-02d8-b3f307546eb2@memebeam.org>

Anthony Carrico <acarrico@memebeam.org> 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 would say that 90% of the links in my org notes are file links with 
> the title as the description. I tend to use *deft* to search a lot of 
> small pages without deep outlines.

You can set :store property for "file" links in `org-link-parameters' to
adjust for your personal use case.

-- 
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>


  reply	other threads:[~2023-06-29 15:56 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 [this message]
2023-06-29 16:11               ` Anthony Carrico
2023-07-14 11:59               ` Max Nikulin

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=87bkgyw9fc.fsf@localhost \
    --to=yantar92@posteo.net \
    --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 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.