From: Anoop GR <anoopemacs@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: ob-clojure breaks tangling of comments using org-babel-tangle for clojure source code blocks
Date: Tue, 15 Oct 2024 23:22:06 +0530 [thread overview]
Message-ID: <CACabEsS_n36rsS0Noh5Dmnntsd-U8ZWu8XMdFT5rjiXBX8rSNA@mail.gmail.com> (raw)
In-Reply-To: CACabEsQU7W4SOOUgH-BnqB4JrQTR6wT40E2Jy_Zw88ij95LLGA@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 1756 bytes --]
The contents of the tangled output.clj file were:-
---
(def e 2.72)
(def pi 3.14) ;;This is a comment not on a line of its own
---
On Tue, Oct 15, 2024 at 11:21 PM Anoop GR <anoopemacs@gmail.com> wrote:
> The contents of the org file were
> ---
> This file contains only two source blocks
> #+begin_src clojure :noweb-ref "Define a constant"
> (def e 2.72)
> ;;This is a comment on a line of its own
> (def pi 3.14) ;;This is a comment not on a line of its own
> #+end_src
>
> The following block will be tangled
> #+begin_src clojure :noweb yes :tangle output.clj
> <<Define a constant>>
> #+end_src
> ---
>
> On Tue, Oct 15, 2024 at 11:13 PM Anoop GR <anoopemacs@gmail.com> wrote:
>
>> Comments in org babel clojure blocks are not tangled out.
>>
>> Let us take an example org file with the following contents:-
>>
>> This org file contains only two source blocks and a total of ten lines.
>>> #+begin_src clojure :noweb-ref "Define a constant"
>>>
>> (def e 2.72)
>>
>> ;;This is a comment on a line of its own
>>> (def pi 3.14) ;;This is a comment not on a line of its own
>>> #+end_src
>>
>> The following block will be tangled
>>> #+begin_src clojure :noweb yes :tangle ./output.clj
>>> <<Define a constant>>
>>> #+end_src
>>
>>
>> When I tangle the above file, the contents of the output.clj file are:-
>>
>>> (def e 2.72)
>>
>>
>>> (def pi 3.14) ;;This is a comment not on a line of its own
>>
>>
>> *The comment that was on a line of its own is missing from the tangled
>> output.*
>>
>> Was able to reproduce on both emacs 29.3.50 and 29.4 on Ubuntu 22.04 LTS
>> Both were started using *emacs -Q* and then evaluating *(require
>> 'ob-clojure)* as the only line of config.
>>
>
[-- Attachment #2: Type: text/html, Size: 3325 bytes --]
next prev parent reply other threads:[~2024-10-15 17:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 17:43 ob-clojure breaks tangling of comments using org-babel-tangle for clojure source code blocks Anoop GR
2024-10-15 17:51 ` Anoop GR
2024-10-15 17:52 ` Anoop GR [this message]
2024-10-15 17:53 ` Anoop GR
2024-10-16 19:49 ` Ihor Radchenko
2024-10-17 13:42 ` Anoop GR
2024-10-17 17:59 ` Ihor Radchenko
2024-10-18 10:18 ` Anoop GR
2024-10-18 17:23 ` Ihor Radchenko
2024-10-18 20:16 ` Anoop GR
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=CACabEsS_n36rsS0Noh5Dmnntsd-U8ZWu8XMdFT5rjiXBX8rSNA@mail.gmail.com \
--to=anoopemacs@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
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).