haskell-mode

haskell-mode

[Federico Beffa]

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?
Fede

Re: haskell-mode

[Alex Kost]

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.

-- 
Alex

Re: haskell-mode

[Federico Beffa]

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.

Fede

Re: haskell-mode

[Andreas Enge]

Hello,

On Mon, Aug 03, 2015 at 09:50:33AM +0200, Federico Beffa wrote:
> 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.

could you maybe suggest a patch adding a section to the chapter on
naming conventions in the manual?

Thanks in advance,

Andreas

Re: haskell-mode

[Federico Beffa]

On Mon, Aug 3, 2015 at 11:59 AM, Andreas Enge <andreas@enge.fr> wrote:
> Hello,
>
> On Mon, Aug 03, 2015 at 09:50:33AM +0200, Federico Beffa wrote:
>> 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.
>
> could you maybe suggest a patch adding a section to the chapter on
> naming conventions in the manual?

Right now I don't have time. I may do it in a few weeks.

Sorry,
Fede

Re: haskell-mode

[Alex Kost]

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

Re: haskell-mode

[Federico Beffa]

On Mon, Aug 3, 2015 at 2:36 PM, Alex Kost <alezost@gmail.com> wrote:
> 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.

Right, I only intended to change 'haskell-mode' because I'm probably
the only user of it. But then you mentioned the other emacs packages
and I expressed my opinion on the matter. Changing geiser, paredit,
and other emacs packages is going to be disruptive to the work flow of
many people. That's the reason why I'm not interested in doing this
change myself.

But, I agree that it would make sense to change all of them together.
So, I will not change anything, at least for now.

Regards,
Fede

Re: haskell-mode

[Ludovic Courtès]

Federico Beffa <beffa@ieee.org> skribis:

> On Mon, Aug 3, 2015 at 2:36 PM, Alex Kost <alezost@gmail.com> wrote:
>> Federico Beffa (2015-08-03 10:50 +0300) wrote:

[...]

>>> 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.

Agreed.

So I agree we should rename the other packages as well.  The problem
that will make it disruptive is that the UIs don’t know about renames,
so ‘guix package -u’ for instance will never upgrade ‘geiser’ etc. and
people may not notice.

Maybe we should fix that first.

A simple idea that comes to mind would be to have definitions like:

  (define-syntax-rule (define-deprecated-alias variable pkg old-name)
    (define-public variable
      (package
        (inherit pkg)
        (name old-name)
        (properties `((deprecated-alias . ,pkg))))))

  ;; The new package is called “emacs-geiser”; previous it was called
  ;; “geiser”.
  (define-deprecated-alias old-geiser geiser "geiser")

and somehow have (guix profiles) handle it nicely.  That is, installing
“geiser” would automatically install “emacs-geiser” and emit a warning;
upgrading a profile containing “geiser” would upgrade to “emacs-geiser”
and emit a warning.

Any takers?

Ludo’.