all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Tom Gillespie <tgbugs@gmail.com>
Cc: Luis Osa <luis.osa.gdc@gmail.com>,
	 emacs-orgmode <emacs-orgmode@gnu.org>,
	 Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Problem when tangling source blocks with custom coderefs
Date: Sun, 23 Oct 2022 05:37:01 +0000	[thread overview]
Message-ID: <87mt9np0ci.fsf@localhost> (raw)
In-Reply-To: <CA+G3_PNkecusXFfOYTRKiNe+et0xXdz_tXOVunSetdC7hvxJtA@mail.gmail.com>

Tom Gillespie <tgbugs@gmail.com> writes:

>    I don't think you are doing anything wrong. IIRC the portion of the
> patch that allowed the customization to propagate to the tangled code
> was not included. Given that I am no longer the only one who is
> looking for/expecting this behavior, maybe it is worth revisiting the
> decision. 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. I would like to see this implemented,
> so let's see what Nicolas has to say. Best!

Could you please provide a link to the relevant discussion?

-- 
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-10-24  0:44 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mt9np0ci.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=luis.osa.gdc@gmail.com \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.