emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Luis Osa <luis.osa.gdc@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Problem when tangling source blocks with custom coderefs
Date: Thu, 10 Nov 2022 06:27:24 +0000	[thread overview]
Message-ID: <87cz9vjpdf.fsf@localhost> (raw)
In-Reply-To: <CAHf_bEO7TuOA6aa-DjYb3PWTfvBybvncDGa1iQ+6dBsTQ1ShdA@mail.gmail.com>

Luis Osa <luis.osa.gdc@gmail.com> writes:

> I would like to tangle source code blocks that contain coderefs. I have
> found that the coderefs are correctly filtered out from the tangled files
> if they follow the default format, i.e. "(ref:%s)", but not if I try to
> customize the format using the documented "-l" switch [1] to change them to
> something else, e.g. "|%s|".

I have looked through the ML archives and a similar issue appears to be
fixed already. See

> Here is an example:
>     #+begin_src python -r -l "|%s|" :tangle example.py
>     try:
>         sys.exit(app.run())
>     except:            |\label{line:except}\ding{182}|
>         sys.exit(1)
>     #+end_src
>     In line \ref{line:except}, marked \ding{182}, we are catching all
> exceptions ...

Note that we only allow _-A-Za-z0-9 in the labels. So, your example will
not work even after the fix.

Not sure if we need to do anything about this.

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>

      parent reply	other threads:[~2022-11-10  6:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18 22:20 Problem when tangling source blocks with custom coderefs Luis Osa
2022-01-19  1:33 ` Tom Gillespie
2022-01-19 21:00   ` Luis Osa
2022-10-23  5:37   ` Ihor Radchenko
2022-11-10  6:27 ` Ihor Radchenko [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:

  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=87cz9vjpdf.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=luis.osa.gdc@gmail.com \


* 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


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