From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: Abbrevs for the most frequent elisp symbols
Date: Mon, 29 Dec 2014 05:55:00 +0100 [thread overview]
Message-ID: <87h9wfkqcb.fsf@debian.uxu> (raw)
In-Reply-To: mailman.16706.1419519419.1147.help-gnu-emacs@gnu.org
Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
> The question is: does the occurrence inside the
> manual or the source provide indication WRT
> probability of personal usage?
That would have to be done on-the-fly which would be
too slow (?) unless the person doing it could feed it
with a personal Elisp library or some sufficiently
large amount of Elisp in his prefered way to
counterweight the source learning data - it could be a
weighted measure, like if the source says 9 to 1, and
the personal code says the opposite, only in much less
quantity, the personal code would still win because it
is more likely the person who wrote that will write
something similar again.
Also, the program could simply ask at ambiguities
which the prefered one is. Then that would then be
added as a rule.
Or how about, right after expansion, one could iterate
expansions by a keystroke - e.g., like with yanking:
first do C-y (`yank'), then do M-y (`yank-pop`), and
even
(defun yank-pop-back (&optional arg)
(interactive "*p")
(yank-pop (if arg (* arg -1) -1)) )
It also depends how many ambiguities there are. If
they are everywhere, whatever you do it will bite you
hard more often than anyone would like.
(Now I'm only discussing this from your perspective
because I think nothing beats typing.)
--
underground experts united
next prev parent reply other threads:[~2014-12-29 4:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 19:58 Abbrevs for the most frequent elisp symbols Tom
2014-12-25 14:56 ` Andreas Röhler
2014-12-29 15:58 ` Tom
2014-12-29 18:41 ` Andreas Röhler
2014-12-30 10:19 ` Tom
2014-12-30 12:01 ` Artur Malabarba
2014-12-30 21:47 ` Stefan Monnier
2014-12-31 9:50 ` Tom
2014-12-31 21:46 ` Artur Malabarba
2015-01-01 0:16 ` Robert Thorpe
2014-12-30 14:12 ` Óscar Fuentes
[not found] ` <mailman.16706.1419519419.1147.help-gnu-emacs@gnu.org>
2014-12-29 4:55 ` Emanuel Berg [this message]
2014-12-29 11:18 ` Marcin Borkowski
2014-12-29 15:28 ` Drew Adams
[not found] <mailman.16504.1419019164.1147.help-gnu-emacs@gnu.org>
2014-12-29 4:21 ` Emanuel Berg
2014-12-29 11:24 ` Marcin Borkowski
[not found] ` <(message>
[not found] ` <from>
[not found] ` <Marcin>
[not found] ` <Borkowski>
[not found] ` <on>
[not found] ` <Mon>
[not found] ` <29>
[not found] ` <Dec>
[not found] ` <2014>
[not found] ` <12:24:20>
2014-12-29 13:09 ` Robert Thorpe
2014-12-29 15:28 ` Drew Adams
2014-12-29 16:28 ` Robert Thorpe
2014-12-29 13:26 ` Stefan Monnier
2014-12-29 13:40 ` Marcin Borkowski
2014-12-29 14:57 ` Stefan Monnier
2014-12-29 15:49 ` Tom
[not found] ` <mailman.16844.1419852282.1147.help-gnu-emacs@gnu.org>
2015-01-03 2:25 ` Emanuel Berg
2015-01-04 0:19 ` Artur Malabarba
[not found] ` <mailman.17204.1420330787.1147.help-gnu-emacs@gnu.org>
2015-01-05 21:16 ` Emanuel Berg
2015-01-08 20:53 ` Artur Malabarba
2015-01-03 2:31 ` 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=87h9wfkqcb.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--cc=help-gnu-emacs@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.
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).