unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tadeus Prastowo <tadeus.prastowo@unitn.it>
To: Emanuel Berg <moasenwood@zoho.eu>
Cc: help-gnu-emacs@gnu.org, emacs-devel <emacs-devel@gnu.org>
Subject: Re: modularity, code for yourself and possibly others
Date: Thu, 4 Apr 2019 10:10:43 +0200	[thread overview]
Message-ID: <CAN-HRFb7OwWwRA=VF0=GRa7jarp4A0AxQYPsri-u=NC4aYNMZw@mail.gmail.com> (raw)
In-Reply-To: <867ecalam7.fsf@zoho.eu>

On Thu, Apr 4, 2019 at 5:30 AM Emanuel Berg <moasenwood@zoho.eu> wrote:
>
> Tadeus Prastowo wrote:
>
> > Rather than going off tangent now by talking
> > about the extreme case, what about if we
> > confine our discussion _for now_ to your
> > specific case of dealing with your pet
> > function `delete-blank-lines'?
>
> It is not a pet function. I was unaware of the
> existence of the function you mentioned. I have
> replaced the supposed pet with the proper
> function. Your demeaning style isn't
> appreciated BTW.

First, I am sorry if you recognize the term `pet function' as
something pejorative.  AFAIK, the term is not pejorative.  Aside from
that, my intention of using the term is to quickly refer to that
function of yours whose name I didn't recall, but about which I am
sure the referent of the term will not be mistaken.

> > If you agree then let's say we put that pet
> > function to its own file
> > `whitespace-cleaners.el'. As of now, that
> > file will require no other file. So, its user
> > will need to require only that file if that
> > user needs no other function of yours.
> > Problem solved here.
>
> The problem is perhaps solved for another
> person wanting to test my software in an easy
> and straightforward way. For me on the other
> hand, the solution of narrowing down every such
> instance would amount to not 116 Elisp files,
> but to several hundreds! I have shortcuts to
> most of them files [1]. But to navigate
> a system with several hundred files, many of
> them consisting of a single or but a few
> functions, would be a total diaster for me,
> while it would still be uncertain how many
> other people would really use my stuff.
> I.e., a lot of work for me, a crippled system
> for me, to achieve an uncertain gain.
> The primary goal is still to have a good system
> for me, since I wrote it for my purposes.

It's your call.  I just want to address your original question on the
problem that spawned this thread.

> > Now, let's enlarge the case a bit.
> > Suppose now the user also wants to use one
> > other function of yours in file `edit.el'.
> > If you had engineered that function _and_
> > that file properly, then the user would have
> > no need to have your entire Elisp system.
> > Problem solved.
>
> Consistent demeaning style + plain
> insults = *plonk*

Once again, I am sorry if you perceive something demeaning + plain
insults = *plonk* in that paragraph.  But, honestly, I don't see
anything like that in that paragraph.

> PS. Your signature is still incorrect. DS.

Ah, okay, so that's what you mean by giving me the RFC link.  Why
didn't you tell me straight away about what was missing?  Okay, I have
fixed my signature, thanks.

> [1] http://user.it.uu.se/~embe8573/emacs-init/navigate-fs-keys.el
>
> --
> underground experts united
> http://user.it.uu.se/~embe8573

-- 
Best regards,
Tadeus



  reply	other threads:[~2019-04-04  8:10 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 [this message]
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='CAN-HRFb7OwWwRA=VF0=GRa7jarp4A0AxQYPsri-u=NC4aYNMZw@mail.gmail.com' \
    --to=tadeus.prastowo@unitn.it \
    --cc=emacs-devel@gnu.org \
    --cc=help-gnu-emacs@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).