unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Grant Rettke <grant@wisdomandwonder.com>
To: Joost Kremers <joostkremers@fastmail.fm>
Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>,
	Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Disemvowelment Mode?
Date: Wed, 15 May 2019 14:12:40 -0500	[thread overview]
Message-ID: <CAPE0SPMCV5kqbDfJN3YxKGST=ay=23TJq43zJ2qJPF7vqNFO8g@mail.gmail.com> (raw)
In-Reply-To: <87bm0531nq.fsf@fastmail.fm>

On Tue, May 14, 2019 at 3:02 AM Joost Kremers <joostkremers@fastmail.fm> wrote:
> The thing that I still don't understand, is why you would want to
> convert the document to shorthand at all?
> (AND)
> Why would it
> matter when some of the words are written in full?

I feel like it is easier to read when 100% is shortened instead of 3/4
that I shortened
and 1/4 that I didn't. I would only convert something like that.

> Isn't the purpose in the
> end to have a legible written version of the talk?

From what I have tried so far the shorthand version is easy to read but yea if
I wrote it all perfectly like Paul explained then I would never convert it.


>  If you use a timer, there's no reason AFAICT to *not* create a minor mode for
> it.

Good point, thanks!



  parent reply	other threads:[~2019-05-15 19:12 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
2019-05-14 10:59       ` Eric S Fraga
2019-05-15 19:12       ` Grant Rettke [this message]
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='CAPE0SPMCV5kqbDfJN3YxKGST=ay=23TJq43zJ2qJPF7vqNFO8g@mail.gmail.com' \
    --to=grant@wisdomandwonder.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=joostkremers@fastmail.fm \
    --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).