From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: How to define TODOs within continuous text the best way? Date: Wed, 1 Apr 2009 12:05:14 +0200 Message-ID: <6D423B50-3C65-4F7E-A527-04C554BA92E9@gmail.com> References: <49CE32EC.5060508@gmx.de> <51053970-C604-4B96-B3D5-B9F79BD0472C@gmail.com> <87wsa5h3k6.fsf@CPU107.opentrends.net> Mime-Version: 1.0 (Apple Message framework v930.3) Content-Type: multipart/mixed; boundary="===============1504433672==" Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LoxK0-0001oO-Nx for emacs-orgmode@gnu.org; Wed, 01 Apr 2009 06:05:24 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LoxJu-0001fg-GG for emacs-orgmode@gnu.org; Wed, 01 Apr 2009 06:05:23 -0400 Received: from [199.232.76.173] (port=55094 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LoxJt-0001f7-MZ for emacs-orgmode@gnu.org; Wed, 01 Apr 2009 06:05:18 -0400 Received: from mail-ew0-f160.google.com ([209.85.219.160]:54739) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LoxJs-0003yj-VD for emacs-orgmode@gnu.org; Wed, 01 Apr 2009 06:05:17 -0400 Received: by ewy4 with SMTP id 4so3126393ewy.42 for ; Wed, 01 Apr 2009 03:05:16 -0700 (PDT) In-Reply-To: <87wsa5h3k6.fsf@CPU107.opentrends.net> 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: Daniel Clemente Cc: Org Mode List --===============1504433672== Content-Type: multipart/alternative; boundary=Apple-Mail-1-427593311 --Apple-Mail-1-427593311 Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable On Mar 31, 2009, at 9:53 PM, Daniel Clemente wrote: > El dl, mar 30 2009, Carsten Dominik va escriure: > >> I simply cannot believe that after all those years, we might be >> able to close this task. > > Wow, that's wonderful! Thanks for a so easy solution. > I was needing this functionality since a long time. > > > > About org-inlinetask-export: > > ,---- > | Documentation: > | What should be done with inlinetasks upon export? > | Possible values: > | > | nil Remove entirely > | arrow Insert heading in bold, preceeded by an arrow > | arrow+content Insert arrow and headline, add content below in an > | #+begin_example box (ugly, but works for now) > | > `---- > > Could you add that the =84Remove entirely=93 means =84Remove entirely = ... =20 > just the header (but not the content)=93? The "content" of an inline task is not the text up to the next heading, it usually is empty. However, I have implemented a hackers solution, so that you can do ***************** TODO my inline task DEADLINE... PROPERTIES... This is considered to be "content" of the inline task, up to this line: ***************** END I will make this clearer in the docs, the file header of org-inlinetask.el does describe this. - Carsten > > > -- Daniel > > > > _______________________________________________ > Emacs-orgmode mailing list > Remember: use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode --Apple-Mail-1-427593311 Content-Type: text/html; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable
On Mar 31, 2009, = at 9:53 PM, Daniel Clemente wrote:

El dl, mar 30 2009, Carsten Dominik va = escriure:

I simply cannot believe that = after all those years, we might be
able to close this task.

 Wow, = that's wonderful! Thanks for a so easy solution.
 I was needing = this functionality since a long time.



 About = org-inlinetask-export:

,----
| Documentation:
| What should = be done with inlinetasks upon export?
| Possible values:
|
| = nil =            Remove = entirely
| arrow =          Insert heading in = bold, preceeded by an arrow
| arrow+content  Insert arrow and = headline, add content below in an
| =             &n= bsp;  #+begin_example box (ugly, but works for now)
| =
`----

 Could you add that the =84Remove entirely=93 = means =84Remove entirely ... just the header (but not the = content)=93?


The = "content" of an inline task is not the text up to the next = heading,
it usually is = empty.

However, I have implemented a hackers = solution, so that you can = do


***************** TODO my = inline task
             =      DEADLINE...
       =           =  PROPERTIES...
           =        This is considered to be "content" of = the
               =    inline task, up to this line:
***************** = END


I will make this clearer in = the docs, the file header of
org-inlinetask.el does describe = this.

- Carsten



-- = Daniel



_______________________________________________
E= macs-orgmode mailing list
Remember: use `Reply All' to send replies = to the list.
Emacs-orgmode@gnu.org
http://= lists.gnu.org/mailman/listinfo/emacs-orgmode
<= br>= --Apple-Mail-1-427593311-- --===============1504433672== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode --===============1504433672==--