From: chad <yandros@gmail.com>
To: emacs-tangents@gnu.org
Cc: Ihor Radchenko <yantar92@posteo.net>, Eli Zaretskii <eliz@gnu.org>
Subject: dog-wagging systems
Date: Sat, 13 Jul 2024 11:56:50 -0500 [thread overview]
Message-ID: <CAO2hHWbi0BOnCRMZMJ1vpUE+aSyFvpO-cB0E=fRtriEqNQSNUw@mail.gmail.com> (raw)
In-Reply-To: <86ikx9jrh4.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 635 bytes --]
Excerpting from another thread:
On Sat, Jul 13, 2024 at 9:30 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > Let's focus on selecting multiple files via completion.
>
> How did "completion" enter the picture?
>
Catching up on this conversation, it strikes me that emacs seems especially
prone to creating Borg-like systems that start focused, gain adherents,
then expand to include all nearby territory, especially UI territory. I'm
thinking of gnus, company/ivy/helm, and org (as well as some MIT-specific
systems from my youth); I'm sure there are more.
Is this just another corollary of Greenspun's Tenth?
~Chad
[-- Attachment #1.2: Type: text/html, Size: 1030 bytes --]
[-- Attachment #2: Type: text/plain, Size: 92 bytes --]
---
via emacs-tangents mailing list (https://lists.gnu.org/mailman/listinfo/emacs-tangents)
parent reply other threads:[~2024-07-13 16:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <86ikx9jrh4.fsf@gnu.org>]
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='CAO2hHWbi0BOnCRMZMJ1vpUE+aSyFvpO-cB0E=fRtriEqNQSNUw@mail.gmail.com' \
--to=yandros@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-tangents@gnu.org \
--cc=yantar92@posteo.net \
/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.
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).