From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Fwd: demoting a heading inserts spaces in column-0 text
Date: Mon, 22 Dec 2014 16:28:34 +0100 [thread overview]
Message-ID: <864msn900t.fsf@example.com> (raw)
In-Reply-To: 87sig7x6ij.fsf@nicolasgoaziou.fr
Hello,
Nicolas Goaziou wrote:
> Daniel Clemente <n142857-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>> El Sat, 13 Dec 2014 15:10:32 +0100 Nicolas Goaziou va escriure:
>>>
>>> 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.
Regarding CLOCK lines, I guess we all agree it's not user-input, but
data managed by Org, right?
>>> So, what's wrong with `org-adapt-indentation' set to nil?
>>
>> This. By default (tested on emacs -Q), when you have this tree:
>>
>> **** Some text
>> Hi
>>
>> ...and you clock in, you get:
>>
>> **** Some text
>> CLOCK: [2014-12-14 Sun 18:55]--[2014-12-14 Sun 18:57] => 0:02
>> Hi
>>
>> Same with properties:
>> **** eeeee
>> :PROPERTIES:
>> :ou: 22
>> :END:
>> Text
>>
>> That is 1) uglier than the default.
>
> This is subjective.
I agree this is probably suggestive, but *I* also find it clearer to
have the indentation different for:
- 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)
> 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 -- not the timestamp one, though.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2014-12-22 15:28 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
[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 [this message]
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=864msn900t.fsf@example.com \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/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).