emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Tom Gillespie <tgbugs@gmail.com>
Cc: flare <gabrielxaviersmith@gmail.com>,
	emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [FEATURE REQUEST] No tangle of code blocks within archived subtrees
Date: Sun, 06 Sep 2020 11:36:59 +0200	[thread overview]
Message-ID: <87sgbvnt50.fsf@bzg.fr> (raw)
In-Reply-To: CA+G3_PMQLgCd6zvOosZUZoqgfeNctRHu+RV4O_FWgAjM3M6mRw@mail.gmail.com

Hi Tom,

Tom Gillespie <tgbugs@gmail.com> writes:

>    This seems like it is probably a bug given that everything else
> about archive headings is disabled.

Yes, I agree this should considered as a bug.

I have a fix for it, which is to ignore archived subtrees along with
commented ones when tangling.

org-in-commented-heading-p is used in these Babel functions:

- org-babel-exp-process-buffer
- org-babel-ref-resolve
- org-babel-expand-noweb-references

Should we treat archived subtrees like commented ones in these
contexts too?  Respectively when exporting, resolving refs and
expanding noweb references?

I'd favor such an equal treatment of commented/archived subtrees but
I'd like to make sure it sounds good to everyone before.

-- 
 Bastien


  reply	other threads:[~2020-09-06  9:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-05  1:31 [FEATURE REQUEST] No tangle of code blocks within archived subtrees flare
2020-09-05  4:48 ` Tom Gillespie
2020-09-06  9:36   ` Bastien [this message]
2020-09-06 10:00     ` Tom Gillespie
2020-09-07  4:52       ` Bastien
2020-09-08  6:54         ` Tom Gillespie

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=87sgbvnt50.fsf@bzg.fr \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=gabrielxaviersmith@gmail.com \
    --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).