Gnus development mailing list
 help / color / mirror / Atom feed
From: Steven L Baur <steve@miranova.com>
Subject: There is no vm.el
Date: 12 Nov 1996 11:15:26 -0800	[thread overview]
Message-ID: <m2u3qvnn01.fsf@deanna.miranova.com> (raw)

I don't see a vm.el in either XEmacs 19.14 or 19.15 so forcing all
.els is wrong.  The following allows Gnus to bytecompile.

===================================================================
RCS file: RCS/dgnushack.el,v
retrieving revision 1.10
diff -u -r1.10 dgnushack.el
--- dgnushack.el	1996/11/12 18:56:00	1.10
+++ dgnushack.el	1996/11/12 19:11:39
@@ -47,6 +47,8 @@
     (save-match-data
       (cond ((string-match "\\.el\\'" filename)
              nil)
+	    ((string-match "\\`vm\\'" filename)
+	     nil)
             ((string-match "\\.elc\\'" filename)
              (setq filename (replace-match ".el" t t filename)))
             (t

-- 
steve@miranova.com baur
Unsolicited commercial e-mail will be billed at $250/message.
What are the last two letters of "doesn't" and "can't"?
Coincidence?  I think not.


                 reply	other threads:[~1996-11-12 19:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=m2u3qvnn01.fsf@deanna.miranova.com \
    --to=steve@miranova.com \
    /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 NNTP newsgroup(s).