From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Fwd: demoting a heading inserts spaces in column-0 text Date: Tue, 23 Dec 2014 09:41:35 +0100 Message-ID: <87r3vq3ghs.fsf@nicolasgoaziou.fr> References: <87k326i71d.wl-n142857@gmail.com> <871tod3bu5.fsf@nicolasgoaziou.fr> <87388mvxgd.fsf@nicolasgoaziou.fr> <87lhmbrgi1.wl-n142857@gmail.com> <87bnn7aio3.fsf@nicolasgoaziou.fr> <87k31vr7pi.wl-n142857@gmail.com> <877fxvabdz.fsf@nicolasgoaziou.fr> <87iohequ70.wl-n142857@gmail.com> <87sig7x6ij.fsf@nicolasgoaziou.fr> <864msn900t.fsf@example.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56683) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y3L1e-0005mH-A1 for emacs-orgmode@gnu.org; Tue, 23 Dec 2014 03:41:15 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y3L1V-0007hI-KA for emacs-orgmode@gnu.org; Tue, 23 Dec 2014 03:41:06 -0500 Received: from plane.gmane.org ([80.91.229.3]:59511) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y3L1V-0007h6-Dw for emacs-orgmode@gnu.org; Tue, 23 Dec 2014 03:40:57 -0500 Received: from public by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Y3L1T-0004Az-1G for emacs-orgmode@gnu.org; Tue, 23 Dec 2014 09:40:55 +0100 In-Reply-To: <864msn900t.fsf@example.com> (Sebastien Vauban's message of "Mon, 22 Dec 2014 16:28:34 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Sebastien Vauban Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org Hello, Sebastien Vauban writes: > Regarding CLOCK lines, I guess we all agree it's not user-input, but > data managed by Org, right? Right. But the problem, which I explained already, is different here. > - user-inputted text > - Org-managed stuff (such as clock line, timestamps or property drawers) > > Note that I wrote timestamps instead of planning info because I also > would find it clearer to get: > >>> **** Some text >>> [2014-12-14 Sun 18:55] > > than > >>> **** Some text >>> [2014-12-14 Sun 18:55] > > (when one wants to insert the timestamp in a captured note or task) This is not possible in the general case since timestamps can be located almost anywhere. I suggest to live with it. >> Again, I suggest to sync indentation of planning info and all adjacent >> drawers. Nothing smarter. > > Including the LOGBOOK, then? That would already fulfill several above > cases IIUC As long as LOGBOOK is located at the top of the section, right after planning info or some drawers, it should be fine. If it is located elsewhere, it will not be indented automatically. > not the timestamp one, though. See above. Regards, -- Nicolas Goaziou