From: Joost Kremers <joostkremers@fastmail.fm>
To: help-gnu-emacs@gnu.org
Cc: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Disemvowelment Mode?
Date: Tue, 14 May 2019 10:01:29 +0200 [thread overview]
Message-ID: <87bm0531nq.fsf@fastmail.fm> (raw)
In-Reply-To: <CAPE0SPOqzJoEpnZw_-aYODnrQA6FyyiVdOZeTXHZCEJ=HjTJ3g@mail.gmail.com>
On Tue, May 14 2019, Grant Rettke wrote:
> When I am typing, most of the time I can keep up and more or
> less apply the simple rules I am trying to follow. The problem
> is when I get distracted (or tired, or the speaker goes to fast
> and I can't keep up) and I just start typing word-for-word. In
> those cases, I don't want to have to go back over the document
> to clean it up. That is why I was thinking about the mode
> "looking back at the last two words or so" to do the right thing
> to them.
The thing that I still don't understand, is why you would want to
convert the document to shorthand at all? Isn't the purpose in the
end to have a legible written version of the talk? Why would it
matter when some of the words are written in full?
> Having talked through this now, there is certainly a case for
> not
> doing this in a mode -_- :).
Well, in any case you'd need to write a function that can
disemvowel a word. You can call this function manually (or wrap it
in another function that runs over a region/the buffer), or you
could run it in an (idle) timer or something similar. If you use a
timer, there's no reason AFAICT to *not* create a minor mode for
it.
--
Joost Kremers
Life has its moments
next prev parent reply other threads:[~2019-05-14 8:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 6:56 Disemvowelment Mode? Grant Rettke
2019-05-13 19:08 ` Stefan Monnier
2019-05-13 19:23 ` Eli Zaretskii
2019-05-14 0:49 ` Grant Rettke
2019-05-14 0:48 ` Grant Rettke
2019-05-14 1:32 ` Stefan Monnier
2019-05-14 3:54 ` Grant Rettke
2019-05-14 4:17 ` Paul W. Rankin
2019-05-15 19:03 ` Grant Rettke
2019-05-14 8:01 ` Joost Kremers [this message]
2019-05-14 10:59 ` Eric S Fraga
2019-05-15 19:12 ` Grant Rettke
2019-05-15 21:41 ` Joost Kremers
2019-05-14 11:57 ` Emanuel Berg
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bm0531nq.fsf@fastmail.fm \
--to=joostkremers@fastmail.fm \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).