unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Richard M. Stallman" <rms@gnu.org>
Cc: emacs-devel@gnu.org, mh-e-devel@lists.sourceforge.net
Subject: Re: Shall we use etc/images more?
Date: Tue, 13 Sep 2005 11:55:52 -0400	[thread overview]
Message-ID: <E1EFD8S-0000nt-CN@fencepost.gnu.org> (raw)
In-Reply-To: <873bo9vree.fsf@olgas.newt.com> (message from Bill Wohler on Mon, 12 Sep 2005 15:43:21 -0700)

    I don't remember why reply2
    went into the mail directory, but we added the -2 suffix to avoid
    potential conflicts with Gnus.

If Gnus and MH-E both want an icon for replies, shouldn't they both
use the same one?

    One way to reorganize these--assuming that other packages haven't used
    them yet--is to put them all into etc/images/mh-e. However, in the
    interest of sharing images, I propose the following structure instead:

	etc/images/mail/alias -- adds the current sender to your alias file
	etc/images/mail/refile -- files the message(s)
	etc/images/mail/repack -- renumbers the messages, removing gaps
	etc/images/mail/reply -- different flavors of replies
	etc/images/mail/reply-all
	etc/images/mail/reply-from
	etc/images/mail/reply-to
	etc/images/mail/rescan -- updates the message listing
	etc/images/mail/show -- display the current message
	etc/images/mail/widen -- removes a view restriction
	etc/images/mh-e/mh-logo
	etc/images/execute -- could be used by the dired `x' command
	etc/images/highlight -- used to add a persistent mark
	etc/images/page-down

This makes sense, except that having a subdirectory mh-e just to
contain one file is pointless.  It would be better to use
etc/images/mh-logo for that.

    Three of the images could be generally useful and could be placed at
    the top-level. It's possible I've overlooked other general images, so
    feel free to comment.

Conceptually, widen and rescan are not limited to mail,
so I think they ought to go at top level.

			  Maybe repack is too MH-specific and should be in
    the MH-E directory?

It's not worth having an mh-e directory just for that.

    In the long term, I think we should modify find-image to use the
    algorithm in mm-image-load-path instead of using just data-directory.

I think we should not do either of these; instead, we should do
what you've suggested here.

    Gnus adds etc/images/gnus to the load-path so that it can refer to the
    images directly like "exit-gnus" instead of "gnus/exit-gnus". I think
    I'd prefer to specify the images explicitly as in "execute" or
    "mail/reply"

I agree.


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

  parent reply	other threads:[~2005-09-13 15:55 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-07  2:37 Shall we use etc/images more? Bill Wohler
2005-09-07  8:30 ` Kim F. Storm
     [not found] ` <E1EDCMR-00043d-Vd@fencepost.gnu.org>
2005-09-08  5:47   ` Bill Wohler
2005-09-12  4:57     ` Richard M. Stallman
2005-09-12  6:07       ` Bill Wohler
2005-09-13 15:54         ` Richard M. Stallman
     [not found]         ` <E1EFD6x-0000cn-Qd@fencepost.gnu.org>
