emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Re: Help Debugging Change In Behavior (Last 30 Days)


From: Pedro Andres Aranda Gutierrez
Subject: Re: Re: Help Debugging Change In Behavior (Last 30 Days)
Date: Wed, 28 Jun 2023 09:18:07 +0200

>Message: 22
>Date: Tue, 27 Jun 2023 08:37:04 -0700
>From: "T.V Raman" <raman@google.com>
>To: emacs-devel@gnu.org
>Subject: Re: Help Debugging Change In Behavior (Last 30 Days)
>Message-ID: <p91zg4kor1b.fsf@google.com">p91zg4kor1b.fsf@google.com>
>Content-Type: text/plain; charset=gb18030

"T.V Raman" <raman@google.com> writes:


> Answering my own question:

>There may be a subtle bug that has crept in in setf --

> In my code, I changed the
>(setf (struct-slot-access-form val)
>by introducing a local var slot, and then using it

>(setq slot val)
>(setf (struct-slot-access-form) slot)

>and that fixed the issue

Interestingly enough, this kind of behaviour also affects yasnippet.el and if you grep for setf there, you will find 0 (zero) occurrences there. So some other function in elisp is using fset and that it making yasnippets explode...

BR,/PA
--
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


reply via email to

[Prev in Thread] Current Thread [Next in Thread]