unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Emanuel Berg <moasenwood@zoho.eu>
To: emacs-devel@gnu.org
Cc: help-gnu-emacs@gnu.org
Subject: Re: modularity, code for yourself and possibly others
Date: Tue, 02 Apr 2019 00:22:25 +0200	[thread overview]
Message-ID: <86wokd9xi6.fsf@zoho.eu> (raw)
In-Reply-To: CAN-HRFaApTZS6L3OppJoRPUwGaRcpbikKfpLYpQstg6JevYpYA@mail.gmail.com

Tadeus Prastowo wrote:

> Why not firing `whitespace-cleanup' instead?

OK, I didn't know about it. Thank you. But it
doesn't change the general situation.

> Why don't you put that function in another
> file other than edit.el? You are basically
> dealing with a common problem in software
> engineering that can be solved
> by refactoring.

All my stuff are already sorted into files
according to what they do. E.g.,
for Emacs-w3m [1], I have


    bookmarks.el
    dl.el
    history.el
    search.el
    w3m-keys.el
    w3m-my.el
    w3m-tabs.el
    w3m-unisearch.el


so it is all neatly sorted. But hardly none of
it is/can be used independently.

Moving one function from edit.el to some other
file would require the user to `require' that
file instead, and that file would `require' yet
another file(s), and so on. How would that be
any different?

In the extreme case, for someone else to use
a single of my .el files, s/he would have to
use my entire Elisp system!


[OFF TOPIC] Hint: RFC 3676, section 4.3 (Usenet
Signature Convention)
https://www.ietf.org/rfc/rfc3676.txt


[1] http://user.it.uu.se/~embe8573/emacs-init/w3m/

-- 
underground experts united
http://user.it.uu.se/~embe8573




  reply	other threads:[~2019-04-01 22:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-29  0:42 modularity, code for yourself and possibly others Emanuel Berg
2019-03-29 10:43 ` Tadeus Prastowo
2019-04-01 22:22   ` Emanuel Berg [this message]
2019-04-02  9:42     ` Tadeus Prastowo
2019-04-04  3:20       ` Emanuel Berg
2019-04-04  8:10         ` Tadeus Prastowo
2019-04-04 22:38           ` Richard Stallman
2019-04-05  3:16             ` Emanuel Berg
2019-04-05 22:31               ` Richard Stallman
2019-04-05  9:57             ` Tadeus Prastowo
2019-04-05 22:33               ` Richard Stallman
2019-04-05 22:48                 ` Drew Adams

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=86wokd9xi6.fsf@zoho.eu \
    --to=moasenwood@zoho.eu \
    --cc=emacs-devel@gnu.org \
    --cc=help-gnu-emacs@gnu.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.
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).