From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel,gmane.emacs.orgmode Subject: Re: info URL =?iso-8859-1?Q?=AB?= open at point =?iso-8859-1?Q?=BB?= patch Date: Tue, 26 Jun 2018 17:34:34 +0300 Message-ID: <83muvhr4zp.fsf@gnu.org> References: , <83h8lstfwh.fsf@gnu.org> , <8336xct8v0.fsf@gnu.org> , <83y3f4rpjt.fsf@gnu.org> , <83vaa7simv.fsf@gnu.org>, NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1530023570 16539 195.159.176.226 (26 Jun 2018 14:32:50 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 26 Jun 2018 14:32:50 +0000 (UTC) Cc: emacs-orgmode@gnu.org, brandelune@gmail.com, emacs-devel@gnu.org To: Vincent =?iso-8859-1?Q?Bela=EFche?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 26 16:32:46 2018 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 1fXp1R-0004BB-Ah for ged-emacs-devel@m.gmane.org; Tue, 26 Jun 2018 16:32:45 +0200 Original-Received: from localhost ([::1]:53086 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fXp3T-0000Da-Sf for ged-emacs-devel@m.gmane.org; Tue, 26 Jun 2018 10:34:51 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45355) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fXp3H-0000DB-Kj for emacs-devel@gnu.org; Tue, 26 Jun 2018 10:34:45 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fXp3B-0004rE-Od for emacs-devel@gnu.org; Tue, 26 Jun 2018 10:34:39 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:58643) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fXp3B-0004rA-KH; Tue, 26 Jun 2018 10:34:33 -0400 Original-Received: from [176.228.60.248] (port=2140 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fXp3B-0007bF-1A; Tue, 26 Jun 2018 10:34:33 -0400 In-reply-to: (message from Vincent =?iso-8859-1?Q?Bela=EFche?= on Tue, 26 Jun 2018 05:47:04 +0000) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e 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:226740 gmane.emacs.orgmode:121002 Archived-At: > From: Vincent Belaïche > CC: "emacs-devel@gnu.org" > Date: Tue, 26 Jun 2018 05:47:04 +0000 > > My point is that for a modular design, the same package that provides > the browse-url function, should also provide some match-url-at-point-p > predicate, e.g. There is such a function: browse-url-url-at-point. But in general, I don't agree with your assertion: there's nothing wrong for, e.g., browse-url.el to use a utility function declared somewhere else. Modularity doesn't mean each module must be standalone and self-contained.