all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: How many packages do you use?
Date: Fri, 23 Feb 2024 04:11:45 +0100	[thread overview]
Message-ID: <87ttlz27ta.fsf@dataswamp.org> (raw)
In-Reply-To: 878r3crncd.fsf@aarsen.me

Arsen Arsenović wrote:

>>   $ grep -h -o '(require .*)' **/*.el | sort -u | wc -l
>>
>> I use 159!
>
>   ~$ qlist -I app-emacs/ | wc -l
>   63
>
> ... and a few more through USE=emacs.

?

What commands and directory are those?

>> Isn't it amazing that one almost never has any collisions
>> doing it? Actually, I can't think of a single time that
>> happened. But maybe it happened once or twice as I don't
>> remember everything that happens.
>
> Depending on what you mean by collisions, I might or might
> not have had some.

If you bring in a bunch of stuff onto a global namespace, you
get a collision if two things are called the same.

>> Maybe this shows that built-in and/or enforced modularity
>> is over-rated?
>
> I'm not sure I can agree even if that were true - I don't
> see how one implies the other.

One way of doing it is to have everything refered to by a full
path or other composition notation involving the module name,
so some function 'sin' from the package 'math' would be called
by 'math:sin' or using some similar syntax to that end. And if
there are two packages called 'math' one would etc etc.

But any such schemes seems to be unnecessary, at least here.

-- 
underground experts united
https://dataswamp.org/~incal




  reply	other threads:[~2024-02-23  3:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22  4:50 How many packages do you use? Emanuel Berg
2024-02-23  1:12 ` Arsen Arsenović
2024-02-23  3:11   ` Emanuel Berg [this message]
2024-02-25 13:57     ` Arsen Arsenović

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

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

  git send-email \
    --in-reply-to=87ttlz27ta.fsf@dataswamp.org \
    --to=incal@dataswamp.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.