unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jason Rumney <jasonr@gnu.org>
Subject: Re: Splitting and moving generic.el.
Date: Wed, 20 Apr 2005 10:05:53 +0100	[thread overview]
Message-ID: <42661B71.6010504@gnu.org> (raw)

For some reason I'm missing all mail to emacs-devel between 4 April and 
8 April, so I had to look into the archives to find this being discussed.

2005-04-05  Lute Kamstra  <address@hidden>

        * generic.el: Commentary section cleanup.
        (generic): Delete.
        (generic-use-find-file-hook, generic-lines-to-scan)
        (generic-find-file-regexp, generic-ignore-files-regexp)
        (default-generic-mode, generic-mode-find-file-hook)
        (generic-mode-ini-file-find-file-hook): Move to generic-x.el.
        * generic-x.el (generic-x): Docstring fix.  Put it in the data group.
        (generic-use-find-file-hook, generic-lines-to-scan)
        (generic-find-file-regexp, generic-ignore-files-regexp)
        (default-generic-mode, generic-mode-find-file-hook)
        (generic-mode-ini-file-find-file-hook): Moved from generic.el.


This change seems to have caused problems. The only reference in my 
.emacs to generic is a

(require 'generic-x)

which used to give me some extra generic based modes.

Now it just gives me an error:

Loading generic...done

An error has occured while loading ~/.emacs:

Symbol's value as variable is void: default-generic-mode



As an aside, I've found Emacs to be less stable since the feature freeze 
was declared than it has been since the early days of 21.0 development. 
I have very little time to spend on Emacs and the little time I have is 
spent tracking down the cause of problems like this leaving no time for 
any real bugfixing on the Windows port. I don't know what the answer is 
to this, but I'm finding it frustrating that after a year of feature 
freeze, people are still shuffling code around between files and 
directories and renaming variables while the manuals still need more 
proofreading and real bugs need fixing.

             reply	other threads:[~2005-04-20  9:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-20  9:05 Jason Rumney [this message]
2005-04-20 10:50 ` Splitting and moving generic.el Lute Kamstra
2005-04-20 11:36   ` Jason Rumney
2005-04-20 12:09     ` Lute Kamstra
2005-04-20 12:31       ` Jason Rumney
2005-04-20 13:27         ` Lute Kamstra
2005-04-20 17:11       ` Eli Zaretskii
2005-04-20 17:08     ` Eli Zaretskii
2005-04-20 20:58       ` Jason Rumney
2005-04-21  3:27         ` Eli Zaretskii
2005-04-20 17:05 ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2005-03-30  9:03 Lute Kamstra
2005-04-05 18:58 ` Lute Kamstra

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=42661B71.6010504@gnu.org \
    --to=jasonr@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 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).