From: Richard Stallman <rms@gnu.org>
To: Emanuel Berg <moasenwood@zoho.eu>
Cc: emacs-devel@gnu.org
Subject: Re: modularity, code for yourself and possibly others
Date: Fri, 05 Apr 2019 18:31:47 -0400 [thread overview]
Message-ID: <E1hCXND-0007Bl-4y@fencepost.gnu.org> (raw)
In-Reply-To: <86bm1ljg4q.fsf@zoho.eu> (message from Emanuel Berg on Fri, 05 Apr 2019 05:16:37 +0200)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> The question/challenge was/is how to avoid not
> just sitting on your own huge personal Elisp
> system, and be all content about that, but how
> to make parts of it accessible to other people
> without having them `require' tons of general
> stuff you yourself have collected in different
> files, some of them huge, for
> practical reasons.
In my experience, the only way to produce good results is to go over
the code foir one functionality at a time, and rewrite it to be
well-integrated with Emacs while modularly separated from the other
functionalities of the contribution.
I wish we had done this with the collection of diverse features
which is Org mode.
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2019-04-05 22:31 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
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 [this message]
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=E1hCXND-0007Bl-4y@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=moasenwood@zoho.eu \
/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).