From: "Phillip Lord" <phillip.lord@russet.org.uk>
To: "Ian Dunn" <dunni@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] New package: paced
Date: Sun, 3 Dec 2017 21:05:49 -0000 [thread overview]
Message-ID: <58ce609b224da827b581fe96334d9a0c.squirrel@cloud103.planethippo.com> (raw)
In-Reply-To: <877eu3bkv7.fsf@gnu.org>
Interesting. In your comparison to pabbrev.el, instead of "you’ve got to
retrain pabbrev every time you restart Emacs", I would say, "it retrains
itself automatically", though. And as an advantage over both paced and
predictive, it requires no set up at all to use. You just turn it on.
Phil
On Sun, December 3, 2017 8:46 pm, Ian Dunn wrote:
>
> I'd like to submit paced[1] to ELPA.
>
>
> Paced (Predictive Abbreviation Completion and Expansion using
> Dictionaries)
> scans a group of files (determined by "population commands") to construct
> a usage table (dictionary). Words (or symbols) are sorted by their usage,
> and may be later presented to the user for completion. A dictionary can
> then be saved to a file, to be loaded later.
>
> Population commands determine how a dictionary should be filled with
> words or symbols. A dictionary may have multiple population commands, and
> population may be performed asynchronously. Once population is finished,
> the contents are sorted, with more commonly used words at the front.
> Dictionaries may be edited
> through EIEIO's customize-object interface.
>
> Completion is done through `completion-at-point'. The dictionary to use
> for completion can be customized.
>
> The code is on Bazaar on Savannah:
>
>
> bzr branch https://bzr.savannah.gnu.org/r/paced-el/ paced
>
> [1] http://nongnu.org/paced-el
>
>
> --
> Ian Dunn
>
>
>
next prev parent reply other threads:[~2017-12-03 21:05 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 [this message]
2017-12-08 14:39 ` Ian Dunn
2017-12-09 11:27 ` Phillip Lord
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=58ce609b224da827b581fe96334d9a0c.squirrel@cloud103.planethippo.com \
--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).