From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: :alnum: broken? Date: Sat, 29 Feb 2020 22:12:43 +0100 Message-ID: <87ftet3xo4.fsf@telefonica.net> 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> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="45205"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.60 (gnu/linux) To: emacs-devel@gnu.org Cancel-Lock: sha1:9QndWuBLnn7VlrUsO6itNJ6l5Dw= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Feb 29 22:13:20 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 1j89QG-000BdO-5U for ged-emacs-devel@m.gmane-mx.org; Sat, 29 Feb 2020 22:13:20 +0100 Original-Received: from localhost ([::1]:35962 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j89QF-0007Mk-7j for ged-emacs-devel@m.gmane-mx.org; Sat, 29 Feb 2020 16:13:19 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:54720) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j89Pn-0006vO-Lq for emacs-devel@gnu.org; Sat, 29 Feb 2020 16:12:52 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j89Pm-0005y4-Or for emacs-devel@gnu.org; Sat, 29 Feb 2020 16:12:51 -0500 Original-Received: from ciao.gmane.io ([159.69.161.202]:51482) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1j89Pm-0005wa-J9 for emacs-devel@gnu.org; Sat, 29 Feb 2020 16:12:50 -0500 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1j89Pl-000B7p-5y for emacs-devel@gnu.org; Sat, 29 Feb 2020 22:12:49 +0100 X-Injected-Via-Gmane: http://gmane.org/ X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 159.69.161.202 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:245129 Archived-At: Stefan Monnier writes: >> byte-compiler warnings is a terrible method for communicating with users. > > 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.