From: Stefan Kangas <stefankangas@gmail.com>
To: Markus Triska <triska@metalevel.at>
Cc: 58196-done@debbugs.gnu.org
Subject: bug#58196: 27.0.50; ediprolog 2.2: Please upload the new version to ELPA
Date: Wed, 10 Jan 2024 02:54:29 -0800 [thread overview]
Message-ID: <CADwFkmmCk71SDEnnPK_dpuKXPVJH5wT2HYkkTtJf8Xw3i5dKwA@mail.gmail.com> (raw)
In-Reply-To: <m2leq0vlvl.fsf@metalevel.at> (Markus Triska's message of "Fri, 30 Sep 2022 18:59:42 +0200")
Markus Triska <triska@metalevel.at> writes:
> ediprolog 2.2 is now available from:
>
> https://www.metalevel.at/ediprolog/ediprolog.el
>
> New in this version:
>
> * handle answers of recent Scryer Prolog versions
> * faithful processing of multiline queries when using Scryer Prolog
> * improved compatibility with older Emacs versions
>
> Project page:
>
> https://www.metalevel.at/ediprolog/
>
> Video demonstration:
>
> https://www.metalevel.at/prolog/videos/ediprolog
>
> For completeness, I also include a copy of the source code below.
>
> Could you please upload the new release to ELPA?
>
> Thank you a lot!
> Markus
It seems like ediprolog 2.2 was uploaded to GNU ELPA on 2022-Oct-26.
Belayed congratulations on the new release.
I'm consequently closing this particular bug report. Please let me know
if that doesn't make sense for some reason and we can reopen.
next prev parent reply other threads:[~2024-01-10 10:54 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 16:59 bug#58196: 27.0.50; ediprolog 2.2: Please upload the new version to ELPA Markus Triska
2022-10-01 12:56 ` Lars Ingebrigtsen
2022-10-01 14:57 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-01 17:01 ` Markus Triska
2022-10-01 18:37 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-02 19:49 ` Markus Triska
2022-10-02 20:07 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-02 20:24 ` Markus Triska
2022-10-02 21:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-03 0:43 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-18 14:34 ` bug#58196: Trivial update to ediprolog Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-26 13:26 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-26 13:32 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-27 21:11 ` Markus Triska
2022-10-28 2:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-28 3:06 ` Stefan Kangas
2022-10-28 3:35 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-28 6:35 ` Eli Zaretskii
2022-10-28 12:37 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-28 3:09 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-28 16:49 ` Markus Triska
2022-10-28 18:07 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-28 20:01 ` Stefan Kangas
2022-10-28 20:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-28 20:51 ` Stefan Kangas
2022-10-28 21:54 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-22 16:20 ` Markus Triska
2022-10-22 16:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-23 7:29 ` Markus Triska
2022-10-25 19:49 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-10 10:54 ` Stefan Kangas [this message]
2024-01-10 22:11 ` bug#58196: 27.0.50; ediprolog 2.2: Please upload the new version to ELPA Markus Triska
2024-01-10 23:18 ` Stefan Kangas
2024-01-14 7:40 ` Markus Triska
2024-01-14 10:17 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmmCk71SDEnnPK_dpuKXPVJH5wT2HYkkTtJf8Xw3i5dKwA@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=58196-done@debbugs.gnu.org \
--cc=triska@metalevel.at \
/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.