From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: :alnum: broken? Date: Mon, 02 Mar 2020 12:03:24 -0500 Message-ID: References: <86wo8flqct.fsf@stephe-leake.org> <837e07gmka.fsf@gnu.org> <1c654ac9-10a2-4e5d-f77c-3b78bb580ffc@cs.ucla.edu> <83v9nqg8la.fsf@gnu.org> <298a093f-6eed-3a9f-99cf-bd17b9cb61f0@cs.ucla.edu> <83blpifp95.fsf@gnu.org> <81bfdae0-9fe1-f173-adb1-b5fe2ba2b808@cs.ucla.edu> <834kvafnwk.fsf@gnu.org> <8DA6D8F4-921B-4FB8-A7A3-CE75B10CE668@acm.org> <83zhd2e6h6.fsf@gnu.org> <87k14547u7.fsf@telefonica.net> <87ftet3xo4.fsf@telefonica.net> <87ftetqbi9.fsf@mbork.pl> <64bcf65a-d05f-b49e-b640-cb64a5b19c77@gmail.com> <878skjr8yo.fsf@mbork.pl> <877e03qlaw.fsf@mbork.pl> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="83878"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: =?windows-1252?Q?Cl=E9ment?= Pit-Claudel , emacs-devel@gnu.org To: Marcin Borkowski Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Mar 02 18:04:24 2020 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 1j8oUR-000Lhj-A0 for ged-emacs-devel@m.gmane-mx.org; Mon, 02 Mar 2020 18:04:23 +0100 Original-Received: from localhost ([::1]:35552 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j8oUQ-0004Gm-B7 for ged-emacs-devel@m.gmane-mx.org; Mon, 02 Mar 2020 12:04:22 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57332) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j8oTa-0003Iu-Ux for emacs-devel@gnu.org; Mon, 02 Mar 2020 12:03:31 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j8oTY-0003uz-5G for emacs-devel@gnu.org; Mon, 02 Mar 2020 12:03:30 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:37222) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1j8oTY-0003um-0x for emacs-devel@gnu.org; Mon, 02 Mar 2020 12:03:28 -0500 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 3003544EF62; Mon, 2 Mar 2020 12:03:27 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 7A3FF44E579; Mon, 2 Mar 2020 12:03:25 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1583168605; bh=oyEinBD3C4FWpt3kNPAIcZ7i5B39WXeg3bNpIY7sp00=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=b6M4W4ZM5/ZYt8/vXGdbauyKBkOs0pV3fO5lEr82tPqes3BWdfju6atFr7/ETLB+s BM0SqS7Xs0VPqROTanrgW89HNASzIBWQcTphf+D+PzKsm9cX77i2NfH5QXhMDX3KYy YQl/ZT021UIl/xICP+kmuq5o8DFes8q3y4vCa2L+B/Pojejth3JqjvzHxJhy7jvu5B 4OVv0j/nGIX7c067sa4FaTp5MQL7DRCJqAvIEA/nzhodXX8PeaJSxIgy8Xm1mvlLw7 81spLlyL45joqErXdMbjbp+W/ctKDlAon/5Fu2vP7FzuKVjq/DLbnKqcAi2+Huy+RB k/n7vl+e93f1w== Original-Received: from pastel (unknown [216.154.50.221]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 38B781206CA; Mon, 2 Mar 2020 12:03:25 -0500 (EST) In-Reply-To: <877e03qlaw.fsf@mbork.pl> (Marcin Borkowski's message of "Mon, 02 Mar 2020 08:15:51 +0100") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 132.204.25.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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:245171 Archived-At: >> Most of the warnings don't claim that the code is likely wrong, but >> their aim is rather to make your code more reliable and future-proof. > That makes me cringe. If I use flycheck, I want my files to be 100% > warning-free. That's indeed what we're aiming for, which is why we provide `with-suppressed-warnings`. > What should I do with the line > (require 'request) > then, when it gives the error (not even warning!): > "Cannot open load file: No such file or directory, request (emacs-lisp)"? That's "unrelated": it's an error, not a warning. In general it indicates either an error in your code or an error in the way the compiler is called, or an error in the compiler. In this case it seems to be a problem linked to flycheck. Have you tried `flymake` instead? Does it suffer from the same problem? Stefan