From: "Sascha Retzki" <sretzki@gmx.de>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] edit -- a new acme(4) file
Date: Tue, 14 Nov 2006 19:56:39 +0100 [thread overview]
Message-ID: <ebe2f9c194970455dfcbcd4584ab2621@mail.gmx.net> (raw)
In-Reply-To: <c4a46c570611111639n6788bd9dr95cfe66abbed243f@mail.gmail.com>
> A quick-and-dirty patch to acme that introduces 'edit', a new acme(4)
> file, to which Edit commands can be written.
[...]
>
> Comments welcome.
*Arrr* I love it. Always wanted an edit-file, makes acme even more powerful. patch(1) :-D ?
> I am planning to port this to Acme
> SAC
Excuse me, What's 'Acme SAC'? Did I miss something? Is it a internet-acronym I never heared of?
next prev parent reply other threads:[~2006-11-14 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-12 0:39 Arvindh Rajesh Tamilmani
2006-11-14 18:56 ` Sascha Retzki [this message]
2006-11-14 19:56 ` Arvindh Rajesh Tamilmani
2006-11-15 18:33 ` Sascha Retzki
2006-11-14 20:11 ` Arvindh Rajesh Tamilmani
2006-11-14 22:06 ` Russ Cox
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=ebe2f9c194970455dfcbcd4584ab2621@mail.gmx.net \
--to=sretzki@gmx.de \
--cc=9fans@cse.psu.edu \
/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).