>dim. 31 déc. 2023 at 13:07, Nicolas Goaziou wrote:
> Hello,
>
> Cayetano Santos writes:
>
>> We distribute emacs packages from gnu/elpa by downloading .tar files
>> from there: I’m thinking about emacs-ggtags.
>>
>> My first concern is, what emacs-ggtags 0.9.0 corresponds to exactly ?
Hello,
Cayetano Santos writes:
> We distribute emacs packages from gnu/elpa by downloading .tar files
> from there: I’m thinking about emacs-ggtags.
>
> My first concern is, what emacs-ggtags 0.9.0 corresponds to exactly ?
> There is no 0.9.0 tag in upstream github reposotory, and, if I
Federico Beffa skribis:
> I'm just saying: If we use separate directories as package.el does, we
> avoid all name clashes with probability 1. If we use a flat structure
> such a claim can not be done.
>
> Even if the clash "only" happens with, say, a README file, the state
> of the system (user p
On Mon, Jun 22, 2015 at 9:43 PM, Ludovic Courtès wrote:
> Federico Beffa skribis:
>
>> On Sun, Jun 21, 2015 at 11:12 PM, Ludovic Courtès wrote:
>>> Federico Beffa skribis:
>
> [...]
>
>> Unfortunately this doesn't work without modification. The reason is
>> that I follow the emacs packa
Federico Beffa skribis:
> On Sun, Jun 21, 2015 at 11:12 PM, Ludovic Courtès wrote:
>> Federico Beffa skribis:
[...]
> Unfortunately this doesn't work without modification. The reason is
> that I follow the emacs package.el strategy to install each ELPA
> package in it's own sub-di
On Sun, Jun 21, 2015 at 11:12 PM, Ludovic Courtès wrote:
> Federico Beffa skribis:
>
>> On Fri, Jun 19, 2015 at 2:13 PM, Ludovic Courtès wrote:
> guix.el already takes care of that (info "(guix) Emacs Initial Setup"),
> so that should be enough.
Unfortunately this doesn't work
Federico Beffa skribis:
> On Fri, Jun 19, 2015 at 2:13 PM, Ludovic Courtès wrote:
guix.el already takes care of that (info "(guix) Emacs Initial Setup"),
so that should be enough.
>>>
>>> Unfortunately this doesn't work without modification. The reason is
>>> that I follow the emacs pa
On Fri, Jun 19, 2015 at 2:13 PM, Ludovic Courtès wrote:
>>> guix.el already takes care of that (info "(guix) Emacs Initial Setup"),
>>> so that should be enough.
>>
>> Unfortunately this doesn't work without modification. The reason is
>> that I follow the emacs package.el strategy to install each
Federico Beffa skribis:
> On Tue, Jun 16, 2015 at 6:00 PM, Ludovic Courtès wrote:
[...]
>>> To make those packages automatically available in Emacs without the
>>> need for any code in the user '.emacs' file, I would suggest to
>>> include in our Emacs package site initialization file some cus
Federico Beffa (2015-06-18 21:32 +0300) wrote:
> On Wed, Jun 17, 2015 at 8:21 PM, Alex Kost wrote:
>> The code for loading "…-autoloads.el" files is placed in
>> "guix-emacs.el", so perhaps it would be enough to adjust:
>>
>> - 'guix-emacs-find-autoloads' to make it look at subdirs;
>>
>> - 'guix
On Wed, Jun 17, 2015 at 8:21 PM, Alex Kost wrote:
> The code for loading "…-autoloads.el" files is placed in
> "guix-emacs.el", so perhaps it would be enough to adjust:
>
> - 'guix-emacs-find-autoloads' to make it look at subdirs;
>
> - 'guix-emacs-load-autoloads' to add the subdir to 'load-path'
On Wed, Jun 17, 2015 at 10:00 PM, Alex Kost wrote:
> Mark H Weaver (2015-06-17 21:42 +0300) wrote:
>
>> Federico Beffa writes:
>>
>>> What do you think about the attached implementation?
>>
>> [...]
>>
>>> +(define (emacs-byte-compile files)
>>> + "Byte compile FILES, a list of file names."
>>>
Mark H Weaver (2015-06-17 21:42 +0300) wrote:
> Federico Beffa writes:
>
>> What do you think about the attached implementation?
>
> [...]
>
>> +(define (emacs-byte-compile files)
>> + "Byte compile FILES, a list of file names."
>> + (if (pair? files)
>> + (for-each (lambda (f)
>> +
Federico Beffa writes:
> What do you think about the attached implementation?
[...]
> +(define (emacs-byte-compile files)
> + "Byte compile FILES, a list of file names."
> + (if (pair? files)
> + (for-each (lambda (f)
> + (let ((expr `(let ()
> +
Federico Beffa (2015-06-17 10:42 +0300) wrote:
> On Tue, Jun 16, 2015 at 6:00 PM, Ludovic Courtès wrote:
[...]
>>> To make those packages automatically available in Emacs without the
>>> need for any code in the user '.emacs' file, I would suggest to
>>> include in our Emacs package site initiali
On Tue, Jun 16, 2015 at 6:00 PM, Ludovic Courtès wrote:
>> - An ELPA package importer
>> - An 'emacs-build-system'
>
> Sounds very useful to me!
Thanks for the interest!
>> To make those packages automatically available in Emacs without the
>> need for any code in the user '.emacs' file, I would
On Tue, Jun 16, 2015 at 6:24 PM, Mark H Weaver wrote:
> FYI, this pattern of using 'fold' with 'and' and a boolean seed would be
> more transparent if handled by 'every' from (srfi srfi-1):
>
> (every (lambda (f)
>(zero? (system* emacs "--batch" "-Q" "-L" el-dir
>
Federico Beffa writes:
> (define* (build #:key outputs inputs #:allow-other-keys)
> "Compile .el files."
> (let* ((emacs (string-append (assoc-ref inputs "emacs") "/bin/emacs"))
> (out (assoc-ref outputs "out"))
> (name-ver (store-dir->elpa-name-version out))
> (el-
Awesome developments!
On Tue, Jun 16, 2015 at 06:00:44PM +0200, Ludovic Courtès wrote:
> Federico Beffa skribis:
>
> > To be concrete about what I'm proposing, attached you find:
> >
> > - An ELPA package importer
> > - An 'emacs-build-system'
>
> Sounds very useful to me!
>
> > There are a lo
Federico Beffa skribis:
> To be concrete about what I'm proposing, attached you find:
>
> - An ELPA package importer
> - An 'emacs-build-system'
Sounds very useful to me!
> There are a lot of Emacs packages. For this reason I would like to
> propose to prefix them with 'emacs-' as we do with Py
This seems like a great idea.
Federico Beffa writes:
> There are a lot of Emacs packages. For this reason I would like to
> propose to prefix them with 'emacs-' as we do with Python, ...
IMO an 'el-' prefix would be better since it refers to the actual
language, and it's more concise.
--
Mathi
21 matches
Mail list logo
