From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] Another acme question
Date: Wed, 18 Feb 2009 17:27:54 +0200 [thread overview]
Message-ID: <bf405074e6b4c935354979d130817189@proxima.alt.za> (raw)
In-Reply-To: <13426df10902180722i6161a19dvb1f7f5a206b94596@mail.gmail.com>
> On Wed, Feb 18, 2009 at 7:16 AM, <lucio@proxima.alt.za> wrote:
>
>> You type /bin/New, instead? It would work 99% of the time.
>
> dang, what was I thinking. I am such a caveman. I'm going back to
> reading entrails.
>
I do agree with you that making up commands to match acme's built-ins
is a sure-fire way of shooting yourself in the foot. But I have
occasionally considered the possibility of a clash through no fault of
my own. Can't think of an example, right now.
++L
next prev parent reply other threads:[~2009-02-18 15:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 15:01 hugo rivera
2009-02-18 15:16 ` lucio
2009-02-18 15:22 ` ron minnich
2009-02-18 15:27 ` lucio [this message]
2009-02-18 15:22 ` hugo rivera
2009-02-18 15:17 ` ron minnich
2009-06-26 10:23 hugo rivera
2009-06-26 11:15 ` roger peppe
2009-06-26 11:46 ` hugo rivera
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=bf405074e6b4c935354979d130817189@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/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).