From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: [Patch] ob-tangle.el: New value 'ascii' for the header argument ':comments'
Date: Sat, 11 Jun 2022 11:20:02 +0000 [thread overview]
Message-ID: <87wndna1lp.fsf@posteo.net> (raw)
In-Reply-To: <87bkuzdahc.fsf@localhost> (Ihor Radchenko's message of "Sat, 11 Jun 2022 13:39:59 +0800")
Hi, Ihor, thanks for your comments,
Ihor Radchenko writes:
> Wouldn't it be better to supply a customization for
> org-babel-process-comment-text instead?
>
> I do not feel that per-src-block control on the comment type makes much
> sense here.
My first approach was actually to define some options for
org-babel-process-comment. But I noticed that a header with properties,
for example:
* Header
:PROPERTIES:
:FOO: var
:END:
is interpreted as:
;; Header
;; :FOO: var
I think the culprit is the '(match-end 0)' in
org-babel-tangle-single-block:
...
(comment
(when (or (string= "both" (cdr (assq :comments params)))
(string= "org" (cdr (assq :comments params))))
;; From the previous heading or code-block end
(funcall
org-babel-process-comment-text
(buffer-substring
(max (condition-case nil
(save-excursion
(org-back-to-heading t) ; Sets match data
(match-end 0)) ;; <=========
(error (point-min)))
(save-excursion
(if (re-search-backward
org-babel-src-block-regexp nil t)
(match-end 0) ;; <=========
(point-min))))
(point)))))
...
So I couldn't think of any other solution than to put the change there,
so as not to break backwards compatibility. But it is a somewhat tricky
solution...
Best regards,
Juan Manuel
next prev parent reply other threads:[~2022-06-11 11:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 18:28 [Patch] ob-tangle.el: New value 'ascii' for the header argument ':comments' Juan Manuel Macías
2022-06-11 5:39 ` Ihor Radchenko
2022-06-11 11:20 ` Juan Manuel Macías [this message]
2022-06-14 3:58 ` Ihor Radchenko
2022-06-14 11:11 ` Juan Manuel Macías
2022-06-14 11:55 ` Ihor Radchenko
2022-06-15 10:30 ` Juan Manuel Macías
2022-07-21 13:44 ` Juan Manuel Macías
2022-07-25 13:34 ` Ihor Radchenko
2022-07-25 17:13 ` Juan Manuel Macías
2022-07-26 5:35 ` Ihor Radchenko
2022-06-12 19:18 ` Rudolf Adamkovič
2022-06-12 19:55 ` Juan Manuel Macías
2022-06-13 8:24 ` Rudolf Adamkovič
2022-06-13 10:22 ` Juan Manuel Macías
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=87wndna1lp.fsf@posteo.net \
--to=maciaschain@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@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).