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, 13 Jan 2015 12:10:44 +0100 Message-ID: <87ppajc4wb.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> <87bnm8j628.wl-n142857@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37172) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YAzM1-0006Qu-Sg for emacs-orgmode@gnu.org; Tue, 13 Jan 2015 06:09:46 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YAzLy-0007oR-MA for emacs-orgmode@gnu.org; Tue, 13 Jan 2015 06:09:45 -0500 Received: from relay3-d.mail.gandi.net ([2001:4b98:c:538::195]:40587) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YAzLy-0007oN-FL for emacs-orgmode@gnu.org; Tue, 13 Jan 2015 06:09:42 -0500 In-Reply-To: <87bnm8j628.wl-n142857@gmail.com> (Daniel Clemente's message of "Fri, 09 Jan 2015 23:02:23 +0700") 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: Daniel Clemente Cc: Org-mode Org-Mode Daniel Clemente writes: >> >> Another option would be to have another option to indent only planning >> >> info, properties drawer, and every drawer located right after it, =C3= =A0 la >> >> `org-log-state-notes-insert-after-drawers'. At least, it couldn't bre= ak >> >> structure. > > Is this possible? Why wouldn't it? > This indents drawers located at the top, which I think is good > enough because it's where org puts the common ones by default. > Your examples are more complex, with drawers in the middle of the > text or in the middle of lists. In those cases you might need full > indentation, but people who only use :CLOCK: and SCHEDULED at the > top (and that's the default) could use this option. > This is not about =E2=80=9Eindenting by type=E2=80=9C, but about =E2=80= =9Eindenting until > point X=E2=80=9C, and the trick is to find the right X. This is what I explained already. Indenting by type will fail in some cases. Indenting until some location is fine, as long as we are cautious about the said location. > I'd rather have org-adapt-indentation =3D 'initial-only which works > like like org-adapt-indentation =3D nil with the extra that =E2=80=9EPr= operty > drawers and planning information is inserted indented=E2=80=9C. > > That is, new things appear with the same indentation as the element abo= ve. > And demoting doesn't indent anything. > > Example: > > > ** something > > > You press C-c C-s and you get: > > > ** something > SCHEDULED: <2051-01-09 Mon> > > > You press S-M-right and you get: > > > *** something > SCHEDULED: <2051-01-09 Mon> > > > The user can then manually decide whether he wants to correct > indentations for each line. I fail to see how this would be useful. In particular, it fails if the section has contents prior to the scheduling step. Also, it doesn't solve S=C3=A9bastien's problem. Regards,