From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emacs pretest 28.0.91 is out Date: Wed, 12 Jan 2022 16:22:53 +0200 Message-ID: <83lezl58zm.fsf@gnu.org> References: <877db65wg4.fsf@gmail.com> <87y23m4awm.fsf@gmail.com> <83o84i6w2j.fsf@gnu.org> <87tuea415m.fsf@gmail.com> <83iluq6rss.fsf@gnu.org> <87pmox4atg.fsf@gmail.com> <83o84h5b69.fsf@gnu.org> <87h7a93us3.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21852"; mail-complaints-to="usenet@ciao.gmane.io" Cc: stefan@marxist.se, emacs-devel@gnu.org To: Robert Pluim Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jan 12 16:26:44 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n7fWO-0005XN-BN for ged-emacs-devel@m.gmane-mx.org; Wed, 12 Jan 2022 16:26:44 +0100 Original-Received: from localhost ([::1]:51052 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n7fWM-0003a9-Vw for ged-emacs-devel@m.gmane-mx.org; Wed, 12 Jan 2022 10:26:43 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:37182) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n7eWj-0004h1-GU for emacs-devel@gnu.org; Wed, 12 Jan 2022 09:23:04 -0500 Original-Received: from [2001:470:142:3::e] (port=46462 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n7eWh-0007OT-By; Wed, 12 Jan 2022 09:23:01 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=ANFWUy3MtGCFNC52cf25ONRC6yfzIW+8qSbb12BxzPw=; b=imPfqN1HAS6I9Qs6Gs2Z XseErjIshgjGjnbf92atbuu0hvEbHYkvhnZ8esJ9H7Cl41Tr15bfSg+Kf5HIKE6tL0thjTenuS9ry T7vdSX4VjbIf8GHXv5V3w99Hmyf560rHJnyAYNiMWfxpH1axnSqEPNp0omKsD1TKZbL1Q/qcb+ba9 zmUi/AzeVP8WvKCQpCBxmj6lcPWEnYd6a5YOW84v/xvWMWTFfLOL31jb49FlT9CmARwBQfGNB34Cs 0HfZYRiwUsF7bz9yZjPlx/pC4cPBImXziaI2ylDTAoc6axc+KdgsLY9PzOIQuOlHbAraf3D15f790 2X5HHy59LNLrsA==; Original-Received: from [87.69.77.57] (port=3620 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n7eWg-000890-EO; Wed, 12 Jan 2022 09:22:59 -0500 In-Reply-To: <87h7a93us3.fsf@gmail.com> (message from Robert Pluim on Wed, 12 Jan 2022 15:15:08 +0100) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:284657 Archived-At: > From: Robert Pluim > Cc: stefan@marxist.se, emacs-devel@gnu.org > Date: Wed, 12 Jan 2022 15:15:08 +0100 > > Debugger entered--Lisp error: (error "Can't find Hunspell dictionary with a .aff affix f...") > signal(error ("Can't find Hunspell dictionary with a .aff affix f...")) > error("Can't find Hunspell dictionary with a .aff affix f...") > ispell-find-hunspell-dictionaries() > ispell-set-spellchecker-params() > ispell-valid-dictionary-list() > byte-code("\301\302!\210\301\303!\210\301\304!\210\10\203>\0\305\10!\203>\0\3061\"\0\307 \210\3100\202&\0\210\202>\0\203>\0\311\312 \235\203>\0\313\314..." [ispell-program-name require ert ispell cl-lib executable-find (error) ispell-check-version t "british" ispell-valid-dictionary-list ert-set-test so-long-spelling record ert-test "Check the spelling in the source code." #f(compiled-function () #) nil :passed (:unstable)] 10) > load("lisp/so-long-tests/spelling-tests" nil t) > > This is because I have no hunspell dictionaries at all (and it would > be cleaner to define the test unconditionally, but skip it when > needed, but thatʼs another discussion). So you want to fix this? I don't mind, but since it's (AFAIU) something specific to your installation, is it important to fix on the release branch?