Gnus development mailing list
 help / color / mirror / Atom feed
From: Han Pilmeyer <han@zk3.dec.com>
Subject: Re: New make.bat, give it a try
Date: Thu, 06 Mar 2003 18:23:30 +0100	[thread overview]
Message-ID: <7kbcjtnx.fsf@zk3.dec.com> (raw)
In-Reply-To: <uof4owjnn.fsf@hschmi22.userfqdn.rz-online.de> (Frank Schmitt's message of "Thu, 06 Mar 2003 17:21:16 +0100")

>>>>> "Frank" == Frank Schmitt <usereplyto@Frank-Schmitt.net> writes:

Frank> Sorry, I don't really understand what you mean. You use an other
Frank> smiley.el and want to know if you've got to recompile everything when
Frank> changing smiley.el?

Frank> If this is it, I don't really know, but I think this shouldn't be
Frank> necessary. In general, all .el files which are newer than the
Frank> corresponding .elc file are compiled, the rest isn't, then all el and
Frank> elc files are copied (if you specified /copy).

It's just a procedural error in my part. I run the script and
everything compiles just fine and is copied to the proper Gnus
directories. Then I find out I can't display messages any longer,
since I'm still set up for the other "old" smiley.el. So I copy my old
smiley.el (with an old date) into the lisp directory and compile
again. Bit it still doesn't work, since there was a new smiley.elc. To
prevent this I added a delete of *.elc to the script.

But perhaps this is too specific to my situations and others don't
like the overhead.

Cheers.
-- 
-- Han Pilmeyer, email: han@zk3.dec.compaq.hp.com                            --
--	    Hewlett-Packard Company - UNIX Support Engineering Group         --
--         Answers are the easy part, questions raise the doubt   - JB       --
-- All opinions are those of the author, not of Hewlett-Packard Company!     --




  reply	other threads:[~2003-03-06 17:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-05 10:49 Frank Schmitt
2003-03-05 17:16 ` Peter Wu
2003-03-05 17:40   ` Frank Schmitt
     [not found]     ` <86heag1wph.fsf@vanilla.zzz>
2003-03-06 15:22       ` Frank Schmitt
2003-03-07  5:27         ` Peter Wu
2003-03-07 17:02           ` Kai Großjohann
2003-03-07 18:28           ` Frank Haun
2003-03-08 14:51             ` Peter Wu
2003-03-08 17:40               ` Frank Haun
2003-03-06 11:00 ` Han Pilmeyer
2003-03-06 11:29   ` Frank Schmitt
2003-03-06 12:00     ` Even newer make.bat (was: New make.bat, give it a try) Frank Schmitt
2003-03-06 23:33       ` Even newer make.bat Frank Haun
2003-03-07  8:41         ` Frank Schmitt
2003-03-07 18:22           ` Frank Haun
2003-03-09 14:14       ` Reiner Steib
2003-03-10  7:04         ` Frank Schmitt
2003-03-06 12:15     ` New make.bat, give it a try Norbert Koch
2003-03-06 12:22     ` Han Pilmeyer
2003-03-06 16:21       ` Frank Schmitt
2003-03-06 17:23         ` Han Pilmeyer [this message]
2003-03-06 18:37           ` Frank Schmitt
2003-03-06 21:56             ` Han Pilmeyer

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=7kbcjtnx.fsf@zk3.dec.com \
    --to=han@zk3.dec.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).