emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Berry, Charles" <ccberry@ucsd.edu>
To: Eric S Fraga <esflists@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
	"Alain.Cochard@unistra.fr" <Alain.Cochard@unistra.fr>,
	Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Problems created by inlinetasks in agenda views
Date: Mon, 16 Apr 2018 17:25:10 +0000	[thread overview]
Message-ID: <307DB3FB-6E6B-4B18-B5B2-645DDDC1592E@ucsd.edu> (raw)
In-Reply-To: <87d0yzfdwu.fsf@gmail.com>



> On Apr 16, 2018, at 7:01 AM, Eric S Fraga <esflists@gmail.com> wrote:
> 
> So, you have motivated me to look at alternatives just in case.  I've
> started playing with the export settings for drawers for odt and
> LaTeX.  It does seem like I can move to using drawers instead of inline
> tasks for all of my uses *except* for actual tasks.

Drawers would probably work for me, too. 

I use inlinetasks tagged :noexport: to contain babel code I might want to run in the course of document preparation, but not on export.

I guess I can omit drawers that are not to be exported according to the drawer-name with my own `format-drawer-function' variants.  But if tags or some equivalent convention get added to drawers, maybe a :noexport: tag would help my case.

I'd just have to convert my existing org files.

Chuck

  parent reply	other threads:[~2018-04-16 17:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-13 14:24 Problems created by inlinetasks in agenda views Alain.Cochard
2018-04-16 12:08 ` Nicolas Goaziou
2018-04-16 14:01   ` Eric S Fraga
2018-04-16 16:39     ` Nicolas Goaziou
2018-04-16 17:01       ` Eric S Fraga
2018-04-16 17:25     ` Berry, Charles [this message]
2018-04-16 17:33       ` Nicolas Goaziou
2018-04-23 13:50   ` Alternatives to inlinetasks? [was: Problems created by inlinetasks in agenda views] Alain.Cochard
2018-04-23 14:21     ` Eric S Fraga
2018-04-23 16:03       ` Carsten Dominik
2018-04-23 21:08         ` Nicolas Goaziou
2018-04-23 21:31           ` Eric Abrahamsen
2018-04-24 11:47             ` Kaushal Modi
2018-04-24 16:01               ` Eric Abrahamsen
2018-04-24 20:22               ` Rasmus
2018-04-25  5:43           ` Carsten Dominik
2018-04-26 23:34             ` Bastien
2018-04-27  7:27               ` Eric S Fraga
2018-04-27  7:46                 ` Bastien
2018-04-27  7:57                   ` Eric S Fraga

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=307DB3FB-6E6B-4B18-B5B2-645DDDC1592E@ucsd.edu \
    --to=ccberry@ucsd.edu \
    --cc=Alain.Cochard@unistra.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=esflists@gmail.com \
    --cc=mail@nicolasgoaziou.fr \
    /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).