From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Marcin Borkowski Newsgroups: gmane.emacs.devel Subject: Re: :alnum: broken? Date: Sat, 29 Feb 2020 23:22:54 +0100 Message-ID: <87ftetqbi9.fsf@mbork.pl> References: <86wo8flqct.fsf@stephe-leake.org> <142e845d-eba3-5975-fa63-4c1b14ed4600@cs.ucla.edu> <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> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="77704"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.1.0; emacs 27.0.50 Cc: emacs-devel@gnu.org To: =?utf-8?Q?=C3=93scar?= Fuentes Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Feb 29 23:23:50 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 1j8AWU-000K1i-A1 for ged-emacs-devel@m.gmane-mx.org; Sat, 29 Feb 2020 23:23:50 +0100 Original-Received: from localhost ([::1]:36418 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j8AWT-00054a-CG for ged-emacs-devel@m.gmane-mx.org; Sat, 29 Feb 2020 17:23:49 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33312) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j8AVu-0004er-HZ for emacs-devel@gnu.org; Sat, 29 Feb 2020 17:23:15 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j8AVq-0005ie-LG for emacs-devel@gnu.org; Sat, 29 Feb 2020 17:23:13 -0500 Original-Received: from mail.mojserwer.eu ([195.110.48.8]:48602) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1j8AVq-0005gS-Ek for emacs-devel@gnu.org; Sat, 29 Feb 2020 17:23:10 -0500 Original-Received: from localhost (localhost [127.0.0.1]) by mail.mojserwer.eu (Postfix) with ESMTP id 187D6E6870; Sat, 29 Feb 2020 23:23:01 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at mail.mojserwer.eu Original-Received: from mail.mojserwer.eu ([127.0.0.1]) by localhost (mail.mojserwer.eu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WI4Theqyb0zL; Sat, 29 Feb 2020 23:22:57 +0100 (CET) Original-Received: from localhost (jeden09-dwa27.echostar.pl [213.156.109.227]) by mail.mojserwer.eu (Postfix) with ESMTPSA id 58B54E683A; Sat, 29 Feb 2020 23:22:57 +0100 (CET) In-reply-to: <87ftet3xo4.fsf@telefonica.net> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.110.48.8 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:245130 Archived-At: On 2020-02-29, at 22:12, =C3=93scar Fuentes wrote: > Stefan Monnier writes: > >>> byte-compiler warnings is a terrible method for communicating with user= s. >> >> I'd love to use better ones. > > Don't assume that the user compiles his .el files, for starts, implement > the warnings on the interpreter too. Show a prompt or prominent notice > about the presence of the warnings (similar to what is shown when the > init files has errors). Show a special buffer with those warnings (and > only those) which are targeted to the user. Ignore files which are > likely authored by package writers (a good hint consists on containing a > `provide' or living on certain directories). Add detailed information > about how to fix the warning, assuming that the user is not proficient > with Elisp. +1. I consider myself fairly proficient in Elisp; I authored quitee a few packages, some of them distributed on Github, some of them for private use for a few people. I admit that even that I know about compiler warnings, I never got into a habit of compiling my files. (I know I should, but consider me as a datapoint suggesting that compiler warnings are not enough.) My 2 cents. --=20 Marcin Borkowski http://mbork.pl