From: Didier Verna <didier@lrde.epita.fr>
Cc: ding@gnus.org
Subject: Re: The etc directory
Date: Wed, 06 Sep 2006 21:47:25 +0200 [thread overview]
Message-ID: <muxejuowzea.fsf@uzeb.lrde.epita.fr> (raw)
In-Reply-To: <87ejupc92q.fsf@catnip.gol.com> (Miles Bader's message of "Thu\, 07 Sep 2006 00\:23\:57 +0900")
Miles Bader <miles@gnu.org> wrote:
> Didier Verna <didier@lrde.epita.fr> writes:
>> I'm afraid of fixing this without knowing if it also affects GNU Emacs (I
>> don't know if GNU Emacs uses the stuff in etc/).
>
> What exactly is your proposed "fix"?
Don't know yet. The quick'n dirty fix I used was to create etc/gnus as
a symlink to /etc/images/gnus, but I should investigate the code and see where
the etc directory is used and how it is computed.
>> Besides, this raises an aside question: gnus seems to only use etc/
>> for images, in which case having etc/images/gnus is logical. However,
>> maybe having etc/gnus directly would also make sense (or perhaps only
>> in the future when something else than glyphs would be added).
>
> Gnus is also distributed as part of Emacs, in which case there's much
> more in etc, and many other images (in etc/images) besides Gnus images.
> The gnus directories are designed to fit into this scheme.
That's all very nice, but I still don't know if there's and etc/gnus
directory in the Emacs distribution, or if gnus only uses etc/images/gnus. But
anyway. There's a very good chance that I"ll find the origin of the problem in
a *-xmacs-*.el of some kind, so this won't affect GNU Emacs users.
--
Didier Verna, didier@lrde.epita.fr, http://www.lrde.epita.fr/~didier
EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (1) 44 08 01 85
94276 Le Kremlin-Bicêtre, France Fax.+33 (1) 53 14 59 22 didier@xemacs.org
next prev parent reply other threads:[~2006-09-06 19:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-06 8:17 Didier Verna
2006-09-06 15:23 ` Miles Bader
2006-09-06 19:47 ` Didier Verna [this message]
2006-09-06 20:42 ` Reiner Steib
2006-09-07 5:51 ` Steve Youngs
2006-09-07 15:30 ` Steven E. Harris
2006-09-07 6:54 ` Didier Verna
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=muxejuowzea.fsf@uzeb.lrde.epita.fr \
--to=didier@lrde.epita.fr \
--cc=ding@gnus.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.
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).