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: Sat, 22 Dec 2018 10:16:54 -0300 [thread overview]
Message-ID: <CAELgYheNETq5DFnKh99hJRUAZpLNhzUnMPSpv=rfWQRZqhgfvg@mail.gmail.com> (raw)
In-Reply-To: <87k1k2ynsh.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1272 bytes --]
>
>
> > Maybe you could rewrite my function in a better way using the
> > precomputed latex regexps and augmenting them with #+BEGIN/END
> > counterparts.
>
> Per above, I'm not really interested in writing yet another workaround
> for something that is going to fail anyway. For the time being, I just
> accept that fontification is not perfect.
>
Hi Nicolas, I understand this. It's just that I have been using an
extension function for editing complex documents with lots of blocks (latex
and org) and I've not yet seen any problem, while I quickly spot rough
edges otherwise. It's not like writing yet another workaround in an
accumulative fashion, since the fontification functions just work forward
as always and the extension function is the one taking care of finding the
opposite end, plus it's just one function for all types of blocks.
I've no problem in contributing a patch if you're not inclined to work in
this anymore. It will have to move the end searching logic out of
org-do-latex-and-related though. All in all I don't think there would be
more lines of code or complexity and all block types would be given the
same treatment, moreover it would be a bit more by the book. Give it a
chance :) Anyway, thank you for your work.
Best regards
--
Carlos
[-- Attachment #2: Type: text/html, Size: 1694 bytes --]
next prev parent reply other threads:[~2018-12-22 13:17 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
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 [this message]
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='CAELgYheNETq5DFnKh99hJRUAZpLNhzUnMPSpv=rfWQRZqhgfvg@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).