From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "S+*n_Pe*rm*n" Newsgroups: gmane.emacs.devel Subject: url-get-url-at-point & url-get-url-filename-chars | comma-p Date: Sat, 21 Mar 2009 21:01:14 -0400 Message-ID: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1237683691 3114 80.91.229.12 (22 Mar 2009 01:01:31 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 22 Mar 2009 01:01:31 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Mar 22 02:02:48 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LlC5Q-0004J0-2t for ged-emacs-devel@m.gmane.org; Sun, 22 Mar 2009 02:02:48 +0100 Original-Received: from localhost ([127.0.0.1]:41026 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LlC43-0003Cq-D7 for ged-emacs-devel@m.gmane.org; Sat, 21 Mar 2009 21:01:23 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LlC3x-0003Cl-Rj for emacs-devel@gnu.org; Sat, 21 Mar 2009 21:01:17 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LlC3x-0003CR-3b for emacs-devel@gnu.org; Sat, 21 Mar 2009 21:01:17 -0400 Original-Received: from [199.232.76.173] (port=42284 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LlC3w-0003CO-VT for emacs-devel@gnu.org; Sat, 21 Mar 2009 21:01:16 -0400 Original-Received: from yw-out-1718.google.com ([74.125.46.157]:24580) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LlC3w-000475-Gl for emacs-devel@gnu.org; Sat, 21 Mar 2009 21:01:16 -0400 Original-Received: by yw-out-1718.google.com with SMTP id 9so1108727ywk.66 for ; Sat, 21 Mar 2009 18:01:15 -0700 (PDT) Original-Received: by 10.151.98.11 with SMTP id a11mr9661207ybm.98.1237683674946; Sat, 21 Mar 2009 18:01:14 -0700 (PDT) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:109767 Archived-At: The var `url-get-url-filename-chars' is bound globally to "-%.?@a-zA-Z0-9()_/:~=&" and called by `url-get-url-at-point' in ../lisp/url/url-util.el Why isn't comma (",") defined as a valid URL character? RFC3986 denotes the comma (",") as a reserved character (sub-delim) Per section 3.3: | Aside from dot-segments in hierarchical paths, a path segment is | considered opaque by the generic syntax. URI producing applications | often use the reserved characters allowed in a segment to delimit | scheme-specific or dereference-handler-specific subcomponents. For | example, the semicolon (";") and equals ("=") reserved characters are | often used to delimit parameters and parameter values applicable to | that segment. The comma (",") reserved character is often used for | similar purposes. For example, one URI producer might use a segment | such as "name;v=1.1" to indicate a reference to version 1.1 of | "name", whereas another might use a segment such as "name,1.1" to | indicate the same. Parameter types may be defined by scheme-specific | semantics, but in most cases the syntax of a parameter is specific to | the implementation of the URI's dereferencing algorithm. See; 3986 Uniform Resource Identifier (URI): Generic Syntax. T. Berners-Lee, R. Fielding, L. Masinter. January 2005. (Format: TXT=141811 bytes) (Obsoletes RFC2732, RFC2396, RFC1808) (Updates RFC1738) (Also STD0066) (Status: STANDARD) (URL `http://www.ietf.org/rfc/rfc3986.txt?number=3986') - I'm not necessarily advocating inclusion of the comma (",") in the var, and I understand that doing so could pose potential syntax conflicts elsewhere. However, I would like to know whether I should expect the `url-get-url-filename-chars' to change at some point. It would be nice to fully leverage the functions in ./url but I can see where the occlusion of the comma (",") might present future problems as currently defined. (FWIW I seem to be encountering comma's in web URLs with increasing frequency). s_P