From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: emacs-devel@gnu.org, mathias.dahl@gmail.com
Subject: Re: Splitting image-dired.el into smaller files
Date: Sun, 21 Aug 2022 17:35:56 +0300 [thread overview]
Message-ID: <83tu65br5f.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmnZ-4NQ-Es6-BZs+b-XDGOJcTe3YJXPNcGVHGO8d4--5g@mail.gmail.com> (message from Stefan Kangas on Sun, 21 Aug 2022 07:32:10 -0700)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Sun, 21 Aug 2022 07:32:10 -0700
> Cc: emacs-devel@gnu.org, mathias.dahl@gmail.com
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> image-dired/image-dired-compat.el
> >> image-dired/image-dired-dired.el
> >> image-dired/image-dired-external.el
> >> image-dired/image-dired-gallery.el
> >> image-dired/image-dired-tags.el
> >> image-dired/image-dired-util.el
> >> image-dired/image-dired.el
> >
> > Having "image-dired" both in the directory name and in the file names
> > sounds redundant to me.
>
> Hmm. Any ideas for how we could name the files instead?
Remove the "image-dired-" part?
> > Also, are you sure we need so many separate files? image-dired.el is
> > only 3K lines.
>
> If there are no protests to obsoleting the HTML gallery support, we can
> remove "image-dired-gallery.el". We could also easily make do without
> "image-dired-compat.el".
And maybe leave the -util.el part inside the main file?
next prev parent reply other threads:[~2022-08-21 14:35 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 21:50 Splitting image-dired.el into smaller files Stefan Kangas
2021-12-08 22:24 ` Stefan Monnier
2021-12-08 22:54 ` Stefan Kangas
2021-12-09 1:05 ` Lars Ingebrigtsen
2021-12-09 7:28 ` Eli Zaretskii
2021-12-09 13:58 ` Stefan Kangas
2021-12-09 14:03 ` Eli Zaretskii
2022-01-27 21:26 ` Mathias Dahl
2021-12-09 3:20 ` Renaming files with git not all that bad? Stefan Kangas
2021-12-09 3:56 ` Phil Sainty
2021-12-09 8:43 ` Andreas Schwab
2021-12-09 9:00 ` tomas
2021-12-09 9:24 ` Eli Zaretskii
2021-12-09 13:57 ` Stefan Kangas
2021-12-09 5:40 ` Yuri Khan
2021-12-09 6:02 ` Tassilo Horn
2021-12-09 6:35 ` Yuri Khan
2021-12-09 7:04 ` Tassilo Horn
2021-12-09 7:28 ` Yuri Khan
2021-12-09 22:03 ` Stefan Kangas
2021-12-10 12:28 ` Tassilo Horn
2021-12-11 12:11 ` Yuri Khan
2021-12-09 14:55 ` Stefan Kangas
2021-12-09 15:50 ` tomas
2021-12-09 22:18 ` Stefan Kangas
2021-12-10 8:17 ` tomas
2022-08-21 0:56 ` Splitting image-dired.el into smaller files Stefan Kangas
2022-08-21 5:50 ` Eli Zaretskii
2022-08-21 14:32 ` Stefan Kangas
2022-08-21 14:35 ` Eli Zaretskii [this message]
2022-08-21 15:11 ` Stefan Kangas
2022-08-21 15:16 ` Lars Ingebrigtsen
2022-08-21 15:20 ` Eli Zaretskii
2022-08-21 15:22 ` Lars Ingebrigtsen
2022-08-21 17:02 ` Stefan Monnier
2022-08-23 19:02 ` Stefan Kangas
2022-08-23 19:09 ` Eli Zaretskii
2022-08-23 19:53 ` Stefan Kangas
2022-08-21 16:20 ` Juri Linkov
2022-08-22 13:08 ` Stefan Kangas
2022-08-22 15:18 ` Eli Zaretskii
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=83tu65br5f.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mathias.dahl@gmail.com \
--cc=stefankangas@gmail.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.
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).