From: Luis Osa <luis.osa.gdc@gmail.com>
To: Tom Gillespie <tgbugs@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>,
Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Problem when tangling source blocks with custom coderefs
Date: Wed, 19 Jan 2022 22:00:51 +0100 [thread overview]
Message-ID: <CAHf_bEMfL1XtxjBiT0MbrjUbBNG3L4W47-43c30+5HLVLdrN+w@mail.gmail.com> (raw)
In-Reply-To: <CA+G3_PNkecusXFfOYTRKiNe+et0xXdz_tXOVunSetdC7hvxJtA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 701 bytes --]
Hi Tom,
The simplest fix right now would be to prepend your coderef
> with the python comment symbols # |hello| so that at the very least it
> won't break your tangled files.
Actually, that is exactly what I have done as a quick fix. It has a minor
inconvenience: anything else included on the line is colored as if it were
a comment in the final PDF, and I intended to add a symbol to mark the
reference. Not a big deal, but it looks different than intended.
I would like to see this implemented,
> so let's see what Nicolas has to say.
I would like to contribute something. Maybe a test to show what is the
behavior to expect. Thanks for your reassurance that this is not an error
on my side!
[-- Attachment #2: Type: text/html, Size: 1265 bytes --]
next prev parent reply other threads:[~2022-01-19 21:02 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 [this message]
2022-10-23 5:37 ` Ihor Radchenko
2022-11-10 6:27 ` 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=CAHf_bEMfL1XtxjBiT0MbrjUbBNG3L4W47-43c30+5HLVLdrN+w@mail.gmail.com \
--to=luis.osa.gdc@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=tgbugs@gmail.com \
/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).