From: Matthew Veety <mveety@gmail.com>
To: "9front@9front.org" <9front@9front.org>
Subject: Re: [9front] Acme Fixes and Changes
Date: Fri, 2 Sep 2016 16:45:21 -0400 [thread overview]
Message-ID: <CA+4OWrxkn7+ui7nhyehTbO_XBYYCyEXk=dR-Ao5Uo_0oykDZFQ@mail.gmail.com> (raw)
In-Reply-To: <4b8c438d232e9c8fd55c41da77bd9954@meiling.znet>
On Fri, Sep 2, 2016 at 3:31 PM, <BurnZeZ@feline.systems> wrote:
>> Made brackets work as per the documentation
> What's not working?
The docs suggest that you should be able to double click anywhere
within the brackets to select everything between the brackets, this
wasn't the behaviour.
>> acme -l loads a default dumpfile without arguments
> Thus breaking arg handling.
Still works the old way too.
>> Dump dumps to a default dumpfile
> This is already the behavior.
> You changed the default location to include $sysname
> (now there potentially exist _many_ "default" locations)
Should have been clearer on this.
> 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.
> Why should dumps go into $home/lib/ ?
Having them go in the current directory by default, I think is the
wrong behaviour. They're basically start scripts (like ~/.vimrc, etc.)
--
Veety
next prev parent reply other threads:[~2016-09-02 20:45 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 [this message]
2016-09-03 3:52 ` BurnZeZ
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='CA+4OWrxkn7+ui7nhyehTbO_XBYYCyEXk=dR-Ao5Uo_0oykDZFQ@mail.gmail.com' \
--to=mveety@gmail.com \
--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).