2005-09-14  1:50           ` Bill Wohler
2005-09-15 13:00             ` Richard M. Stallman
2005-09-15 18:36               ` Bill Wohler
2005-09-16  6:16                 ` Richard M. Stallman
2005-09-30 18:00                   ` Bill Wohler
2005-09-14  8:02         ` Chong Yidong
2005-09-14  8:55           ` Kim F. Storm
2005-09-14 23:54             ` Chong Yidong
2005-09-14 14:08               ` Kim F. Storm
2005-09-15 13:00                 ` Richard M. Stallman
2005-09-16  2:28               ` Katsumi Yamaoka
2005-09-12 22:43     ` Bill Wohler
2005-09-13  9:23       ` Kim F. Storm
2005-09-13 19:51         ` Eli Zaretskii
2005-09-14  1:45         ` Bill Wohler
2005-09-14  6:41           ` Mark D. Baushke
2005-09-15  2:41           ` Richard M. Stallman
2005-09-15 18:48             ` Bill Wohler
2005-09-29 21:45         ` Bill Wohler
2005-09-30  0:40           ` Bill Wohler
2005-09-30 14:22             ` Chong Yidong
2005-09-30 20:01             ` Richard M. Stallman
2005-10-15  6:45               ` Bill Wohler
2005-10-15 15:00                 ` Romain Francoise
2005-10-15 17:43                   ` Bill Wohler
2005-10-15 18:52                     ` Romain Francoise
2005-10-16 14:41                 ` Richard M. Stallman
2005-10-16 18:00                   ` Bill Wohler
2005-10-17 17:30                     ` Richard M. Stallman
2005-10-17 22:21               ` lisp/toolbar is gone (was: Shall we use etc/images more?) Bill Wohler
2005-10-18  8:03                 ` Andreas Schwab
2005-09-13 15:55       ` Richard M. Stallman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-30 22:39 The MH-E repository Bill Wohler
2005-05-30 23:27 ` Juanma Barranquero
2005-05-31  0:21 ` Miles Bader
2005-05-31  7:08 ` Jérôme Marant
2005-05-31  7:46   ` Miles Bader
2005-05-31  8:17     ` Jérôme Marant
2005-05-31  8:59       ` Mark D. Baushke
2005-05-31  9:30         ` Jérôme Marant
2005-05-31 15:21       ` Bill Wohler
2005-05-31  9:03   ` Eli Zaretskii
2005-05-31 17:47   ` Richard Stallman
2005-05-31 20:00     ` Jérôme Marant
2005-06-01 17:22       ` Richard Stallman
2005-06-02  5:31       ` packaging (was: The MH-E repository) Janusz S. Bień
2005-06-03  8:01         ` Richard Stallman
2005-05-31  8:56 ` The MH-E repository Kim F. Storm
2005-05-31 10:07   ` Mark D. Baushke
2005-05-31 17:47     ` Richard Stallman
2005-05-31 18:16       ` Mark D. Baushke
2005-05-31 18:39         ` chad brown
2005-06-01 17:24         ` Richard Stallman
2005-05-31 22:00       ` Kim F. Storm
2005-05-31 13:08 ` Stefan Monnier
2005-05-31 17:09   ` Bill Wohler
2005-05-31 18:06     ` Mark D. Baushke
2005-05-31 19:13       ` Stefan Monnier
2005-07-05  4:35       ` Richard M. Stallman
2005-07-05 18:28         ` Bill Wohler
2005-07-11  1:22           ` Mark D. Baushke
2005-05-31 21:39     ` Miles Bader
2005-05-31 17:46 ` Richard Stallman
2005-06-01  9:39 ` Richard Stallman
2005-06-01 16:50 ` Bill Wohler
2005-06-02  6:40   ` Richard Stallman
2005-06-02 18:32     ` Bill Wohler
2005-06-03 22:30       ` Richard Stallman
2005-06-03 23:25         ` Bill Wohler
2005-06-04  9:44           ` [Savannah-help-public] " Sylvain Beucler
2005-06-04 12:30             ` Miles Bader
2005-06-04 16:13               ` Bill Wohler
2005-06-04 16:52                 ` Sylvain Beucler
2005-09-30 22:49                   ` Bill Wohler
2005-10-01 17:04                     ` Sylvain Beucler
2005-10-03 23:14                       ` Bill Wohler
2005-10-04 12:17                         ` Sylvain Beucler
2005-10-04 20:13                           ` Bill Wohler
2005-06-04 17:59             ` Richard Stallman
     [not found] ` <wohler@newt.com>
2005-06-01 13:47   ` Peter S Galbraith
2005-06-01 14:27     ` Bill Wohler
2005-06-02  6:40     ` Richard Stallman
2005-09-16 19:12   ` Shall we use etc/images more? Peter S Galbraith

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1EFD8S-0000nt-CN@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).