unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Benjamin Rutt" <rutt.4@osu.edu>
To: rms@gnu.org
Cc: Tassilo Horn <tassilo@member.fsf.org>, emacs-devel@gnu.org
Subject: Re: snippet.el
Date: Sun, 28 Oct 2007 10:40:49 -0400	[thread overview]
Message-ID: <68f3f1f70710280740g74c791bft4fcf5c9e3b65de92@mail.gmail.com> (raw)
In-Reply-To: <E1IlmAt-0000DU-7J@fencepost.gnu.org>

I am the author of msf-abbrev.el and am following this thread and can
give some comments.  If people would like to see what it does the best
way is to watch the demo linked off of
http://www.bloomington.in.us/~brutt/msf-abbrev.html

The primary objections I would see people on this list having to
including this package in Emacs would be:

1) a portion of the user interface code deals with setting up and
handling form-like fields within Emacs buffer.  I originally intended
to factor the general-purpose form stuff out into a separate
library,called fld.el, but finally decided to include this code
in-line within msf-abbrev.el for ease of installation.  So, the
package currently pollutes the fld- namespace.  This can be remedied
with some simple effort, such as renaming functions with the fld-
prefix to msf-abbrev-fld- prefix.

2) I feel that it currently suffers from an unresolved
bootstrapping/loading issue.  When it loads up, for each directory in
`msf-abbrev-root', if the directory names a mode, say 'foo-mode', then
if foo-mode exists in Emacs, all the files within 'foo-mode' directory
will have abbreviations created with the same name as the file.  The
problem is that foo-mode must be loaded in Emacs prior to msf-abbrev
loading, so that this detection logic will work.  If anyone has ideas
here, let me know.

3) When a matching directory is detected for say foo-mode, msf-abbrev
will first look for foo-mode-abbrev-table and install the
abbreviations there, if the variable exists (shouldn't all proper
major modes define this?).  If not, it will add a series of
define-abbrev calls to foo-mode-hook.  This scheme generally works
okay, although there are some modes which seem to do funny things like
clearing out their abbrev tables on load which prevents the scheme
from working.

On 10/27/07, Richard Stallman <rms@gnu.org> wrote:
> These packages are probably not so complex that they are a big maintenance
> burden.  Therefore, I think the main question is, which package is best?
>
>
> _______________________________________________
> Emacs-devel mailing list
> Emacs-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-devel
>


-- 
Benjamin Rutt

  reply	other threads:[~2007-10-28 14:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26  3:49 snippet.el Richard Stallman
2007-10-26  8:30 ` snippet.el joakim
2007-10-26 18:38   ` snippet.el Stefan Monnier
2007-10-26 21:10     ` snippet.el Tassilo Horn
2007-10-27 13:58       ` snippet.el Richard Stallman
2007-10-28 14:40         ` Benjamin Rutt [this message]
2007-10-29  9:21           ` snippet.el Richard Stallman
2007-10-27 13:57     ` snippet.el Richard Stallman
2007-10-27  2:28   ` snippet.el Richard Stallman

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=68f3f1f70710280740g74c791bft4fcf5c9e3b65de92@mail.gmail.com \
    --to=rutt.4@osu.edu \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=tassilo@member.fsf.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).