From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Dmitry Alexandrov <321942@gmail.com>
Cc: 31273@debbugs.gnu.org
Subject: bug#31273: 27.0.50; org: #+begin_right block is not exported correctly
Date: Sat, 28 Apr 2018 18:23:38 +0200 [thread overview]
Message-ID: <87h8nvqoz9.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87wowr8hwh.fsf@gmail.com> (Dmitry Alexandrov's message of "Sat, 28 Apr 2018 18:33:50 +0300")
Dmitry Alexandrov <321942@gmail.com> writes:
> Just another unofficial reference card [0], by Caio Rordrigues at that time, that again states that:
>
> #+begin_right This text is aligned to the right! #+end_right
>
> These persons are probably consider themselves highly familiar with
> Org, yet they have been mistaken. What to say about novices! So the
> absence of this feature is indeed highly unobvious. That’s the only
> point I am trying to make.
>
> [0] https://github.com/caiorss/Emacs-Elisp-Programming/blob/master/Org-Mode.org#text-position
>
>> In any case, let me insist again on the following point: you can use
>> "#+begin_right" in HTML to your heart's content if you define the
>> appropriate CSS property.
>
> If there is no plan to make into default as with centring, a warning
> might be very apt.
The issue here is that "#+begin_right" is perfectly valid syntax, and so
is, e.g., "#+begin_foobar". Their behaviour is perfectly defined. For
example, in HTML export the will create <div class="right"> and <div
class="foobar"> if you have a nil `org-html-html5-fancy', or <right> and
<foobar> otherwise.
Therefore, a warning is not an option here. Only a careful read of the
manual can help clearing the misconception about what is included in Org
and what can be extended.
Now, it's true that at some point, Org defined a ".right" CSS rule
instead of ".org-right", so "#+begin_right" could work out of the box, but
only in the HTML export. However, this was not the intent.
For the record any "#+begin_XXX" construct that has no particular
meaning in Org may be treated specially by export back-ends (or ignored
altogether). It is often a way to write a specific environment.
next prev parent reply other threads:[~2018-04-28 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87bme6gg7i.fsf@gmail.com>
2018-04-28 14:08 ` bug#31273: 27.0.50; org: #+begin_right block is not exported correctly Nicolas Goaziou
2018-04-28 14:53 ` Dmitry Alexandrov
2018-04-28 15:12 ` Nicolas Goaziou
2018-04-28 15:33 ` Dmitry Alexandrov
2018-04-28 16:23 ` Nicolas Goaziou [this message]
2018-07-07 11:11 ` Nicolas Goaziou
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=87h8nvqoz9.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=31273@debbugs.gnu.org \
--cc=321942@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).