From: Tom Gillespie <tgbugs@gmail.com>
To: Bastien <bzg@gnu.org>
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, 6 Sep 2020 03:00:11 -0700 [thread overview]
Message-ID: <CA+G3_PMW-DrqkVUSNLm_=WRQuTP86kYX+FmTJ6=B9TRQQst-aQ@mail.gmail.com> (raw)
In-Reply-To: <87sgbvnt50.fsf@bzg.fr>
Hi Bastien,
My initial reaction was to say yes to all of these in the name of
consistency, but there are nuances for org-babel-ref-resolve and
org-babel-expand-noweb-references that are different than for
org-babel-exp-process-buffer. If I have a block that nowebbs in
another block, and at some point that other block is archived, do we
treat it as if the block never existed? I don't think we do. Same for
org-babel-ref-resolve. Those names exist and we know they exist, we
just don't display/export them. I'm basing this on the assumption that
users who archive headings don't want to see them/search them, not
that they wanted to remove them entirely or refactor things related to
them. It might make sense to warn if a block that is nowebbed in has
been archived so the user can do something about it if they want, but
I think having archiving effectively induce a null pointer is a bad
idea. I wonder what other perspectives there are on this. Best!
Tom
On Sun, Sep 6, 2020 at 2:37 AM Bastien <bzg@gnu.org> wrote:
> - org-babel-exp-process-buffer
Yes
> - org-babel-ref-resolve
Probably not?
> - org-babel-expand-noweb-references
Probably not?
next prev parent reply other threads:[~2020-09-06 10:01 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
2020-09-06 10:00 ` Tom Gillespie [this message]
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='CA+G3_PMW-DrqkVUSNLm_=WRQuTP86kYX+FmTJ6=B9TRQQst-aQ@mail.gmail.com' \
--to=tgbugs@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=gabrielxaviersmith@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).