From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Christoph Michelbach <michelbach94@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Feature Proposal: Titled Paragraphs
Date: Wed, 23 Oct 2019 18:44:40 +0200 [thread overview]
Message-ID: <87k18v5s3r.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <3eb58af3-c03b-4225-ec31-15321c05ceff@gmail.com> (Christoph Michelbach's message of "Wed, 23 Oct 2019 15:13:09 +0200")
Hello,
Christoph Michelbach <michelbach94@gmail.com> writes:
> I often write documents in org mode that are going to be exported to
> PDF via LaTeX and find myself writing something like
>
> \paragraph{Lorem Ipsum} Duis ac nibh cursus, elementum ipsum quis,
> faucibus sapien.
>
> \paragraph{Interdum} Cras volutpat, sem eu semper ultrices, risus
> lacus tempor erat, eu pulvinar magna arcu sit amet massa.
>
> a lot, therefore mixing very simple Latex into my org documents simply
> because I want titled paragraphs. This comes with the further
> disadvantage that there is no syntax highlighting for it while
> editing.
There is nothing wrong with using simple LaTeX in Org files, if you
intent to export to PDF. Org doesn't provide equivalents for \bigskip,
or \vspace, or \hfill…
Anyhow, you could use a macro, if you want to make it look more Org-ish,
or try to use keywords, e.g.,
#+attr_latex: :title Whatever
Foo...
Changing the syntax is the very last thing to consider, IMO.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2019-10-23 16:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 13:13 Feature Proposal: Titled Paragraphs Christoph Michelbach
2019-10-23 13:24 ` Fraga, Eric
2019-10-23 13:51 ` Christoph Michelbach
2019-10-23 14:18 ` Dominik Schrempf
2019-10-23 14:55 ` Loris Bennett
2019-10-24 7:50 ` Julius Müller
2019-10-23 14:20 ` Fraga, Eric
2019-10-23 16:44 ` Nicolas Goaziou [this message]
2019-10-24 5:20 ` Fraga, Eric
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=87k18v5s3r.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=michelbach94@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).