unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs does not know state of my abbrevs
Date: Mon, 23 Mar 2015 00:07:06 +0100	[thread overview]
Message-ID: <87fv8wmy1x.fsf@debian.uxu> (raw)
In-Reply-To: mailman.2516.1427034345.31049.help-gnu-emacs@gnu.org

Guido Van Hoecke <guivho@gmail.com> writes:

> Sorry to answer my own question, but for the record:

Yes, that is a good thing to do. First, other people
don't have to answer it, at least if their's solution
coincide precisely with yours. Second, if this problem
gets G00gled and the user ends up at your post, [s]he
can find your answer as well. Third, (well, it goes on
an on) ...

> The file does change whenever an abbrev is used: the
> usage count gets stepped up.
>
> I changed (setq save-abbrevs t) into (set ​q​
> save-abbrevs 'silently) and that fixed thi ​n​ gs
> as desired.

Ha ha, far out!

    (setq save-abbrevs 'silently)

I have my abbrevs hard coded in an init file, then
I just likewise do

    (define-abbrev-table 'global-abbrev-table DEFINITIONS)

on startup. Perhaps there is a speed deficiency but
for a small number of abbrevs it hasn't slowed me down
at least. The advantage is that I can edit the abbrevs
swiftly as I am any file, and never bother with that
whole interactive interface which I don't know where
it ends up.

DEFINITIONS is just a list, e.g. for Usenet newsgroups:

       '(("ctt" "comp.text.tex")
         ("geg" "gnu.emacs.gnus")
         ("geh" "gnu.emacs.help")
         ("ges" "gnu.emacs.sources")
         ("rsb" "rec.sport.boxing")
         ("rbt" "rec.bicycles.tech")
        )

-- 
underground experts united


      parent reply	other threads:[~2015-03-22 23:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-22 12:54 Emacs does not know state of my abbrevs Guido Van Hoecke
2015-03-22 14:25 ` Guido Van Hoecke
     [not found] ` <mailman.2516.1427034345.31049.help-gnu-emacs@gnu.org>
2015-03-22 23:07   ` Emanuel Berg [this message]

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=87fv8wmy1x.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).