From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Newsgroups: gmane.emacs.help Subject: Re: Is there something like `file-name-concat', but for urls? Date: Wed, 26 Jul 2023 06:34:07 +0200 Message-ID: References: <87edkxnb68.fsf@mbork.pl> <877cqoynaa.fsf@dataswamp.org> <87v8e7yh7b.fsf@dataswamp.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="po3IND2ZzWW8GSDi" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36394"; mail-complaints-to="usenet@ciao.gmane.io" To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Wed Jul 26 06:35:20 2023 Return-path: Envelope-to: geh-help-gnu-emacs@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 1qOWF6-0009Id-Ho for geh-help-gnu-emacs@m.gmane-mx.org; Wed, 26 Jul 2023 06:35:20 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qOWEZ-0001q3-3H; Wed, 26 Jul 2023 00:34:47 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qOWEW-0001pS-3A for help-gnu-emacs@gnu.org; Wed, 26 Jul 2023 00:34:44 -0400 Original-Received: from mail.tuxteam.de ([5.199.139.25]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qOWDz-0000tX-0Y for help-gnu-emacs@gnu.org; Wed, 26 Jul 2023 00:34:43 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tuxteam.de; s=mail; h=From:In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:To:Date:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=wzrUtQkfAXgNVIcioMAAjwVRYLdfoVWmAHUgGhfV6wc=; b=pfbcTRlNSWMKhcQLtPktx3yAyf UdAzKd+E3KMmNb6fyfMkPYP/SFo/71ZXT38uaRSGf9vYkZa+z4TzgUurPzJAIh6pg70sliAHqlWz1 0vu2Djwbab1/P1rE9poM9T/VS57Y77dLP8g/EnjxCbblsFC/QZpZTv9QXn+d89yEiew+2D/EcqzNn SVHEwXNBqeImqQcPRpnurDbzrlEYKxGtiLmK6wPxYYkpJ0PZyDZ/44fH4leQANsoT/guf/KtM/Tqg ivyoxJdkG7KRKna7j5wp00nDcAQeKa9LA2KGdFY5QdUMeCejpdheVqJJTLnf4CAZJKx7ozD66719V Gh6l/zLQ==; Original-Received: from tomas by mail.tuxteam.de with local (Exim 4.94.2) (envelope-from ) id 1qOWDv-00012X-KG for help-gnu-emacs@gnu.org; Wed, 26 Jul 2023 06:34:08 +0200 Content-Disposition: inline In-Reply-To: <87v8e7yh7b.fsf@dataswamp.org> Received-SPF: pass client-ip=5.199.139.25; envelope-from=tomas@tuxteam.de; helo=mail.tuxteam.de X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.help:144466 Archived-At: --po3IND2ZzWW8GSDi Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jul 25, 2023 at 08:33:12PM +0200, Emanuel Berg wrote: > tomas wrote: >=20 > >> BTW thanks for letting me realize I should modernize that, > >> it is so old https isn't even included [...] > > > > Plus URL encoding. Plus deciding in fringe cases whether > > encoding is in order or not [...] >=20 > How the URL can look is defined by a grammar Have you read RFC 3986? > this is > Computer Science theory of Compiler Design. Because, if we get > the standard definition, expressed as a grammar, we can not > only use the correct terminology from there, we can also > verify if the result URL is valid or not. No. This is, alas, Computer Tinkering Practice, where RFCs try as well as they can, to codify existing practice. Some try to even set up a grammar, often in some EBNF dialect -- but practice and existing implementations often emerge long before that grammar was written, shaped by negligence, inexperience, not seldomly by economical or political interests. When people, at last, meet at a table to hammer out an RFC, often they are sent in by companies trying to defend the stakes they have rammed in the ground. Once the RFC is out, if, say, Microsoft or Google is doing something not according to it, you can shout at them until you are blue in the face. It won't help, anyway. Sometimes, standards bodies just give up and declare something as a "living standard", which means "whatever we come up with this week", as happens to HTML5. This is, alas, reality, where our "industry" is dominated by a handful of actors. Enjoy, nevertheless. Cheers --=20 t --po3IND2ZzWW8GSDi Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCZMCiOQAKCRAFyCz1etHa RiY2AJ4ss61zyUxHh+z7nAciiemE18QWiwCeOG74CanJ07ajr9CqMQFuZTex2ww= =XFhC -----END PGP SIGNATURE----- --po3IND2ZzWW8GSDi--