From: gerard.vermeulen@posteo.net
To: Dan Drake <dan.drake@gmail.com>
Cc: emacs-orgmode@gnu.org,
emacs-orgmode-bounces+gerard.vermeulen=posteo.net@gnu.org
Subject: Re: inconsistency links and code line labels
Date: Fri, 07 Jul 2023 05:57:46 +0000 [thread overview]
Message-ID: <db0d52164322243ce1a9f6d318aa2195@posteo.net> (raw)
In-Reply-To: <CAKqbAeEpzFarKhyo_z0eMFzZRN=TQpct5doQfCw2RO_t5Rzp+g@mail.gmail.com>
On 06.07.2023 14:49, Dan Drake wrote:
>
> There's a bug [[(my-code-line-label)][right here]].
>
> This seems inconsistent. Why do I have to omit the ref: bit? This
> always confuses me; it seems like it would be simpler to just make the
> label and the links to that line of code be exactly the same. I don't
> see any particular reference to this in the org manual
> (https://orgmode.org/manual/Internal-Links.html [2]). Any insights?
>
> My idea would be to get rid of the special behavior for code line
> labels and just make this work with dedicated targets: in regular
> parts of my org file, I use <<link-target>> and can make links to
> that. It would be simple and consistent to make that also work the
> same when <<link-target>> is inside a code block.
>
Such link targets would conflict with <<code-block-id>> references
See: https://orgmode.org/manual/Noweb-Reference-Syntax.html
Therefore something like the behavior described in
https://orgmode.org/manual/Literal-Examples.html
must have been invented (look at the description of the -n, -r, and
-l switches).
Regards -- Gerard
next prev parent reply other threads:[~2023-07-07 5:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 12:49 inconsistency links and code line labels Dan Drake
2023-07-07 5:57 ` gerard.vermeulen [this message]
2023-07-07 9:48 ` Ihor Radchenko
2023-07-08 22:24 ` Dan Drake
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=db0d52164322243ce1a9f6d318aa2195@posteo.net \
--to=gerard.vermeulen@posteo.net \
--cc=dan.drake@gmail.com \
--cc=emacs-orgmode-bounces+gerard.vermeulen=posteo.net@gnu.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).