From: "João Távora" <joaotavora@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 67480@debbugs.gnu.org, Mou Tong <mou.tong@outlook.com>
Subject: bug#67480: 30.0.50; Cannot start eglot
Date: Wed, 29 Nov 2023 00:40:45 +0000 [thread overview]
Message-ID: <CALDnm539joOWb+4U7Dd6cEHJkiz9=OhLZbah8zAr0L+cxEQd2g@mail.gmail.com> (raw)
In-Reply-To: <CALDnm53RkOmvDnAioVFC7OG1ZPLcp5-gWC+_T=YS0QjAOJ8b=Q@mail.gmail.com>
On Tue, Nov 28, 2023 at 5:27 PM João Távora <joaotavora@gmail.com> wrote:
> I don't have the code in front of me, but ok, so a lazy slot.
I've now fixed this and a bunch of other similar problems in
master. But let's wait a few more days if some more related
flak comes in before closing this.
Maybe it also makes sense to merge this with bug#67480?
João
PS: I wrote earlier that the :before on the accessor generic is
standard CLOS technique for lazy slots. It could be, but
slot-unbound of the slot-value protocol is more correct. Just
nitpicking myself here. EIEIO seems to support slot-unbound.
next prev parent reply other threads:[~2023-11-29 0:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 8:12 bug#67480: 30.0.50; Cannot start eglot Mou Tong
2023-11-27 13:09 ` Eli Zaretskii
2023-11-28 6:06 ` Mou Tong
2023-11-28 14:24 ` Eli Zaretskii
2023-11-28 14:42 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-02 18:54 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-28 14:52 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-28 15:10 ` João Távora
2023-11-28 15:48 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-28 17:27 ` João Távora
2023-11-29 0:40 ` João Távora [this message]
2023-12-01 16:04 ` João Távora
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='CALDnm539joOWb+4U7Dd6cEHJkiz9=OhLZbah8zAr0L+cxEQd2g@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=67480@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=mou.tong@outlook.com \
/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.