From: BurnZeZ@feline.systems
To: 9front@9front.org
Subject: Re: [9front] Acme Fixes and Changes
Date: Fri, 2 Sep 2016 23:52:51 -0400 [thread overview]
Message-ID: <b06167489bcfb26fef81c8363e7aa803@meiling.znet> (raw)
In-Reply-To: <CA+4OWrxkn7+ui7nhyehTbO_XBYYCyEXk=dR-Ao5Uo_0oykDZFQ@mail.gmail.com>
> >> acme -l loads a default dumpfile without arguments
> > Thus breaking arg handling.
> Still works the old way too.
acme -l $f
^ when $f is empty, you load the default dump rather than exiting.
It also easily leads to misconceptions about how the arguments are
handled.
> > Why should acme be sysname aware?
> If you have multiple systems with different screen sizes or uses. You
> don't go about accidentally overwriting or using a dumpfile that you
> didn't want to use.
This is what namespaces or personal scripts are for. What might make
more sense is the ability to specify the default dump path. Then you
could invoke acme with some script like,
#!/bin/rc
acme -d $home/lib/acme.$sysname.dump $*
I'm not sure if this is a good idea, but it's simple and doesn't
needlessly modify existing behavior.
prev parent reply other threads:[~2016-09-03 3:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 23:19 Matthew Veety
2016-09-02 19:31 ` [9front] " BurnZeZ
2016-09-02 19:34 ` stanley lieber
2016-09-02 19:48 ` cinap_lenrek
2016-09-02 20:45 ` Matthew Veety
2016-09-03 3:52 ` BurnZeZ [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b06167489bcfb26fef81c8363e7aa803@meiling.znet \
--to=burnzez@feline.systems \
--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).