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: Sun, 01 Mar 2020 22:07:52 -0500 Message-ID: References: <86wo8flqct.fsf@stephe-leake.org> <3A14F30E-60EF-4C99-AC1A-9A1B2539169B@acm.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> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="70900"; 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 04:08:36 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 1j8bRc-000INW-89 for ged-emacs-devel@m.gmane-mx.org; Mon, 02 Mar 2020 04:08:36 +0100 Original-Received: from localhost ([::1]:54188 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j8bRb-0007Bl-7r for ged-emacs-devel@m.gmane-mx.org; Sun, 01 Mar 2020 22:08:35 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60174) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j8bR0-0006mx-9W for emacs-devel@gnu.org; Sun, 01 Mar 2020 22:07:59 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j8bQy-0004XU-Tq for emacs-devel@gnu.org; Sun, 01 Mar 2020 22:07:57 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:54122) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1j8bQy-0004Vr-Ns for emacs-devel@gnu.org; Sun, 01 Mar 2020 22:07:56 -0500 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 6881081184; Sun, 1 Mar 2020 22:07:55 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id B1C7B80D52; Sun, 1 Mar 2020 22:07:53 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1583118473; bh=VTHNLb5shmFvqqrUp93gXPYJ4ZHNSR736qJeCePgfiQ=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=UAA/VrQPlNb3snxb9PEDsWeI8Sr8qaTkBfR666vDvOBMWxVbMEv/5jPAicxrLsk/e eDsMX7DWbD8+fUGxrZTBibOyisiYE4hgCq3d7QABPwn90vXETPl4l4eFtzw7ujPLwH KNXevG7yQUkGbEC9BmRZGzrG1XEah3NxDrsoPQ+w9291TdCHADtwuGRkUOe5aiBKDG cvbXrT6Prh92BQkjibvUBKhH1a7mACw69ZC32NHXbHf4D/63IFj7595BcbJlTjAZ2E EjFE13Yylhr1PbLW/bKm7bpPy3/PaJ/miBOE9GVPb9DDQ1AMnI7WJWVlW7TMJaTAT3 hfl9r3zOEa2eQ== Original-Received: from pastel (unknown [216.154.50.221]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 51D8F1205FF; Sun, 1 Mar 2020 22:07:53 -0500 (EST) In-Reply-To: <878skjr8yo.fsf@mbork.pl> (Marcin Borkowski's message of "Sun, 01 Mar 2020 23:44:47 +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:245147 Archived-At: > Interesting. I didn't know that. I tried enablng flycheck on one of my > larger Elisp files. It gave me one error in a apparently totally > correct (and working!) 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. Stefan