From: mkf9 <mkf9@riseup.net>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] hget: file name detection
Date: Wed, 12 Oct 2022 06:20:37 +0330 [thread overview]
Message-ID: <4f949543-a147-1699-86cf-55debf8cca98@riseup.net> (raw)
In-Reply-To: <Y0XUd5H9mXtfxkxx@talos>
Can you mention a example?
i don't understand first one and simple URLs with queries in them worked
for me.
Alex Musolino wrote:
>> @@ -34,6 +34,8 @@
>> case -b
>> b=$2
>> shift
>> + case -a
>> + o=`{basename $2}
>> case *
>> usage
>> }
>
> This assumes that the URL immediately follows the '-a' which it won't
> in general. That aside, the idea probably doesn't work so well when
> you have URLs with a query component either.
>
next prev parent reply other threads:[~2022-10-12 2:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 19:11 mkf9
2022-10-11 20:39 ` Alex Musolino
2022-10-12 2:50 ` mkf9 [this message]
2022-10-12 4:32 ` unobe
2022-10-12 11:31 ` umbraticus
2022-10-12 22:01 ` mkf9
2022-10-15 21:07 Alex Musolino
2022-10-15 21:10 ` Alex Musolino
2022-10-15 22:51 ` ori
2022-10-16 19:59 ` Alex Musolino
2022-10-16 21:53 ` ori
2022-10-16 6:00 ` mkf9
2022-10-16 20:02 ` Alex Musolino
2022-10-16 20:17 ` Stanley Lieber
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4f949543-a147-1699-86cf-55debf8cca98@riseup.net \
--to=mkf9@riseup.net \
--cc=9front@9front.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.
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 NNTP newsgroup(s).