let-alist.el

let-alist.el

[Eli Zaretskii]

Shouldn't it be in lisp/emacs-lisp/, like all the rest of our Lisp
infrastructure?

Re: let-alist.el

[Artur Malabarba]

Why we have an "emacs-lisp" dir inside the "lisp" dir has always been
a mistery to me. Is there anything inside the "lisp" dir that is *not*
emacs-lisp code? :-)

Anyway, placing it inside "lisp" was probably a mistake.

Re: let-alist.el

[Eli Zaretskii]

> Date: Mon, 15 Jun 2015 16:51:37 +0100
> From: Artur Malabarba <bruce.connor.am@gmail.com>
> Cc: emacs-devel <emacs-devel@gnu.org>
> 
> Why we have an "emacs-lisp" dir inside the "lisp" dir has always been
> a mistery to me. Is there anything inside the "lisp" dir that is *not*
> emacs-lisp code? :-)

You've elided my answering this question, even before it was asked.

Re: let-alist.el

[Artur Malabarba]

> You've elided my answering this question, even before it was asked.

Forgive my english, but I don't know what you mean. (Or, if it means
what I think it means, then I don't see why...)

Re: let-alist.el

[Eli Zaretskii]

> Date: Mon, 15 Jun 2015 18:48:43 +0100
> From: Artur Malabarba <bruce.connor.am@gmail.com>
> Cc: emacs-devel <emacs-devel@gnu.org>
> 
> > You've elided my answering this question, even before it was asked.
> 
> Forgive my english, but I don't know what you mean. (Or, if it means
> what I think it means, then I don't see why...)

Sorry, I thought it was clear: lisp/emacs-lisp/ is where we keep the
infrastructure for Emacs Lisp.

Re: let-alist.el

[Artur Malabarba]

> Sorry, I thought it was clear
You were, I just clearly needed a second coffee yesterday.

Well, getting back on track, should I just move it to "emacs-lisp/"?

The "lisp" dir looked like a reasonable place to me because I see lots
of proper packages in there (with version headers and all), and I
thought of let-alist as a package. But really, makes no difference to
me.

Re: let-alist.el

[Eli Zaretskii]

> Date: Tue, 16 Jun 2015 16:22:18 +0100
> From: Artur Malabarba <bruce.connor.am@gmail.com>
> Cc: emacs-devel <emacs-devel@gnu.org>
> 
> Well, getting back on track, should I just move it to "emacs-lisp/"?

Yes, I think so.

> The "lisp" dir looked like a reasonable place to me because I see lots
> of proper packages in there (with version headers and all), and I
> thought of let-alist as a package.

So are eieio and pcase and macroexp and easymenu and many others you
see in emacs-lisp.  The important attribute is that they are basis on
which to build many applications.

Thanks.

Re: let-alist.el

[Artur Malabarba]

Done

2015-06-16 16:27 GMT+01:00 Eli Zaretskii <eliz@gnu.org>:
>> Date: Tue, 16 Jun 2015 16:22:18 +0100
>> From: Artur Malabarba <bruce.connor.am@gmail.com>
>> Cc: emacs-devel <emacs-devel@gnu.org>
>>
>> Well, getting back on track, should I just move it to "emacs-lisp/"?
>
> Yes, I think so.
>
>> The "lisp" dir looked like a reasonable place to me because I see lots
>> of proper packages in there (with version headers and all), and I
>> thought of let-alist as a package.
>
> So are eieio and pcase and macroexp and easymenu and many others you
> see in emacs-lisp.  The important attribute is that they are basis on
> which to build many applications.
>
> Thanks.