From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Clemente Subject: Re: demoting a heading inserts spaces in column-0 text Date: Thu, 11 Dec 2014 19:36:58 +0700 Message-ID: References: <87k326i71d.wl-n142857@gmail.com> <871tod3bu5.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=f46d043d66f542f9260509f0083f Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49222) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xz2zQ-0007qP-Si for emacs-orgmode@gnu.org; Thu, 11 Dec 2014 07:37:09 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xz2zM-0004Wq-P1 for emacs-orgmode@gnu.org; Thu, 11 Dec 2014 07:37:04 -0500 Received: from mail-wi0-x22b.google.com ([2a00:1450:400c:c05::22b]:51010) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xz2zM-0004Wa-Dg for emacs-orgmode@gnu.org; Thu, 11 Dec 2014 07:37:00 -0500 Received: by mail-wi0-f171.google.com with SMTP id bs8so14416693wib.4 for ; Thu, 11 Dec 2014 04:36:59 -0800 (PST) In-Reply-To: <871tod3bu5.fsf@nicolasgoaziou.fr> 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: Org-mode Org-Mode --f46d043d66f542f9260509f0083f Content-Type: text/plain; charset=ISO-8859-1 > > Proposal: if text starts in column 0, don't move the text; move > > only the headers. > > Then, in this case, :CLOCK: drawer will not move either. Unless > "headers" is defined as "stuff not too far from the headline". But it is > too vague to be usable. > There no such thing as a your "headers" in Org. :CLOCK: and "Text" are > treated equally, as contents of the headline. Of course everything's text, but if there's no distinction between drawers/headers and text, that's the problem. Those headers are metadata written and managed by org and must follow some rules, whereas the rest of text is data typed by the user and relatively free. Those headers must even follow strict processes (like being "repaired" to make CLOCK appear after PROPERTIES), so I wouldn't say they are normal text. Maybe you are referring to the non-drawers metadata, i.e. to those notes that you can add with C-c C-z. That's in the limbo between org data and text, that's the tricky part. I don't know whether that should be indented together with the drawers, probably yes. So, I think org should detect its own syntax (:CLOCK: ... :END: etc.), and do automatic changes only to its own syntax, not to text typed by the user unless the user asks for it. -- Daniel On Sat, Dec 6, 2014 at 6:40 AM, Nicolas Goaziou wrote: > Hello, > > Daniel Clemente writes: > > > There was a change (cba2f0a2a3024ae5bf71e1a12ba99778a92902a2, Sat > > Nov 8 14:35:24 2014 +0100) which made :CLOCK: etc entries shift to > > the right when the tree is being shifted to the right ("demoted", > > e.g. using M-S-Right). > > > > > > But now it changes from this: > > > > **** some > > :CLOCK: > > CLOCK: [2013-11-12 Sel 10:45]--[2013-11-12 Sel 11:40] => 0:55 > > :END: > > Text > > > > > > > > to this: > > > > ***** some > > :CLOCK: > > CLOCK: [2013-11-12 Sel 10:45]--[2013-11-12 Sel 11:40] => 0:55 > > :END: > > Text > > > > > > > > while what I expected was this: > > > > ***** some > > :CLOCK: > > CLOCK: [2013-11-12 Sel 10:45]--[2013-11-12 Sel 11:40] => 0:55 > > :END: > > Text > > > > > > > > > > Proposal: if text starts in column 0, don't move the text; move > > only the headers. > > Then, in this case, :CLOCK: drawer will not move either. Unless > "headers" is defined as "stuff not too far from the headline". But it is > too vague to be usable. > > > An old behaviour (reported in > http://permalink.gmane.org/gmane.emacs.orgmode/92450) was not to move > anything in this case, that's bad and was fixed. I think the proposal is > better. > > org-adapt-indentation=nil would write all headers in column 0 by > > default, which is ugly and doesn't give the desired result. > > There no such thing as a your "headers" in Org. :CLOCK: and "Text" are > treated equally, as contents of the headline. > > > Regards, > > -- > Nicolas Goaziou > --f46d043d66f542f9260509f0083f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

> >    Proposal: if text sta= rts in column 0, don't move the text; move
> >    only the headers.
>
> Then, in this case, :CLOCK: drawer will not move either. Unless
> "headers" is defined as "stuff not too far from the hea= dline". But it is
> too vague to be usable.

> There no such thing as a your "header= s" in Org. :CLOCK: and "Text" are
> treated equally, as contents of the headline.

  Of course everything's text, but if there's no dis= tinction between drawers/headers and text, that's the problem. Those he= aders are metadata written and managed by org and must follow some rules, w= hereas the rest of text is data typed by the user and relatively free. Thos= e headers must even follow strict processes (like being „repaired&ldq= uo; to make CLOCK appear after PROPERTIES), so I wouldn't say they are = normal text.
  Maybe you are referring to the non-drawer= s metadata, i.e. to those notes that you can add with C-c C-z. That's i= n the limbo between org data and text, that's the tricky part. I don= 9;t know whether that should be indented together with the drawers, probabl= y yes.
  So, I think org should detect its own syntax (:= CLOCK: … :END: etc.), and do automatic changes only to its own synta= x, not to text typed by the user unless the user asks for it.

--
Daniel

On Sat, Dec 6, 20= 14 at 6:40 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr>= wrote:
Hello,

Daniel Clemente <n142857@gmail.com<= /a>> writes:

>   There was a change (cba2f0a2a3024ae5bf71e1a12ba99778a92902= a2, Sat
>   Nov 8 14:35:24 2014 +0100) which made :CLOCK: etc entries = shift to
>   the right when the tree is being shifted to the right (&bd= quo;demoted“,
>   e.g. using M-S-Right).
>
>
> But now it changes from this:
>
> **** some
>       :CLOCK:
>       CLOCK: [2013-11-12 Sel 10:45]--[2013-11-12 S= el 11:40] =3D>  0:55
>       :END:
> Text
>
>
>
>   to this:
>
> ***** some
>        :CLOCK:
>        CLOCK: [2013-11-12 Sel 10:45]--[2013-11-12 = Sel 11:40] =3D>  0:55
>        :END:
>  Text
>
>
>
>    while what I expected was this:
>
> ***** some
>        :CLOCK:
>        CLOCK: [2013-11-12 Sel 10:45]--[2013-11-12 = Sel 11:40] =3D>  0:55
>        :END:
> Text
>
>
>
>
>    Proposal: if text starts in column 0, don't move the = text; move
>    only the headers.

Then, in this case, :CLOCK: drawer will not move either. Unless=
"headers" is defined as "stuff not too far from the headline= ". But it is
too vague to be usable.

>    An old behaviour (reported in http://permalink.gm= ane.org/gmane.emacs.orgmode/92450) was not to move anything in this cas= e, that's bad and was fixed. I think the proposal is better.
>    org-adapt-indentation=3Dnil would write all headers in co= lumn 0 by
>    default, which is ugly and doesn't give the desired r= esult.

There no such thing as a your "headers" in Org. :CLOCK: an= d "Text" are
treated equally, as contents of the headline.


Regards,

--
Nicolas Goaziou

--f46d043d66f542f9260509f0083f--