From mboxrd@z Thu Jan 1 00:00:00 1970 References: <1436968754300761450@ml.lv> From: "steve@quintile.net" Content-Type: text/plain; charset=utf-8 In-Reply-To: <1436968754300761450@ml.lv> Message-Id: <3563F483-49E3-450A-8FD5-5C98AABEC7EC@quintile.net> Date: Wed, 15 Jul 2015 15:24:33 +0100 To: Antons Suspans , Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Subject: Re: [9fans] Sam/Acme commands and idioms in ASCII/Markdown Topicbox-Message-UUID: 6047dd84-ead9-11e9-9d60-3106f5b1d025 it would be more helpful if you submitted fixes to the appropriate author if= you find mistakes. I wrote the original document based on sam(1), Sam-tut.ms, and the musings o= f the sam-fans list. it collates info which was hard won at the time. sam's l= anguage is so expressive few people understand, much less remember how to us= e it effectively. -Steve > On 15 Jul 2015, at 14:59, Antons Suspans wrote: >=20 > Tr, 07/15/2015 11:27 AM Anssi Porttikivi rakst=C4=AB= ja: >> I converted >>=20 >> A Sam Commands Reference Card by Steve Simon >> http://sam.cat-v.org/cheatsheet/ >>=20 >> to Markdown ASCII format for myself to use in Acme-sac. Could be just raw= >> ASCII of course. >>=20 >> sam-editor-commands-and-idioms.md >> http://pastebin.com/wX1f0ExG >=20 > Unless that cheatsheet is concerned with some custom variant of Sam/Acme, i= t > could benefit from a bit of proofreading. I'd rather stick with sam(1). >=20 > --=20 > Antons