9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] [PATCH] hget: file name detection
Date: Sun, 16 Oct 2022 17:53:08 -0400	[thread overview]
Message-ID: <D792FBD6143A298C1B41745C0A150F3D@eigenstate.org> (raw)
In-Reply-To: <C059A8A5-0774-4EE3-A197-499C09F88B66@musolino.id.au>

Quoth Alex Musolino <alex@musolino.id.au>:
> > take a look at RFC6266 for the filename param; we should probably use that
> > if it is present.
> 
> I think that would just create more problems. Now the target filename is hidden. You’d have to print out the name of the file it wrote for it to be available for further manipulation in a script, say.
> 
> Furthermore, what happens if the destination already exists? You can’t just overwrite it.
> 
> I think this -a may just be a bad idea. If you want to do this kind of thing in the privacy of your own $home it shouldn’t be hard to create a wrapper script that does whatever you want.

consider me convinced.


  reply	other threads:[~2022-10-16 21:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2022-10-16  6:00   ` mkf9
2022-10-16 20:02     ` Alex Musolino
2022-10-16 20:17       ` Stanley Lieber
  -- strict thread matches above, loose matches on Subject: below --
2022-10-11 19:11 mkf9
2022-10-11 20:39 ` Alex Musolino
2022-10-12  2:50   ` mkf9
2022-10-12  4:32     ` unobe
2022-10-12 11:31       ` umbraticus
2022-10-12 22:01       ` mkf9

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=D792FBD6143A298C1B41745C0A150F3D@eigenstate.org \
    --to=ori@eigenstate.org \
    --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).