[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Brand new clojure support in Emacs ;-)

From: Lynn Winebarger
Subject: Re: Brand new clojure support in Emacs ;-)
Date: Sun, 3 Sep 2023 12:53:11 -0400

On Fri, Sep 1, 2023 at 1:30 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Yuan Fu <casouri@gmail.com>
> > Date: Fri, 1 Sep 2023 10:10:27 -0700
> > Cc: João Távora <joaotavora@gmail.com>,
> >  Eli Zaretskii <eliz@gnu.org>, Dmitry Gutov <dmitry@gutov.dev>,
> >  Richard Stallman <rms@gnu.org>, emacs-devel@gnu.org
> >
> > >> Of course the naming issue is real,
> > >
> > > Yes, I'm glad to see you acknowledge this as an issue. The naming issue
> > > is all I'm trying to speak to right now.
> >
> > From a nontechnical side, taking over a package name that has been around 
> > for 15 years, is very popular, is depended by thousands of Emacs users, 
> > would leave a bad taste is the mouth for clojure-mode developers and users. 
> > And it certainly wouldn’t help with the reputation of Emacs developers 
> > being hard to approach.
> No one who speaks for the project suggested anything like that.  It's
> a non-issue.
So, does RMS not speak for the project?  Am I misreading his message:
https://lists.gnu.org/archive/html/emacs-devel/2023-08/msg01063.html ?
To be clear, I am not advocating anything here other than recognizing
the GNU emacs project's rights to use <language>-mode as a library
name based on that project's use of that naming pattern for 40 years.
I don't think any external party should feel they have trademark-type
rights over such a functional name.

It would be better if there were some policy statement in the emacs or
elisp manual regarding library and package naming practices, though.
Especially with libraries in core being treated as packages by the
built-in package system.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]