emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Timothy <tecosaur@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: tangling seems to have broken today
Date: Wed, 05 May 2021 21:41:56 +0800	[thread overview]
Message-ID: <87h7jhl2l7.fsf@gmail.com> (raw)
In-Reply-To: <8735v1uwqv.fsf@disroot.org>

I'd just like to chime in to note that I am also experiencing this issue.

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> I note that the git log shows a commit which affects tangling: 501b2a191
> I can no longer tangle with a given file name.  The error I get
> indicates that the tangling procedure is looking at the first line of
> the actual code block.  For instance, if I have
> #+begin_src org
>   ,#+begin_src julia :exports none :results output :tangle "svfmon.jl"
>     using DigitalFilter
>     ...
>   ,#+end_src
> #+end_src
> the error message when trying to tangle says:
> Wrong type argument: listp, "using DigitalFilter
> followed by the full src block in the *Messages* buffer.  So it seems
> that the search for the file name is using the contents of the block.
> Switching to the wip-cite-new branch (since I'm playing with that in any
> case) solves the problem for me so no panic.
> thank you,
> eric

  reply	other threads:[~2021-05-05 13:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-05 13:38 tangling seems to have broken today Eric S Fraga
2021-05-05 13:41 ` Timothy [this message]
2021-05-05 13:45   ` Bastien
2021-05-05 16:22     ` [PATCH] " Sébastien Miquel
2021-05-06 11:14       ` Bastien
2021-05-06 11:35         ` Sébastien Miquel
2021-05-06 11:38           ` Bastien
2021-05-06 11:19       ` Bastien
2021-05-05 13:54 ` Sébastien Miquel
2021-05-05 14:08   ` Eric S Fraga
2021-05-05 14:17     ` Sébastien Miquel
2021-05-05 14:20       ` Eric S Fraga

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=87h7jhl2l7.fsf@gmail.com \
    --to=tecosaur@gmail.com \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \


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