From: Matthew Lundin <mclundin@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Matt Lundin <mclundin@gmail.com>, Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Tagging a region of text without creating a branch
Date: Mon, 12 Oct 2009 09:40:25 -0400 [thread overview]
Message-ID: <m2k4z0688m.fsf@fastmail.fm> (raw)
In-Reply-To: <63255A67-9D91-414F-AEBB-B3D6D12015D1@gmail.com> (Carsten Dominik's message of "Mon, 12 Oct 2009 15:27:37 +0200")
Carsten Dominik <carsten.dominik@gmail.com> writes:
> On Oct 12, 2009, at 3:14 PM, Matt Lundin wrote:
>
>> At Mon, 12 Oct 2009 09:29:05 +0200,
>> Carsten Dominik wrote:
>>>
>>> On Oct 10, 2009, at 5:39 PM, Matt Lundin wrote:
>>>
>>>> Hi Carsten,
>>>>
>>>> Carsten Dominik wrote:
>>>>>
>>>>> Yes, this should now work. Good catch.
>>>>>
>>>>> You method with the tag on the END line would even be harmful, as
>>>>> it
>>>>> removes any text after the END line, up to the next heading.
>>>>>
>>>>> Can you show me the use case for not exporting inline tasks?
>>>>> Maybe I
>>>>> need to bring that variable back, if there is a good case for
>>>>> it....
>>>>
>>>> Now that I am doing more of my writing in org-mode, I plan to use
>>>> inline tasks for marking up my drafts with TODOs. These reminders
>>>> would be "for my eyes only." When I publish the draft to LaTeX or
>>>> html
>>>> for sharing, I would thus prefer that the inline tasks be excluded.
>>>
>>> OK, I have re-introduced the variable org-inlinetask-export, as a
>>> Boolean. Do we need to be able to set this on a per-file basis?
>>
>> Thanks Carsten! An option to set per-file would indeed be nice. For
>> instance, if I'm working on an article, I might want to share one
>> version of it without visible inline tasks/comments and another with
>> them.
>>
>> That said, I suppose I could use local variables to do this.
>
> Local variables will not work, but #+BIND will.
>
> I guess this will be enough....
Absolutely!
Thanks again,
Matt
prev parent reply other threads:[~2009-10-12 13:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 16:06 Tagging a region of text without creating a branch bar tomas
2009-10-08 18:10 ` Matt Lundin
2009-10-08 20:18 ` Bernt Hansen
[not found] ` <1f38ae890910090023h2b5cb320y1d2d778c1037d752@mail.gmail.com>
2009-10-09 7:26 ` Andrew Stribblehill
2009-10-09 13:19 ` Bernt Hansen
[not found] ` <fdcd75820910090229v39ec6e47m1037cb46afde19a5@mail.gmail.com>
2009-10-09 12:53 ` Matt Lundin
2009-10-09 14:05 ` bar tomas
2009-10-09 14:43 ` Stephan Schmitt
2009-10-09 15:01 ` bar tomas
2009-10-09 17:45 ` Carsten Dominik
2009-10-09 17:58 ` Matthew Lundin
2009-10-10 14:56 ` Carsten Dominik
2009-10-10 15:39 ` Matt Lundin
2009-10-12 7:29 ` Carsten Dominik
2009-10-12 13:14 ` Matt Lundin
2009-10-12 13:27 ` Carsten Dominik
2009-10-12 13:40 ` Matthew Lundin [this message]
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=m2k4z0688m.fsf@fastmail.fm \
--to=mclundin@gmail.com \
--cc=carsten.dominik@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).