From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 68145@debbugs.gnu.org,
"Felician Nemeth" <felician.nemeth@gmail.com>,
"João Távora" <joaotavora@gmail.com>,
"Vyacheslav Akhmechet" <coffeemug@gmail.com>
Subject: bug#68145: [PATCH] * doc/misc/eglot.texi: Fix broken function calls
Date: Mon, 01 Jan 2024 13:17:35 -0500 [thread overview]
Message-ID: <jwvcyuk6hwp.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CADwFkm=tFx0jrYVs36ZffuY9HVxwLUmUZcAO0g0KAAFNF9FYkg@mail.gmail.com> (Stefan Kangas's message of "Sat, 30 Dec 2023 10:16:44 -0800")
>> Strange indeed. No idea what happened, but the 1.16 tarball is also
>> available:
I think the previous run of "update packages" was killed (timeout? OOM?)
and left the Git tree in an incorrect state (more specifically in
a detached state pointing at some old commit where Eglot happened to
still be at 1.15).
I've seen such problem sin the past and have tried to make the scripts
more robust in the face of such weird states, but it's hard to know
how/where to handle it. I fixed it by hand this time, and added
yet-another sanity check elsewhere to help me catch or fix it, so
hopefully in won't re-occur.
Stefan
next prev parent reply other threads:[~2024-01-01 18:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-30 9:05 bug#68145: [PATCH] * doc/misc/eglot.texi: Fix broken function calls Vyacheslav Akhmechet
2023-12-30 13:45 ` Felician Nemeth
2023-12-30 14:46 ` João Távora
2023-12-30 18:16 ` Stefan Kangas
2024-01-01 18:17 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-12-30 20:32 ` Slava Akhmechet
2024-01-11 20:58 ` Stefan Kangas
2024-01-11 21:52 ` João Távora
2024-01-13 10:56 ` Stefan Kangas
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvcyuk6hwp.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=68145@debbugs.gnu.org \
--cc=coffeemug@gmail.com \
--cc=felician.nemeth@gmail.com \
--cc=joaotavora@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=stefankangas@gmail.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.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).