unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tom <adatgyujto@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Abbrevs for the most frequent elisp symbols
Date: Fri, 19 Dec 2014 19:58:58 +0000 (UTC)	[thread overview]
Message-ID: <loom.20141219T204835-349@post.gmane.org> (raw)

The other day it occurred to me I could use simple abbrevs for
elisp programming, but defining these manually is tiresome, so
I did some automation.

1. I collected all elisp symbols from the manual

2. Generated abbrevs for those which have multiple parts in the
name from the first letters (e.g. goto-char -> gc)

3. There can be collisions (e.g. gc maps to both goto-char and
garbage-collect), so I collected the usage statistics of all
elisp symbols from the emacs lisp sources and in case of a
collision I used that one which occurs more frequently (in the
above case: goto-char).

The result is an automated abbrev table for elisp symbols based
on frequency. So, for example, you can use wcb for
with-current-buffer, bol for beginning-of-line, mb for
match-beginning, etc.

Here's the list of abbrevs, you can try it in a buffer:

http://pastebin.com/D7Lrg3WA


The idea is trivial, so probably somebody has done something like
this already, but I thought I'd share it in case someone else
finds it useful.





             reply	other threads:[~2014-12-19 19:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-19 19:58 Tom [this message]
2014-12-25 14:56 ` Abbrevs for the most frequent elisp symbols 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
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=loom.20141219T204835-349@post.gmane.org \
    --to=adatgyujto@gmail.com \
    --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).