From: Romain Francoise <romain@orebokech.com>
Subject: Re: Changes committed gnus/contrib (ChangeLog compface.el)
Date: Mon, 25 Oct 2004 08:19:19 +0200 [thread overview]
Message-ID: <873c03e2vs.fsf@orebokech.com> (raw)
In-Reply-To: <b9yu0sjd6a5.fsf@jpl.org> (Katsumi Yamaoka's message of "Mon, 25 Oct 2004 08:51:14 +0900")
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> Is there any reason you don't want to use the version of compface.el
> which still exists in the lisp directory?
Yes, I don't have the necessary tools installed, and I don't want to
install them: I find the Elisp-based solution much more elegant and it
reduces the number of external tools Emacs depends on in my setup.
Besides, my system is fast enough to do this in Elisp.
> You don't happen to include the contrib directory in load-path, do
> you? I don't think that's a good idea. Instead, you can move
> required modules from the contrib directory to the lisp directory
> before performing `configure; make install'.
In fact I do, it makes it easier to track changes in those files: if I
move them elsewhere I'd have to check that my version and the version in
contrib are the same each time I update Gnus. And I don't do `make
install' at all, I just add the lisp directory to my load-path.
I will modify the Makefile to byte-compile files in contrib in my local
version, then.
> The best way will be to rewrite the ELisp-based uncompface program by
> someone who can assign or has been assigned the right.
That sounds like a waste of time. :-( Let's hope the original author
will reply soon.
Thanks for your reply,
--
Romain Francoise <romain@orebokech.com> | I know, you love the song but
it's a miracle -- http://orebokech.com/ | not the singer.
next prev parent reply other threads:[~2004-10-25 6:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1CHV1v-00031P-00@quimby.gnus.org>
2004-10-24 16:13 ` Romain Francoise
2004-10-24 23:51 ` Katsumi Yamaoka
2004-10-25 6:19 ` Romain Francoise [this message]
2004-10-25 7:21 ` Katsumi Yamaoka
2006-04-15 13:27 ` Lars Magne Ingebrigtsen
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=873c03e2vs.fsf@orebokech.com \
--to=romain@orebokech.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).