From: Carlos Pita <carlosjosepita@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: Add option to fontify latex blocks [9.1.9 (release_9.1.9-65-g5e4542 @ /home/carlos/local/stow/emacs-26/share/emacs/26.1.50/lisp/org/)]
Date: Tue, 27 Nov 2018 21:14:22 -0300 [thread overview]
Message-ID: <CAELgYhcDvkvur0LYh0aKn4AsSf9zWzX9PJ_Jc=8GQAiOYu-KmA@mail.gmail.com> (raw)
In-Reply-To: <87lg5ershk.fsf@nicolasgoaziou.fr>
> > 1. #+BEGIN_LATEX could be changed to honor current fontification
> > setting
>
> This construct doesn't exist in Org.
Yes, I realized after posting, it was suggested in reddit but I was
unable to find any reference to it in the source code. Maybe it did
exist in the past since it's often mentioned in stackexchange and
reddit.
> > 2. #+BEGIN_EXPORT latex should be changed to allow inline preview
> It is not a bug. Why would it be one?
The behavior of
(P) previews,
(E) C-c ' editing and
(F) native fontification
is very inconsistent for latex:
1. $xxx$ and $$xxx$$ no (F) no (E) but (P)
2. \begin{xxx}...\end{xxx} no (F) but (E) and (P)
3. #+BEGIN_EXPORT latex and #+LATEX no (P) but (E) and (F)
I understand the limited behavior of $...$ since it's intended to be
for short snippets.
The lack of features for $$...$$ is more questionable. And you can do
\begin{displaymath}, which is exactly the same, and get (E).
Anyway, if there were an option for long code fragments to be
correctly folded, fontified, edited and previewed I would pay the
price of the "#+BEGIN_EXPORT latex" extra typing. The only problem is
that previews are not working there. So why not activate previews
inside export environments of latex type to get the full combo?
Regards
--
Carlos
>
> Regards,
>
> --
> Nicolas Goaziou
next prev parent reply other threads:[~2018-11-28 0:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 22:32 Bug: Add option to fontify latex blocks [9.1.9 (release_9.1.9-65-g5e4542 @ /home/carlos/local/stow/emacs-26/share/emacs/26.1.50/lisp/org/)] Carlos Pita
2018-11-27 22:58 ` Carlos Pita
2018-11-27 23:49 ` Nicolas Goaziou
2018-11-28 0:14 ` Carlos Pita [this message]
2018-11-28 0:27 ` Carlos Pita
2018-11-28 1:22 ` Carlos Pita
2018-11-28 10:57 ` Nicolas Goaziou
2018-11-28 15:02 ` Carlos Pita
2018-11-28 16:55 ` Carlos Pita
2018-11-28 17:28 ` Carlos Pita
2018-11-28 18:38 ` Carlos Pita
2018-11-28 22:46 ` Carlos Pita
2018-12-03 3:54 ` Carlos Pita
2018-12-03 4:18 ` Carlos Pita
2018-12-19 21:42 ` Nicolas Goaziou
2018-12-21 23:37 ` Carlos Pita
2018-12-21 23:54 ` Carlos Pita
2018-12-22 0:42 ` Carlos Pita
2018-12-22 0:46 ` Carlos Pita
2018-12-22 2:38 ` Carlos Pita
2018-12-22 8:21 ` Nicolas Goaziou
2018-12-22 13:16 ` Carlos Pita
2018-12-22 15:07 ` Carlos Pita
2019-01-01 16:46 ` Nicolas Goaziou
2019-01-01 17:11 ` Carlos Pita
2019-01-01 17:14 ` Carlos Pita
2019-01-01 18:17 ` 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='CAELgYhcDvkvur0LYh0aKn4AsSf9zWzX9PJ_Jc=8GQAiOYu-KmA@mail.gmail.com' \
--to=carlosjosepita@gmail.com \
--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 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).