From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: Andrea Corallo <acorallo@gnu.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: yasnippets block last emacs
Date: Wed, 28 Jun 2023 07:22:36 +0200 [thread overview]
Message-ID: <CAO48Bk968Cewcf4MnHSKsvRf6_CJoL9oYyk6sek9LZ+Y_oDdVw@mail.gmail.com> (raw)
In-Reply-To: <CAO48Bk_Eeu2SGJUC96T_Vh8n8yco5+RzLt8wEei53JLUs4rt5g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2839 bytes --]
I've submitted a bug report. It's in the generation of .elc files,
apparently.
Looking for more side effects on stock emacs packages...
/PA
On Tue, 27 Jun 2023 at 07:09, Pedro Andres Aranda Gutierrez <
paaguti@gmail.com> wrote:
> Hi,
>
> Interestingly enough, if I try to grep through my .emacs.d to find find
> internal--with-suppressed-warnings, I get no coincidence:
>
> ~ ➤ find .emacs.d -name \*.el -exec grep -H
> internal--with-suppressed-warnings {} \;
> ~ ➤
>
> but when I grep through the emacs source:
>
> paag@multi-edit:~/emacs$ find emacs -name \*.el -exec grep -H
> internal--with-suppressed-warnings {} \;
> emacs/lisp/emacs-lisp/bytecomp.el: ;; Later
> `internal--with-suppressed-warnings' binds it again, this
> emacs/lisp/emacs-lisp/bytecomp.el:
> `(internal--with-suppressed-warnings
> emacs/lisp/emacs-lisp/bytecomp.el:(put 'internal--with-suppressed-warnings
> 'byte-hunk-handler
> emacs/lisp/emacs-lisp/bytecomp.el:(byte-defop-compiler-1
> internal--with-suppressed-warnings
>
> It might not be native compile, but...
> Scratching my head...
> /PA
>
> On Mon, 26 Jun 2023 at 19:59, Andrea Corallo <acorallo@gnu.org> wrote:
>
>> Pedro Andres Aranda Gutierrez <paaguti@gmail.com> writes:
>>
>> > Hi
>> >
>> > I'm getting the following message:
>> >
>> > yas--template-menu-binding-pair-get-create: Symbol's function
>> definition is void: \(setf\
>> > internal--with-suppressed-warnings\)
>> >
>> > Just compiled emacs:
>> >
>> > In GNU Emacs 30.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version
>> > 3.24.33, cairo version 1.16.0) of 2023-06-26 built on 5fdd05eae699
>> > Repository revision: a6de0d22e4209e2c75dbf1e8c005dfc9d8c64cce
>> > Repository branch: master
>> >
>> > Configured features:
>> > CAIRO DBUS FREETYPE GIF GLIB GMP GNUTLS GSETTINGS HARFBUZZ JPEG JSON
>> > LIBSELINUX LIBXML2 MODULES NATIVE_COMP NOTIFY INOTIFY PDUMPER PNG
>> > SECCOMP SOUND THREADS TIFF TOOLKIT_SCROLL_BARS X11 XDBE XIM XINPUT2 XPM
>> > GTK3 ZLIB
>> >
>> > Doesn't happen when I don't have NATIVE_COMP activated.
>>
>> That's most likely a bug in the yasnippets missing the necessesary
>> require. I suggest you to report it to the yasnippets developer(?s).
>>
>> Best Regards
>>
>> Andrea
>>
>
>
> --
> Fragen sind nicht da, um beantwortet zu werden,
> Fragen sind da um gestellt zu werden
> Georg Kreisler
>
> Headaches with a Juju log:
> unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
> a leader-deposed hook here, but we can't yet
>
>
--
Fragen sind nicht da, um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet
[-- Attachment #2: Type: text/html, Size: 4194 bytes --]
next prev parent reply other threads:[~2023-06-28 5:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 16:12 yasnippets block last emacs Pedro Andres Aranda Gutierrez
2023-06-26 17:59 ` Andrea Corallo
2023-06-27 5:09 ` Pedro Andres Aranda Gutierrez
2023-06-28 5:22 ` Pedro Andres Aranda Gutierrez [this message]
2023-06-28 18:36 ` T.V Raman
2023-06-29 5:15 ` Pedro Andres Aranda Gutierrez
-- strict thread matches above, loose matches on Subject: below --
2023-06-27 2:48 Vitaly Ankh
2023-06-28 12:08 Ramón Lorenzo Panadés-Barrueta
2023-06-28 14:27 ` bug#64292: " Corwin Brust
2023-06-28 20:26 ` Ramón Lorenzo Panadés-Barrueta
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAO48Bk968Cewcf4MnHSKsvRf6_CJoL9oYyk6sek9LZ+Y_oDdVw@mail.gmail.com \
--to=paaguti@gmail.com \
--cc=acorallo@gnu.org \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.