From: "Berry, Charles" <ccberry@ucsd.edu>
To: Carlos Pita <carlosjosepita@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Feature Request: allow export yes/no for blocks that are valid babel inputs
Date: Sun, 24 Mar 2019 16:30:09 +0000 [thread overview]
Message-ID: <F9806F2F-BD5E-4ADE-8E2A-989F76E31E8B@ucsd.edu> (raw)
In-Reply-To: <CAELgYhdDoCZtWaNqerGRodnnT_SMHGB-LDkF9BORY7kkA2PeKQ@mail.gmail.com>
AFAICS, the functionality you seek already exists, although it is not heavily advertised.
`C-c C-x t' will insert an inline task. Within such a `task' you can put text, tables, src blocks and other objects.
Setting option `inline:nil' will prevent export, but leave the content visible to src blocks etc.
Alternatively, you can tag inlinetasks as with headlines to control their export.
Browse the commentary in org-inlinetask.el for more details.
HTH,
Chuck
> On Mar 23, 2019, at 2:20 PM, Carlos Pita <carlosjosepita@gmail.com> wrote:
>
> Hi all,
>
> when using lists, tables and example blocks as inputs to babel src
> blocks sometimes the inputs are just... inputs. There is some
> inconsistency in the fact that src blocks can be selectively exported
> but not their inputs. Commenting these inputs out makes them invisible
> to the block referencing them (apparently this method worked a time
> ago but it's not working now). OTOH using the noexport tag introduces
> spurious sections that interrupt the flow of the document and might be
> hard to close afterwards (similar to the boilerplate introduced by
> beamer blocks).
>
> What do you think of adding an :export yes/no parameter to these
> blocks? Or to blocks in general.
>
> Best regards
> --
> Carlos
>
>
next prev parent reply other threads:[~2019-03-24 16:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-23 21:20 Feature Request: allow export yes/no for blocks that are valid babel inputs Carlos Pita
2019-03-23 21:30 ` Carlos Pita
2019-03-23 21:35 ` Carlos Pita
2019-03-24 16:30 ` Berry, Charles [this message]
2019-04-16 21:13 ` Carlos Pita
2019-04-17 5:42 ` Fraga, Eric
2019-04-17 16:16 ` Berry, Charles
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=F9806F2F-BD5E-4ADE-8E2A-989F76E31E8B@ucsd.edu \
--to=ccberry@ucsd.edu \
--cc=carlosjosepita@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).