unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: Ian Dunn <dunni@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] New package: paced
Date: Sat, 09 Dec 2017 11:27:38 +0000	[thread overview]
Message-ID: <87d13ocf9x.fsf@russet.org.uk> (raw)
In-Reply-To: <877etxwag3.fsf@gnu.org> (Ian Dunn's message of "Fri, 08 Dec 2017 09:39:24 -0500")

Ian Dunn <dunni@gnu.org> writes:

>     Phil> Interesting. In your comparison to pabbrev.el, instead of "you’ve got
>     Phil> to retrain pabbrev every time you restart Emacs", I would say, "it
>     Phil> retrains itself automatically", though. And as an advantage over both
>     Phil> paced and predictive, it requires no set up at all to use. You just
>     Phil> turn it on.
>
>     Phil> Phil
>
> I clarified the issues with pabbrev, mainly, the task of having to open
> each file from which you want to train it.  For me, that's about 100
> files with my prose in it.  But I also mentioned its easy setup and that
> retraining is automatic.


Thanks for this! Personally, it doesn't bother me; I don't "train"
it. It just gets more correct over time. And not being persistent means
that I don't really need an editor to remove incorrect expansions.

Still, if it's a problem for you, it's fair that you mention them. I
would deal with the issue by using desktop.el (which will persist your
sessions). pabbrev.el then does it's thing in the background.

Phil



  reply	other threads:[~2017-12-09 11:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-03 20:46 [ELPA] New package: paced Ian Dunn
2017-12-03 21:05 ` Phillip Lord
2017-12-08 14:39   ` Ian Dunn
2017-12-09 11:27     ` Phillip Lord [this message]
2017-12-04 14:46 ` Robert Weiner
2017-12-04 15:17   ` Stefan Monnier
2017-12-04 15:46     ` Robert Weiner

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=87d13ocf9x.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=dunni@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).