From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Sebastien Vauban
<public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: Fwd: demoting a heading inserts spaces in column-0 text
Date: Tue, 23 Dec 2014 09:41:35 +0100 [thread overview]
Message-ID: <87r3vq3ghs.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <864msn900t.fsf@example.com> (Sebastien Vauban's message of "Mon, 22 Dec 2014 16:28:34 +0100")
Hello,
Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
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
next prev parent reply other threads:[~2014-12-23 8:41 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
2014-12-23 8:41 ` Nicolas Goaziou [this message]
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=87r3vq3ghs.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
--cc=public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.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).