all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Daniele Nicolodi <daniele@grinta.net>, emacs-devel@gnu.org
Subject: Re: Package naming
Date: Sun, 7 Jun 2020 01:20:33 +0300	[thread overview]
Message-ID: <ab7a34e9-9f42-ed02-cfd8-63153f07c147@yandex.ru> (raw)
In-Reply-To: <6110ea25-7e2f-9ac4-2f4d-f07bd4425782@grinta.net>

On 07.06.2020 00:56, Daniele Nicolodi wrote:
> beside the matter-of-fact reply of Stefan, I haven't seen anyone else
> express opinion on this matter. I believe that with easy code
> distribution via ELPA (and MELPA) it would be best to have some
> consistency in package naming, thus an (unofficial, not strictly
> enforced) naming convention would be a good thing.
> 
> Does anyone else feel like commenting on this?

I generally lean toward naming the packages 'foo', not 'foo-mode'. But 
there are exceptions.

E.g. if the mode is called <language>-mode, looks like almost everybody 
in MELPA up to now has chosen to name the package the same, apparently 
in order not to confuse the name of the package with the language? There 
are plenty of exceptions for this in core Emacs, though (python.el, 
pascal.el, prolog.el, etc). So you really can go either way.

All packages with minor modes, on the other hand, can safely go with the 
<foo> name, because it's probably sufficiently unique.

I'd call the org-mode package 'org', by the way.



  reply	other threads:[~2020-06-06 22:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-30 22:31 Package naming Daniele Nicolodi
2020-05-30 22:42 ` Stefan Monnier
2020-05-30 22:58   ` Daniele Nicolodi
2020-06-06 21:56 ` Daniele Nicolodi
2020-06-06 22:20   ` Dmitry Gutov [this message]
2020-06-06 23:11   ` 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

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

  git send-email \
    --in-reply-to=ab7a34e9-9f42-ed02-cfd8-63153f07c147@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=daniele@grinta.net \
    --cc=emacs-devel@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.