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 17:12:51 +0200 [thread overview]
Message-ID: <87lgd7qs98.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87k1sr9ycb.fsf@gmail.com> (Dmitry Alexandrov's message of "Sat, 28 Apr 2018 17:53:24 +0300")
Dmitry Alexandrov <321942@gmail.com> writes:
> Now, I am not sure, whether am I supposed to use #+begin_org-center
> blocks instead of #+begin_center too.
The latter. As I explained, ".org-center" is an internal style.
> In fact, given that #+begin_center creates a .org-center div block,
> that is centred by default CSS (and stylesheets of other formats),
> I found your answer absolutely surprising.
"Center" blocks are defined in the manual, along with their syntax.
There is nothing surprising.
Moreover, there is no such thing as a "Right" block. Or, more precisely,
this falls into the special block category, which is handled differently
in each export back-end.
> I would be probably not alone on this feeling; see, for instance,
> Fabrice Niessen’s Org mode syntax reference card [0], where (as far as
> I got it) #+begin_right is presented as alignment tag for paragraphs
> rather than tables:
This reference card is not an official reference card.
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.
next prev parent reply other threads:[~2018-04-28 15:13 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 [this message]
2018-04-28 15:33 ` Dmitry Alexandrov
2018-04-28 16:23 ` Nicolas Goaziou
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=87lgd7qs98.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).