From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Daniel Clemente <n142857@gmail.com>
Cc: Org-mode Org-Mode <emacs-orgmode@gnu.org>
Subject: Re: demoting a heading inserts spaces in column-0 text
Date: Sat, 13 Dec 2014 15:10:32 +0100 [thread overview]
Message-ID: <877fxvabdz.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87k31vr7pi.wl-n142857@gmail.com> (Daniel Clemente's message of "Sat, 13 Dec 2014 20:38:01 +0700")
Daniel Clemente <n142857@gmail.com> writes:
> No need to teach the user the differences of a :CLOCK: vs
> a :PROPERTIES: or drawer vs. metadata.
The difference is important, e.g., wrt export.
> Users who type can do a simpler distinction:
> 1. things you type yourself
> 2. things that appear/change/disappear after invoking org functions
> (C-something, S-something, M-something). E.g.: the words SCHEDULED,
> TODO, CLOCK, PROPERTIES, EFFORT, checkboxes [ ], timestamps, …
>
> I speak for myself, but I expect class 1 not to be changed by org,
> and class 2 to be handled only by org (I can always edit manually, but
> I shouldn't need to do it). I know that you can actually type
> everything in class 2, but you shouldn't NEED to.
> Any other opinions are welcome.
You are free to make any distinction you want. Unfortunately, Org does
a different one. In particular, as you noticed, there are some areas
where things are not as clear. For example, Org cannot be sure that
a given drawer wasn't inserted manually, so altering its indentation may
or may not be a good choice.
> Indentation is for me as important as the other letters I type. I don't want it changed.
> It's a personal preference. Emacs respects it to great extents.
I understand. Simply set `org-adapt-indentation' to nil.
> Maybe I should clarify that I see the text inside my org files as
> a tree of knowledge. The position inside the tree of a particular item
> does not affect how I write the text (e.g. how many indentation
> spaces). I can move nodes freely from one place to another and I have
> no indentations to fix. „Tree structure“ and „item content“ are
> disconnected.
> If you really need other sources, you can see how tree operations in
> other contexts don't modify the contents of each node:
> http://pythonhosted.org/ete2/tutorial/tutorial_trees.html#concatenating-trees
> I wouldn't want titles, clocks, IDs, indentations, properties, priorities etc. changed when the tree structure changes.
> Maybe other people think the same; you can survey the list.
So, what's wrong with `org-adapt-indentation' set to nil?
> The only one: indentation is added:
>
>
> After demoting, 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
See above.
> That's similar to a not-so-bad old behaviour. But it's still a bit better (it avoids the problem described in http://permalink.gmane.org/gmane.emacs.orgmode/92450)
The problem described there is different: the OP wants some changes when
tree structure is modified (e.g., planning info moved). You claim to
want no change at all, which is easier, and already implemented.
>> AFAICT, you erroneously think regular drawers are an Org internal
>> artifact whereas they are really meant for users. They should be
>> indented like their contents, no like planning info.
>
> I do the typed-by-me/not-typed-by-me distinction.
See above.
> Ok, make it:
>
> 2. With org-adapt-indentation = 'partial, new lines added by org
> (:CLOCK: drawer, CLOCK lines etc) are indented at the same level as
> the element above.
This is better, but there is still the hack about text at column 0.
Also, this only makes sense if these lines are also moved when headline
is promoted or demoted. But, then, contents will change along with tree,
which you don't like, and it could break section structure (some lines
being moved and not others), which cannot happen currently.
Another option would be to have another option to indent only planning
info, properties drawer, and every drawer located right after it, à la
`org-log-state-notes-insert-after-drawers'. At least, it couldn't break
structure.
Regards,
next prev parent reply other threads:[~2014-12-13 14:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 13:02 demoting a heading inserts spaces in column-0 text Daniel Clemente
2014-12-05 23:40 ` Nicolas Goaziou
2014-12-11 12:36 ` Daniel Clemente
2014-12-12 18:25 ` Nicolas Goaziou
2014-12-13 10:28 ` Daniel Clemente
2014-12-13 11:33 ` Nicolas Goaziou
2014-12-13 13:38 ` Daniel Clemente
2014-12-13 14:10 ` Nicolas Goaziou [this message]
[not found] ` <87iohequ70.wl-n142857@gmail.com>
2014-12-22 5:43 ` Fwd: " Daniel Clemente
2014-12-22 11:34 ` Nicolas Goaziou
2014-12-22 15:28 ` Sebastien Vauban
2014-12-23 8:41 ` Nicolas Goaziou
2015-01-09 16:02 ` Daniel Clemente
2015-01-13 11:10 ` Nicolas Goaziou
2015-01-16 14:29 ` Daniel Clemente
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877fxvabdz.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=n142857@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).