From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from feline.systems ([99.23.220.214]) by ur; Fri Sep 2 23:52:55 EDT 2016 Date: Fri, 2 Sep 2016 23:52:51 -0400 From: BurnZeZ@feline.systems To: 9front@9front.org Subject: Re: [9front] Acme Fixes and Changes Message-ID: In-Reply-To: References: <4b8c438d232e9c8fd55c41da77bd9954@meiling.znet> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: open ORM over ORM framework metadata-oriented framework > >> 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.