From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] delkey(1)
Date: Fri, 23 Oct 2015 11:16:53 +0100 [thread overview]
Message-ID: <1445595413.1878806.418215713.7E1E0168@webmail.messagingengine.com> (raw)
In-Reply-To: <f203b728e74716ea6b219c3bbaf1d1b8@u2.inri>
On Wed, Oct 7, 2015, at 01:47 AM, sl@9front.org wrote:
> > delkey(1) strikes me as stupid.
> > it should be more like
> >
> > % delkey
> > echo 'delkey proto=hj user=dicks' >/mnt/factotum/ctl
> > echo 'delkey proto=p9sk1 user=glenda' > /mnt/factotum/ctl
> > etc
> >
> > instead of the silly yes/no prompting.
>
> I agree with this.
>
> sl
oh, yes please! i don't know why i didn't reply to this before; i hate programs which present question after question.
--
Wir mussen wissen, wir werden wissen.
next prev parent reply other threads:[~2015-10-23 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 0:47 sl
2015-10-23 10:16 ` Ethan Grammatikidis [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-09-29 22:21 delkey(1) Julius Schmidt
2015-09-29 23:35 ` [9front] delkey(1) arisawa
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=1445595413.1878806.418215713.7E1E0168@webmail.messagingengine.com \
--to=eekee57@fastmail.fm \
--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).