From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: joaotavora@gmail.com (=?utf-8?B?Sm/Do28gVMOhdm9yYQ==?=) Newsgroups: gmane.emacs.devel Subject: Re: use-package.el -> Emacs core Date: Tue, 10 Nov 2015 21:00:53 +0000 Message-ID: References: <564136F7.2020404@yandex.ru> <877flqe1a4.fsf@gmail.com> <87twoucaxz.fsf@gmail.com> <877flqc9jh.fsf@gmail.com> <87twout0iu.fsf@fencepost.gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1447189299 2677 80.91.229.3 (10 Nov 2015 21:01:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 10 Nov 2015 21:01:39 +0000 (UTC) Cc: Juanma Barranquero , Dmitry Gutov , Oleh Krehel , Emacs developers To: John Wiegley Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 10 22:01:24 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZwG2c-0008Cf-Em for ged-emacs-devel@m.gmane.org; Tue, 10 Nov 2015 22:01:22 +0100 Original-Received: from localhost ([::1]:35548 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZwG2c-00034p-My for ged-emacs-devel@m.gmane.org; Tue, 10 Nov 2015 16:01:22 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35544) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZwG2N-00034f-89 for emacs-devel@gnu.org; Tue, 10 Nov 2015 16:01:10 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZwG2F-0008Tf-A2 for emacs-devel@gnu.org; Tue, 10 Nov 2015 16:01:06 -0500 Original-Received: from mail-wm0-x234.google.com ([2a00:1450:400c:c09::234]:34524) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZwG2E-0008TF-Rs for emacs-devel@gnu.org; Tue, 10 Nov 2015 16:00:58 -0500 Original-Received: by wmvv187 with SMTP id v187so27863779wmv.1 for ; Tue, 10 Nov 2015 13:00:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:in-reply-to:references:user-agent:date :message-id:mime-version:content-type:content-transfer-encoding; bh=tsjzWqJJhfdvXz8nNfVwbqhRIqA2x1u/OUiBSLjAwcc=; b=o19AtIKLjAcdCJ9PN+ekSRH0MTZsAZjBSCiQ0e51jc0zeC5b+PxCsnRRwfMsW/FFlj jePqkeLX2B3U8TfcRrV+z98dJesAqGKaJlA/rY1BtNdqCS4aWL7JpM42gN2tLV7sc5AL uMYsWL8sr+OLZc7bkKT6uVe89pLvybbzM4rsr8igVZJTUtSNootPEm300SJbs19AfH9q KIkYhwnURsqXb8CHJm8WplloUcAReddKAR+guQNFcPV/1V5Kiy9PAVNf3fJOrcbg83hZ huYbl+sJLI9L8HQFxbK+SjJ0p17cpFWwJaPJy2WcG4c2IuLybU7srhBPvTTiSF1SCvms 5aLQ== X-Received: by 10.28.4.7 with SMTP id 7mr6686667wme.85.1447189258240; Tue, 10 Nov 2015 13:00:58 -0800 (PST) Original-Received: from king.yourcompany.com (31.57.37.188.rev.vodafone.pt. [188.37.57.31]) by smtp.gmail.com with ESMTPSA id jh4sm5449112wjb.33.2015.11.10.13.00.56 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Nov 2015 13:00:56 -0800 (PST) In-Reply-To: (John Wiegley's message of "Tue, 10 Nov 2015 11:47:43 -0800") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (darwin) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c09::234 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:193972 Archived-At: John Wiegley writes: >> (package-install 'markdown-mode) >> (with-eval-after-load 'markdown-mode >> (modify-syntax-entry ?` "\"" markdown-mode-syntax-table)) > > To match those semantics, you'd use: > > (use-package markdown-mode > :ensure t > :config (modify-syntax-entry ?` "\"" markdown-mode-syntax-table)) OK, so we would agree that in this particular example it doesn't bring a great advantage, if any. Perhaps you could provide another example where you definitely think it does. >> I don't think you understood. I don't mean bugs in `use-package', I mean= bug >> reports in my extensions that are reported in terms of `use-package'. Sh= ould >> I not handle those bugs? > > Ah. Does it help that you can macro-expand use-package forms, so that you= see > what the underlying Emacs Lisp calls? I try hard to make the expanded code > "look like what you'd write", as much as possible. That's what I would do yes. But then I have to have a running emacs with `use-package' myself, right? I've seen some macroexpansions of it somewhere in this thread and it's not particularly pretty (also not particularly correct apparently: see my criticism of the use of fboundp and autoload, for example). But I can't resist pointing out a certain irony in your argument: if use-package is not hiding any ugly implementation details, there's really no use for it :-). For contrast, and quite a scare, see the macroexpansions of `define-minor-mode` or `define-globalized-minor-mode'. yucky. On the other hand, I have to admit that by participanting in this discussion I ended up probably learning more than enough of the use-package minilanguage to handle such a bug report. So I don't know. Count me in the "initially against, but now doesn't care" category and let the masses decide :-) Jo=C3=A3o