From: revcomninos@gmail.com
To: 9fans <9fans@9fans.net>
Subject: [9fans] Autoexpand in sam
Date: Wed, 22 Sep 2021 16:14:58 -0400 [thread overview]
Message-ID: <16323416980.Df93.845004@composer.9fans.topicbox.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 423 bytes --]
Is there a way to implement autoexpand and autocorrect in sam in any way, i.e. for common spelling mistakes and commonly used phrases?
I don't need anything too sophisticated.
Thanks.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T0e2541a723ce90e5-M9fd6984628a79bf758af4f1b
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 998 bytes --]
next reply other threads:[~2021-09-22 20:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 20:14 revcomninos [this message]
2021-09-22 22:51 ` umbraticus
2021-09-23 0:51 ` revcomninos
2021-09-23 3:08 ` Ethan Gardener
2021-09-23 5:29 ` Skip Tavakkolian
2021-09-23 5:54 ` umbraticus
2021-09-23 9:22 ` revcomninos
2021-09-25 16:07 ` revcomninos
2021-09-25 18:45 ` Silas
2021-09-26 4:40 ` revcomninos
2021-09-26 7:42 ` Steve Simon
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=16323416980.Df93.845004@composer.9fans.topicbox.com \
--to=revcomninos@gmail.com \
--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).