From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Abbrevs for the most frequent elisp symbols
Date: Mon, 29 Dec 2014 19:41:40 +0100 [thread overview]
Message-ID: <54A1A064.3020602@easy-emacs.de> (raw)
In-Reply-To: <loom.20141229T165506-550@post.gmane.org>
On 29.12.2014 16:58, Tom wrote:
> Andreas Röhler <andreas.roehler <at> easy-emacs.de> writes:
>>
>> The question is: does the occurrence inside the manual or the source
> provide indication WRT probability of
>> personal usage?
>>
>> As being a heavy abbrevs-user, here my collection of emacs-lisp abbrevs
> defined:
>>
>
> Certainly, if you assemble a list manually that is more personal.
> My idea was to assemble an abbrev list automatically, because
> adding an abbrev for everything manually is cumbersome.
>
> It may be more efficient to start from an automatic list and
> make it more personal, than starting from scratch and adding
> everything manually.
>
>
>
>
Sure, finally it's a matter of personal habits.
As said, your project is interesting and once pondered to realize it in a simialar way.
However, abandoned that path.
Beside the reason given: there is the need remember abbrevs - unless it's useless.
When defining it manually, you will give a mnemonic abbrev, which presents itself maybe.
Apropos cumbersome: there are ways to make that task easier.
See ar-mode-abbrev-propose
https://github.com/andreas-roehler/werkstatt/blob/master/ar-abbrev-extensions.el
Cheers,
Andreas
next prev parent reply other threads:[~2014-12-29 18:41 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54A1A064.3020602@easy-emacs.de \
--to=andreas.roehler@easy-emacs.de \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.