From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carlos Pita Subject: Problems with yasnippet enabled in hidden font locking buffer Date: Tue, 26 Mar 2019 14:43:56 -0300 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000002e78ad058502de16" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:49114) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h8q7O-0004Lg-LN for emacs-orgmode@gnu.org; Tue, 26 Mar 2019 13:44:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h8q7N-0000PM-Gl for emacs-orgmode@gnu.org; Tue, 26 Mar 2019 13:44:10 -0400 Received: from mail-yw1-xc2b.google.com ([2607:f8b0:4864:20::c2b]:32968) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1h8q7N-0000Mw-25 for emacs-orgmode@gnu.org; Tue, 26 Mar 2019 13:44:09 -0400 Received: by mail-yw1-xc2b.google.com with SMTP id l5so10347510ywa.0 for ; Tue, 26 Mar 2019 10:44:08 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode --0000000000002e78ad058502de16 Content-Type: text/plain; charset="UTF-8" Hi all, 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. Best regards -- Carlos [1] https://github.com/joaotavora/yasnippet/issues/985 --0000000000002e78ad058502de16 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,
<= br>
I've been having problems with latex font locking the fir= st 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 requ= ested this to be changed [1]. I'll keep you informed of any advance reg= arding 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 nam= e matches an org mode specific pattern/prefix. Short of every concerned use= r taking action here, at least one of the interacting parties (org and snip= pet) would have to compromise: (i) yasnippet by disabling its global minor = mode for all hidden buffers and/or those matching an org specific pattern a= nd/or (ii) org by including a yasnippet specific filter. IMO the best solut= ion is what I described above: yasnippet disabling its global minor mode fo= r *all* hidden buffers.

Best regards
--0000000000002e78ad058502de16--