From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: John Mastro Newsgroups: gmane.emacs.devel Subject: Re: with-url Date: Sat, 21 Jan 2017 14:25:34 -0800 Message-ID: References: <87mvffva75.fsf@gnus.org> <9bd035f3-c7cd-0c8d-81b8-226fb24f608e@yandex.ru> <87bmv0beoa.fsf@gnus.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: blaine.gmane.org 1485037578 31040 195.159.176.226 (21 Jan 2017 22:26:18 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 21 Jan 2017 22:26:18 +0000 (UTC) Cc: Lars Ingebrigtsen , Dmitry Gutov To: emacs-devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 21 23:26:15 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cV46i-0006Ki-EF for ged-emacs-devel@m.gmane.org; Sat, 21 Jan 2017 23:26:00 +0100 Original-Received: from localhost ([::1]:33521 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cV46l-0000PP-Vx for ged-emacs-devel@m.gmane.org; Sat, 21 Jan 2017 17:26:04 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44071) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cV46f-0000PI-Uh for emacs-devel@gnu.org; Sat, 21 Jan 2017 17:25:58 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cV46f-0001hz-8F for emacs-devel@gnu.org; Sat, 21 Jan 2017 17:25:57 -0500 Original-Received: from mail-qk0-x22d.google.com ([2607:f8b0:400d:c09::22d]:35756) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cV46f-0001h0-46 for emacs-devel@gnu.org; Sat, 21 Jan 2017 17:25:57 -0500 Original-Received: by mail-qk0-x22d.google.com with SMTP id u25so44861267qki.2 for ; Sat, 21 Jan 2017 14:25:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=yh7IybF9NGH7i+yhg1VchUVUKisF/5McQTG6NU2SH30=; b=ig/S/rwAvGk0O0xUJtfjkSUhzIi6pi68/bmeYFQ4/bHRlQ2xqEFl1TAHpXkKieirRI 8uv8CLdIX0IziAM3UYLS+d55euDY/45MW9hU7BeMm4sAtW6gCLeP7QQituhAOJUPgvll 3IXHIgSfcr95eGfJCgI8HlzSWVcS4xyPVQGorecIEBA3E1S61NoHM+czokJ+Ds/J6NaT d229TFxuXgdr4WdvYALzYRrUEEOmSBS2CdBodjmlsmUAbJKNQ6Msq3UW8DkKp3yOjqns tHr9Sapp6wq1w9xHkGqbZl8WWpY3CwileR0mfNgGOpKHvWGba54VjFopfhtIEjkhducm PNmQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=yh7IybF9NGH7i+yhg1VchUVUKisF/5McQTG6NU2SH30=; b=K+4yNen7owqyfOP8ITz++Z58T6lpWLdxIQsWqqcCLq3XHarqiTf6wDfXHxj8sltryC wf4vizPlE5Sf+xwWuY+y14utxKOfxU85Gh1T9SfahYm+Q3PHtreUiTmoVfHK9Bdo86Pu TVaBujn9kXrxmWjErgt7iLzCXz1HngsS5+FWcePmAfdCzHBexe4yypFhlLPWo3L94G0m yOLPNv3YKy7dWDEDpWI5L0jEmMFkHkSBbHsW7xsTgF++yokC++l5dfWuWRkc9QWB9MKW JBL8oRsIDXItCXqrewYanCoJNDpbueqiXdkj47Qa/H+Xm+90m4StsBxgQpyF9f7+8ewc RRxw== X-Gm-Message-State: AIkVDXJHj6YZUUJ9vWCYI8Mu28zL63ASmJFFEPiHn/Xa07KhlMoScvZ6Td+FKJKJRwtMazthbyvW1DtnoiSq/A== X-Received: by 10.55.103.85 with SMTP id b82mr17726030qkc.24.1485037555143; Sat, 21 Jan 2017 14:25:55 -0800 (PST) Original-Received: by 10.237.56.138 with HTTP; Sat, 21 Jan 2017 14:25:34 -0800 (PST) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:400d:c09::22d X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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" Xref: news.gmane.org gmane.emacs.devel:211507 Archived-At: >>> Something else I take an issue with, is with `with-url' being a >>> macro. :) That violates The First Rule of Macro Club. >> >> Yes, the first rule is "use a macro when it makes sense". > > Not really. And macros make sense the most when we add a control flow > construct, or some sort of definition syntax for a new facility. > Neither of which is really the case here. I apologize if this has already been discussed, but how about implementing this as a new function that improves on the current situation but offers a traditional interface, plus a macro as an optional convenience layer atop it? John