From: "João Távora" <joaotavora@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: "Mattias Engdegård" <mattias.engdegard@gmail.com>,
"Stefan Monnier" <monnier@iro.umontreal.ca>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: cus-test fails from completion-category-overrides eglot adds
Date: Wed, 26 Oct 2022 10:39:46 +0100 [thread overview]
Message-ID: <CALDnm52_Ey6gaL6iaM7zs451p=JP++vOhrui_jt_HWdHDptMVQ@mail.gmail.com> (raw)
In-Reply-To: <87sfjbt4ej.fsf@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
On Wed, Oct 26, 2022 at 8:44 AM Michael Albinus <michael.albinus@gmx.de>
wrote:
> João Távora <joaotavora@gmail.com> writes:
>
> Hi João,
>
> > Is this test in the normal test suite executed by `make check`? I ran
> > that after
> > the merge and the only failure I got was the usual tramp-something
> > that I ignore.
>
> What is the "usual tramp-something"? in your case?
>
Whoops. My bad. It's some `esh` thing (eshell?):
Test esh-var-test/alias/symbol-pair condition:
(ert-test-failed
((should
(eshell-match-output regexp))
:form
(eshell-match-output "Variable `ALIAS' is not settable\n")
:value nil :explanation
(mismatched-output
(command "set ALIAS hello\n")
(output "Variable ‘ALIAS’ is not settable\n")
(regexp "Variable `ALIAS' is not settable\n"))))
Fancy quote stuff, apparently. Maybe already fixed, didn't check with the
very latest.
João Távora
[-- Attachment #2: Type: text/html, Size: 1580 bytes --]
next prev parent reply other threads:[~2022-10-26 9:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 19:47 cus-test fails from completion-category-overrides eglot adds Mattias Engdegård
2022-10-25 21:19 ` João Távora
2022-10-25 22:48 ` Stefan Monnier
2022-10-26 6:22 ` Stefan Kangas
2022-10-26 9:05 ` Mattias Engdegård
2022-10-26 11:45 ` Stefan Monnier
2022-10-26 7:44 ` Michael Albinus
2022-10-26 9:39 ` João Távora [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-26 11:35 Mauro Aranda
2022-10-26 12:18 ` Stefan Monnier
2022-10-26 14:35 ` Mauro Aranda
2022-10-26 12:51 ` Mattias Engdegård
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='CALDnm52_Ey6gaL6iaM7zs451p=JP++vOhrui_jt_HWdHDptMVQ@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=mattias.engdegard@gmail.com \
--cc=michael.albinus@gmx.de \
--cc=monnier@iro.umontreal.ca \
/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).