From: Bastien <bastienguerry@googlemail.com>
To: User <spamfilteraccount@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Automatic indentation of org tree
Date: Tue, 28 Jul 2009 20:05:58 +0800 [thread overview]
Message-ID: <87r5w13taq.fsf@bzg.ath.cx> (raw)
In-Reply-To: <loom.20090728T041942-187@post.gmane.org> (User's message of "Tue, 28 Jul 2009 04:25:38 +0000 (UTC)")
User <spamfilteraccount@gmail.com> writes:
> It is a possible solution to the clean view problem mentioned in
> the org manuual:
>
> Indentation of text below headlines
>
> You may indent text below each headline to make the left
> boundary line up with the headline, like
>
> *** 3rd level
> more text, now indented
>
>
> A good way to get this indentation is by hand, and Org supports
> this with paragraph filling, line wrapping, and structure
> editing99 preserving or adapting the indentation as
> appropriate. A different approach would be to have a way to
> automatically indent lines according to outline structure by
> adding overlays or text properties. But I have not yet found a
> robust and efficient way to do this in large files.
>
> http://orgmode.org/manual/#Clean-view
>
>
> The solution I posted implements that different approach, so you
> don't have to do the indentation by hand.
Okay, I see.
I tested your code but there are several problems: it is not usable on
big files, and even on small files the auto-indentation is confusing.
For example, stars get indented while there should not.
I guess this is still work-in-progress -- hope you'll find ways to fix
the problems above!
--
Bastien
next prev parent reply other threads:[~2009-07-28 12:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 20:04 Automatic indentation of org tree User
2009-07-27 20:47 ` Bastien
2009-07-28 4:25 ` User
2009-07-28 12:05 ` Bastien [this message]
2009-07-28 19:32 ` User
2009-07-29 5:41 ` Bastien
2009-08-03 4:36 ` Carsten Dominik
2009-08-03 16:49 ` Eric S Fraga
2009-08-04 15:08 ` Carsten Dominik
2009-08-04 17:49 ` Eric S Fraga
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=87r5w13taq.fsf@bzg.ath.cx \
--to=bastienguerry@googlemail.com \
--cc=emacs-orgmode@gnu.org \
--cc=spamfilteraccount@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).