From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Lundin Subject: Re: Re: Tagging a region of text without creating a branch Date: Mon, 12 Oct 2009 09:14:26 -0400 Message-ID: References: <87r5tc919n.wl@imapmail.org> <426ABD01-2F97-4F67-BC37-96C079DF94FC@gmail.com> <96F16419-FA3F-4C33-899B-1C79C0CC840F@gmail.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MxKjW-0005Pb-Rl for emacs-orgmode@gnu.org; Mon, 12 Oct 2009 09:14:38 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MxKjS-0005P5-DW for emacs-orgmode@gnu.org; Mon, 12 Oct 2009 09:14:38 -0400 Received: from [199.232.76.173] (port=36396 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MxKjS-0005P2-6q for emacs-orgmode@gnu.org; Mon, 12 Oct 2009 09:14:34 -0400 Received: from out1.smtp.messagingengine.com ([66.111.4.25]:38345) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MxKjR-0002w7-TC for emacs-orgmode@gnu.org; Mon, 12 Oct 2009 09:14:34 -0400 In-Reply-To: <96F16419-FA3F-4C33-899B-1C79C0CC840F@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Carsten Dominik Cc: Org Mode List 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. - Matt