From: Max Nikulin <manikulin@gmail.com>
To: Carlos Pita <carlosjosepita@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Adding target and custom id links doesn't ask for description
Date: Wed, 3 Aug 2022 18:35:35 +0700 [thread overview]
Message-ID: <28e3e346-3110-b5fc-54c5-24d25e69cc50@gmail.com> (raw)
In-Reply-To: <B14656E6-EA19-4C5F-8ED6-578CB7EC0F2F@gmail.com>
On 03/08/2022 01:58, Carlos Pita wrote:
>
> This is the link that org-insert-link inserts for <<here>>:
>
> [[here][file:~/Desktop/Org/capturas.org::here]]
>
> This is the link that org-insert-link inserts for CUSTOM_ID = cusid:
>
> [[#cusid][file:~/Desktop/Org/capturas.org::#cusid]]
>
> Perhaps description and link are swapped? In both cases the full path
> is redundant since the link is pointing to the current file, but the
> verbosity is arguably less adequate for the description field.
In my opinion, attempt to fix storing of <<target>> links broke such use
cases, however I am unsure that we are complaining about exactly the
same things. My attempts to alleviate the issue:
Max Nikulin. Re: Bug: org-store-link uses CUSTOM_ID instead of target
point. Sat, 6 Nov 2021 19:51:29 +0700.
https://list.orgmode.org/e2c807a7-1924-6f08-9e63-4f70aee9d3b5@gmail.com
next prev parent reply other threads:[~2022-08-03 11:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 17:44 Adding target and custom id links doesn't ask for description Carlos Pita
2022-08-02 18:58 ` Carlos Pita
2022-08-03 11:35 ` Max Nikulin [this message]
2022-08-10 5:39 ` [PATCH] " Ihor Radchenko
2022-08-10 12:30 ` Carlos Pita
2022-08-11 15:50 ` Max Nikulin
2022-08-12 19:18 ` Carlos Pita
2022-08-13 5:01 ` [PATCH v2] " Ihor Radchenko
2022-08-14 9:53 ` Max Nikulin
2022-09-11 13:18 ` Max Nikulin
2022-09-12 11:02 ` Ihor Radchenko
2022-09-12 16:05 ` Max Nikulin
2022-09-13 13:08 ` 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=28e3e346-3110-b5fc-54c5-24d25e69cc50@gmail.com \
--to=manikulin@gmail.com \
--cc=carlosjosepita@gmail.com \
--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).