emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Dan Drake <dan.drake@gmail.com>
To: emacs-orgmode@gnu.org
Subject: inconsistency links and code line labels
Date: Thu, 6 Jul 2023 07:49:59 -0500	[thread overview]
Message-ID: <CAKqbAeEpzFarKhyo_z0eMFzZRN=TQpct5doQfCw2RO_t5Rzp+g@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]

Hello -- I'm wondering about my question from here:

https://emacs.stackexchange.com/questions/77768/why-the-inconsistency-with-org-mode-code-line-labels-and-links

Copying my question: in a source code special block, I can add code line
labels, which have ref: in the label -- but when I make a link there, I
have to omit the ref:. For example:

#+begin_src csharp
1044 string foo = someFunction(1234);
1045 if (foo == "1")
1046 {
1047     bar = 5; //  (ref:my-code-line-label)
1048 }
// etc etc
#+end_src

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

Thanks!

-- 
Ceci n'est pas une .signature.

[-- Attachment #2: Type: text/html, Size: 2097 bytes --]

next             reply	other threads:[~2023-07-06 12:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06 12:49 Dan Drake [this message]
2023-07-07  5:57 ` inconsistency links and code line labels gerard.vermeulen
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='CAKqbAeEpzFarKhyo_z0eMFzZRN=TQpct5doQfCw2RO_t5Rzp+g@mail.gmail.com' \
    --to=dan.drake@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

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