Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: mh-e-devel@lists.sourceforge.net
Subject: Re: New GNOME icons
Date: Thu, 16 Mar 2006 10:39:42 +0900	[thread overview]
Message-ID: <b4md5gnnp5t.fsf@jpl.org> (raw)
In-Reply-To: <yamaokairqgeatp.fsf@jpl.org>

>>>>> In <yamaokairqgeatp.fsf@jpl.org> Katsumi Yamaoka wrote:

> It suggests there's no way that she uses her favorite images instead
> of the ones Emacs provides.

Didn't you all understand my funny English?  Does Gnus demand
that users use only images that Gnus (or Emacs) provides?  Isn't
it a policy of Gnus that all are fully customizable?  Or did I
miss something?

In the present way of Gnus, there is almost no room for
unprivileged users to customize the directory in which Gnus
finds image files.  For instance, if a user wants Gnus to use
images installed in the ~/images directory even if the ones Gnus
provides are in "gnus/../../etc/images" or "gnus/../etc/images",
how does a user tell Gnus about it?  Although there might be no
such users and I'm not an unprivileged user, I stated a principle.

If users are allowed to modify `image-load-path' like
`load-path', Gnus should respect it (and I presented a way to
achieve it).  Otherwise, Gnus should provide some variable by
which users tell Gnus where to find images.

Regards,


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

  parent reply	other threads:[~2006-03-16  1:39 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-07  0:18 Bill Wohler
2006-03-10 23:15 ` Bill Wohler
2006-03-10 23:56 ` Reiner Steib
2006-03-11  1:23   ` Bill Wohler
2006-03-11  1:29   ` Miles Bader
2006-03-11 12:48     ` Reiner Steib
2006-03-11  2:12   ` *image-load-path-for-library update Bill Wohler
2006-03-11 11:33     ` Reiner Steib
2006-03-11 22:53       ` Bill Wohler
2006-03-12  1:43       ` Bill Wohler
2006-03-12  2:00       ` Bill Wohler
2006-03-13 11:52   ` New GNOME icons Katsumi Yamaoka
2006-03-13 16:56     ` Bill Wohler
2006-03-14  5:32       ` Katsumi Yamaoka
2006-03-14  6:43         ` Bill Wohler
2006-03-14 11:57           ` Katsumi Yamaoka
2006-03-14 17:58             ` Bill Wohler
2006-03-15  1:49               ` Katsumi Yamaoka
2006-03-15  7:34                 ` Katsumi Yamaoka
2006-03-15  7:58                   ` Katsumi Yamaoka
2006-03-16  1:41                   ` gmm-image-load-path-for-library redux (was: New GNOME icons) Bill Wohler
2006-03-16  2:04                     ` gmm-image-load-path-for-library redux Katsumi Yamaoka
2006-03-16  7:24                     ` Katsumi Yamaoka
2006-03-16  8:05                       ` Bill Wohler
2006-03-16 17:41                         ` Bill Wohler
2006-03-16  1:39                 ` Katsumi Yamaoka [this message]
2006-03-14 15:16           ` New GNOME icons Reiner Steib
2006-03-14 19:29             ` Bill Wohler
2006-03-14 21:00               ` Reiner Steib
2006-03-14 21:35                 ` Bill Wohler
2006-03-15  8:58                   ` Reiner Steib
2006-03-15 12:10                   ` Reiner Steib
2006-03-15 15:42                     ` Bill Wohler
2006-03-15 16:40                       ` defvars at compile time (was: New GNOME icons) Reiner Steib
2006-03-15 16:49                         ` defvars at compile time Bill Wohler

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=b4md5gnnp5t.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=mh-e-devel@lists.sourceforge.net \
    /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).