From: Alex Kost <alezost@gmail.com>
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: haskell-mode
Date: Mon, 03 Aug 2015 15:36:44 +0300 [thread overview]
Message-ID: <87wpxc4kgz.fsf@gmail.com> (raw)
In-Reply-To: <CAKrPhPNqYN1-eVco+F+V9OwZMcNgYehYZxmeRHzgosMqgPyUiQ@mail.gmail.com> (Federico Beffa's message of "Mon, 3 Aug 2015 09:50:33 +0200")
Federico Beffa (2015-08-03 10:50 +0300) wrote:
> On Sun, Aug 2, 2015 at 1:59 PM, Alex Kost <alezost@gmail.com> wrote:
>> Federico Beffa (2015-08-01 19:18 +0300) wrote:
>>
>>> Hi,
>>>
>>> I would like to propose to change the name of package 'haskell-mode'
>>> to 'emacs-haskell-mode' as we recently started doing for emacs
>>> packages.
>>>
>>> WDYT?
>>
>> I agree on this, but I don't understand the convention of naming emacs
>> packages. What about "geiser", "emms", "magit", "paredit"? I have a
>> feeling they shouldn't be renamed into "emacs-geiser", … but I can't
>> explain why.
>
> The discussion on naming was very quick:
> https://lists.gnu.org/archive/html/guix-devel/2015-06/msg00309.html
>
> From my point of view, if we want to be consistent we should use the
> same prefix for all packages providing Emacs libraries/extensions.
> Choices based on feelings are just going to make things confusing.
I was confused because you proposed to rename only 'haskell-mode'. I
think it is better to rename all emacs packages in once.
--
Alex
next prev parent reply other threads:[~2015-08-03 12:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-01 16:18 haskell-mode Federico Beffa
2015-08-02 11:59 ` haskell-mode Alex Kost
2015-08-03 7:50 ` haskell-mode Federico Beffa
2015-08-03 9:59 ` haskell-mode Andreas Enge
2015-08-05 10:06 ` haskell-mode Federico Beffa
2015-08-03 12:36 ` Alex Kost [this message]
2015-08-05 10:11 ` haskell-mode Federico Beffa
2015-08-18 15:50 ` haskell-mode Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wpxc4kgz.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=beffa@ieee.org \
--cc=guix-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 public inbox
https://git.savannah.gnu.org/cgit/guix.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).