From: Robert Pluim <rpluim@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: emacs-devel@gnu.org
Subject: Re: package-archives terminating slash
Date: Thu, 10 Feb 2022 14:25:51 +0100 [thread overview]
Message-ID: <87h7963lb4.fsf@gmail.com> (raw)
In-Reply-To: <874k58m04k.fsf@igel.home> (Andreas Schwab's message of "Wed, 09 Feb 2022 18:16:11 +0100")
>>>>> On Wed, 09 Feb 2022 18:16:11 +0100, Andreas Schwab <schwab@linux-m68k.org> said:
>> (cl-defun package--with-response-buffer-1 (url body &key async file error-function noerror &allow-other-keys)
>> (if (string-match-p "\\`https?:" url)
>> - (let ((url (concat url file)))
>> + (let ((url (file-name-concat url file)))
Andreas> url-expand-file-name perhaps?
Yes, thatʼs a much better function to use.
Robert
--
prev parent reply other threads:[~2022-02-10 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 15:42 package-archives terminating slash Robert Pluim
2022-02-09 17:16 ` Andreas Schwab
2022-02-10 13:25 ` Robert Pluim [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7963lb4.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).