From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: full production use of org-mode: time to say thanks again! Date: Mon, 11 Oct 2010 10:04:15 +0200 Message-ID: <664F7423-EE5E-40E8-B6B3-CE2EEB4E08BC@gmail.com> References: <87r5fzk5j5.wl%ucecesf@ucl.ac.uk> <20EA118D-E909-47F4-AEF8-8B1B929F5601@gmail.com> <87eibzfgia.wl%n.goaziou@gmail.com> <87bp720vwy.wl%ucecesf@ucl.ac.uk> <871v7xz182.wl%n.goaziou@gmail.com> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from [140.186.70.92] (port=45266 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P5DRf-0001Xs-MO for emacs-orgmode@gnu.org; Mon, 11 Oct 2010 04:09:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P5DMp-0004Fu-DP for emacs-orgmode@gnu.org; Mon, 11 Oct 2010 04:04:20 -0400 Received: from mail-ew0-f41.google.com ([209.85.215.41]:52938) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P5DMp-0004Fp-8L for emacs-orgmode@gnu.org; Mon, 11 Oct 2010 04:04:19 -0400 Received: by ewy5 with SMTP id 5so353208ewy.0 for ; Mon, 11 Oct 2010 01:04:18 -0700 (PDT) In-Reply-To: <871v7xz182.wl%n.goaziou@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: Nicolas Goaziou Cc: Eric S Fraga , org-mode mailing list Hi, On Oct 11, 2010, at 8:34 AM, Nicolas Goaziou wrote: > Hello, > > Could you try the following patch and tell me if it fixes your issue? A quick test shows that things seem to work well in inlinetasks which are properly ended with an END line. There is also a dirty form of inline tasks which allows only a planning line (SCHEDULED etc) and one or several drawers directly after the task line, and then no END line is necessary. But I guess it is fair to force the END line if you do want to have proper indentation. Eric Fraga, have you tested the patch yet? Please do so when you wake up from your two-week sleep, so that we can check this in. Thanks Nicolas! I am seeing now two things that should be added: - M-RET after inline tasks should ignore the inline task and make a new entry with normal indentation - Maybe I should treat inline tasks with proper END statement as a drawer and fold it? Comments? > > As a side note (to maintainers), the second patch isn't really needed, > but I thought, while I was at it, that it would make sense > (`org-inlinetask-min-level' doesn't need to be a boolean). Hmmm, what happens is a user has customized this variable and it has a value nil. I guess then your patch will break things? So I think we need to keep testing the value in the code, but it is OK to change the customize type. > > Regards, > > -- Nicolas > > <0001-Fix-indentation-of-text-after-an-inline-task.patch><0002- > inlinetask-Make-org-inlinetask-min-level-an-integer-.patch> - Carsten