From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Carlos Pita <carlosjosepita@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Problems with yasnippet enabled in hidden font locking buffer
Date: Wed, 27 Mar 2019 15:31:15 +0100 [thread overview]
Message-ID: <878sx0z8wc.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAELgYhd4fMRJ059Y-BbCBNTmFQPwStt4ifzBwTAoAcwzZYJt9w@mail.gmail.com> (Carlos Pita's message of "Tue, 26 Mar 2019 14:43:56 -0300")
Hello,
Carlos Pita <carlosjosepita@gmail.com> writes:
> I've been having problems with latex font locking the first time the
> internal font locking buffer is created (this with native latex
> fontification). It was hard to debug but at a point it became obvious that
> the culprit was yas minor mode, which I had globally enabled. I don't think
> this global minor mode should be enabled in hidden buffers and I requested
> this to be changed [1]. I'll keep you informed of any advance regarding
> this matter but, anyway, maybe org mode could also add a hook to
> yas-dont-activate-functions in order to disable activation when the buffer
> name matches an org mode specific pattern/prefix. Short of every concerned
> user taking action here, at least one of the interacting parties (org and
> snippet) would have to compromise: (i) yasnippet by disabling its global
> minor mode for all hidden buffers and/or those matching an org specific
> pattern and/or (ii) org by including a yasnippet specific filter. IMO the
> best solution is what I described above: yasnippet disabling its global
> minor mode for *all* hidden buffers.
I don't think the issue belongs to the Org side, and Org needs not be
aware of Yasnippets.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2019-03-27 14:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 17:43 Problems with yasnippet enabled in hidden font locking buffer Carlos Pita
2019-03-27 14:31 ` Nicolas Goaziou [this message]
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=878sx0z8wc.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=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).