From: Emanuel Evans <mail@emanuel.industries>
To: emacs-orgmode@gnu.org
Subject: Re: bug#21818: 24.5; org-set-tags-to indentation problems when called programmatically
Date: Thu, 19 Nov 2015 10:39:27 -0800 [thread overview]
Message-ID: <874mghrfz4.fsf@emanuel.industries> (raw)
In-Reply-To: 87h9kil72a.fsf@nicolasgoaziou.fr
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> I don't consider it to be a bug.
>
> `org-element-interpret-data' produces a string, which is expected to be
> syntactically correct, but doesn't guarantee aesthetics. In particular,
> `org-element-headline-interpreter' tries to align tags as accurately as
> possible, but, in this case, fails to succeed as it would require to
> introduce fontification in the process. This is out of the scope of the
> function.
Hmmm, that doesn't really make sense to me. Shouldn't the flow of
1. Edit a document with org-mode
2. (org-element-interpret-data (org-element-parse-buffer))
be as close to the original as possible? Seems like the fontification
aspect is just an implementation detail. In any case, I looked more into
the code and would be happy to submit a patch to change it if it makes
sense to you.
- Emanuel
next prev parent reply other threads:[~2015-11-19 18:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 5:40 bug#21818: 24.5; org-set-tags-to indentation problems when called programmatically mail
2015-11-03 15:26 ` Eli Zaretskii
[not found] ` <87bnbbvtkm.fsf@emanuel.industries>
2015-11-03 20:54 ` Eli Zaretskii
2015-11-03 21:25 ` Emanuel Evans
2015-11-03 21:25 ` Emanuel Evans
2015-11-03 20:54 ` Eli Zaretskii
2015-11-04 17:36 ` Glenn Morris
2015-11-04 18:18 ` Emanuel Evans
2015-11-04 23:01 ` Emanuel Evans
2015-11-05 0:39 ` Emanuel Evans
2015-11-05 8:14 ` Nicolas Goaziou
2015-11-05 11:29 ` Nicolas Goaziou
2015-11-05 17:02 ` Emanuel Evans
2015-11-16 3:58 ` Emanuel Evans
2015-11-19 8:36 ` Nicolas Goaziou
2015-11-19 18:39 ` Emanuel Evans [this message]
2015-11-20 13:19 ` Nicolas Goaziou
2017-12-03 16:24 ` Nicolas Goaziou
2015-11-04 17:36 ` Glenn Morris
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874mghrfz4.fsf@emanuel.industries \
--to=mail@emanuel.industries \
--cc=emacs-orgmode@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.