>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 em
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 reposo
Hello Guix,
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
understand it correctly
Dear Guix Developers,
I would like to suggest adding version information to the Guix packages for
Emacs.
This would make it easier to know which version is installed,
upgrade/downgrade easily, and avoid confusion with version set to 0.0.0.
This is an example I'm using the version in Guix
Hi Maxim!
Em [2022-07-06 qua 09:35:28-0400], Maxim Cournoyer escreveu:
> I guess it's simply an oversight. Could you try to removing it from the
> affected packages and see if they still byte compile and run happily?
> If they do, a patch would be welcome.
I have just sent the patch to
Git master. When I tried to use the new
> emoji commands on the "C-x 8e" prefix, I was getting an error message
> (sorry for not having written it down) mentioning transient. I solved
> it by modifying Guix recipes to not pull emacs-transient as propagated
> input of some E
Hi! I apologize for the delay and reply below:
Em [2022-07-04 seg 14:41:06+0200], zimoun escreveu:
> Which are the Emacs packages you are using without an explicit mention
> to emacs-transient?
I have modified the recipes (removing the dependency on emacs-transient)
of the followin
Hi,
On Sun, 03 Jul 2022 at 19:10, "Jorge P. de Morais Neto"
wrote:
> So, why do many Emacs packages still pull emacs-transient, when Guix has
> Emacs version 28.1, which has Transient built-in? This redundancy
> wastes (a little bit of) bandwidth, install time and disk
prefix, I was getting an error message
(sorry for not having written it down) mentioning transient. I solved
it by modifying Guix recipes to not pull emacs-transient as propagated
input of some Emacs packages I installed via Guix.
So, why do many Emacs packages still pull emacs-transient, whe
I'm newbie to Guix and know little about Guix jargon. I'm sorry about that my
words make you puzzled.
>? The source of what?
I mean the emacs package in guix source, the emacs-next package, precisely.
>> will record its modification of EMACSLOADPATH in profile,
>
>Where is it recorded?
Hi,
Can you clarify what you mean with
> the Emacs package in the source
? The source of what?
and
> will record its modification of EMACSLOADPATH in profile,
Where is it recorded? Which modification? What is "EMACSLOADPATH in profile"?
--
Pierre Neidhardt
https://ambrevar.xyz/
I use guix to manage different version of Emacs in a foreign distro. However,
the Emacs package in the source will record its modification of EMACSLOADPATH
in profile, which will cause conflict in different version of Emacs, and also
conflict with Emacs in foreign distro.
My idea is move the
(Damn, just realized that I'd sent this email to guix-devel-request :p)
Emacs packages seem to be inconsistently named.
Some are prefixed with "emacs-", others are not.
Here is a list of missing prefixes on package names:
--8<---cut here---start
Alex Kost <alez...@gmail.com> writes:
> Ricardo Wurmus (2016-07-13 00:04 +0300) wrote:
>
>> Hi Guix,
>>
>> here are almost all of the remaining Emacs packages that I previously
>> installed via package.el. I hope you find them useful!
>>
>> ~~
Roel Janssen <r...@gnu.org> writes:
> Ricardo Wurmus writes:
>
>> Hi Guix,
>>
>> here are almost all of the remaining Emacs packages that I previously
>> installed via package.el. I hope you find them useful!
>>
>> ~~ Ricardo
>>
>> Ric
Ricardo Wurmus writes:
> Hi Guix,
>
> here are almost all of the remaining Emacs packages that I previously
> installed via package.el. I hope you find them useful!
>
> ~~ Ricardo
>
> Ricardo Wurmus (17):
> gnu: Add emacs-el-mock.
> gnu: Add emacs-espuds.
&g
Hi Guix,
here are almost all of the remaining Emacs packages that I previously
installed via package.el. I hope you find them useful!
~~ Ricardo
Ricardo Wurmus (17):
gnu: Add emacs-el-mock.
gnu: Add emacs-espuds.
gnu: Add emacs-expand-region.
gnu: Add emacs-fill-column-indicator.
gnu
This is the updated patchset for adding emacs-minimal and using it to
build emacs packages. Only PATCH 2 is new: I removed the mess I did
with native-inputs and used #:emacs keyword for auctex instead (thanks
to Federico and Ludovic for the comments!). The rest patches are the
same as they were
Hello, currently we use either 'emacs' or 'emacs-no-x' to build
(byte-compile) emacs packages. What about making a really minimal emacs
to use for this task?
Most of the times it should be enough. AFAICT the only case where a
full-featured emacs is needed is auctex; and for this particular case
Ludovic Courtès (2016-02-06 15:46 +0300) wrote:
> Alex Kost <alez...@gmail.com> skribis:
>
>> Fixes <http://bugs.gnu.org/22550>.
>
> Please add “Reported by …”.
Added.
>> * emacs/guix-emacs.el: Autoload Emacs packages installed in a system
>> profile.
>
> OK!
--
Alex
>> (guix-emacs-load-autoloads): Replace with ...
>> (guix-emacs-autoload-packages): this. New procedure. At first, find a
>> list of directories with Emacs packages, then add them to 'load-path'
>> and finally, load autoloads.
>> (guix-emacs-load-autoloads-
Alex Kost <alez...@gmail.com> skribis:
> Fixes <http://bugs.gnu.org/22550>.
Please add “Reported by …”.
> * emacs/guix-emacs.el: Autoload Emacs packages installed in a system
> profile.
OK!
packages): this. New procedure. At first, find a
> list of directories with Emacs packages, then add them to 'load-path'
> and finally, load autoloads.
> (guix-emacs-load-autoloads-maybe): Rename to ...
> (guix-emacs-autoload-packages-maybe): ... this.
> * emacs/guix-backend.el (gui
Fixes <http://bugs.gnu.org/22550>.
* emacs/guix-emacs.el: Autoload Emacs packages installed in a system
profile.
---
emacs/guix-emacs.el | 1 +
1 file changed, 1 insertion(+)
diff --git a/emacs/guix-emacs.el b/emacs/guix-emacs.el
index 5c32f2f..aa8e299 100644
--- a/emacs/guix-emacs.el
with Emacs packages, then add them to 'load-path'
and finally, load autoloads.
(guix-emacs-load-autoloads-maybe): Rename to ...
(guix-emacs-autoload-packages-maybe): ... this.
* emacs/guix-backend.el (guix-after-repl-operation-hook): Adjust for the
renaming.
* doc/emacs.texi (Emacs Initial Setup
Alex Kost <alez...@gmail.com> skribis:
> * doc/guix.texi (Application Setup)[Emacs Packages]: New subsection.
[...]
> +directory for each package is a good idea. It is very similar to how
> +Emacs package system organizes the file structure (@pxref{Package
^^
“the Emacs
* doc/guix.texi (Application Setup)[Emacs Packages]: New subsection.
---
doc/guix.texi | 19 +++
1 file changed, 19 insertions(+)
diff --git a/doc/guix.texi b/doc/guix.texi
index c252f63..7c60780 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -1051,6 +1051,25 @@ for Chinese
On Mon, Jun 22, 2015 at 9:43 PM, Ludovic Courtès l...@gnu.org wrote:
Federico Beffa be...@ieee.org skribis:
On Sun, Jun 21, 2015 at 11:12 PM, Ludovic Courtès l...@gnu.org wrote:
Federico Beffa be...@ieee.org skribis:
[...]
Unfortunately this doesn't work without modification. The reason is
Federico Beffa be...@ieee.org skribis:
On Sun, Jun 21, 2015 at 11:12 PM, Ludovic Courtès l...@gnu.org wrote:
Federico Beffa be...@ieee.org skribis:
[...]
Unfortunately this doesn't work without modification. The reason is
that I follow the emacs package.el strategy to install each ELPA
On Sun, Jun 21, 2015 at 11:12 PM, Ludovic Courtès l...@gnu.org wrote:
Federico Beffa be...@ieee.org skribis:
On Fri, Jun 19, 2015 at 2:13 PM, Ludovic Courtès l...@gnu.org wrote:
guix.el already takes care of that (info (guix) Emacs Initial Setup),
so that should be enough.
Unfortunately
Federico Beffa be...@ieee.org skribis:
On Fri, Jun 19, 2015 at 2:13 PM, Ludovic Courtès l...@gnu.org 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
initialization file some custom code
(to activate our ELPA emacs packages) such as the one in the attached
'guix-elpa.el' file.
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
of Emacs packages installed in PROFILE.
If PROFILE is nil, use `guix-user-profile'.
Return nil if there are no emacs packages installed in PROFILE.
- (let ((dir (guix-emacs-directory profile)))
-(if (file-directory-p dir)
-(directory-files dir 'full-name -autoloads\\.el\\')
+ (let
On Fri, Jun 19, 2015 at 2:13 PM, Ludovic Courtès l...@gnu.org 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
On Wed, Jun 17, 2015 at 10:00 PM, Alex Kost alez...@gmail.com wrote:
Mark H Weaver (2015-06-17 21:42 +0300) wrote:
Federico Beffa be...@ieee.org writes:
What do you think about the attached implementation?
[...]
+(define (emacs-byte-compile files)
+ Byte compile FILES, a list of file
On Wed, Jun 17, 2015 at 8:21 PM, Alex Kost alez...@gmail.com 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
Mark H Weaver (2015-06-17 21:42 +0300) wrote:
Federico Beffa be...@ieee.org 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)
+
initialization file some custom code
(to activate our ELPA emacs packages) such as the one in the attached
'guix-elpa.el' file.
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
Federico Beffa be...@ieee.org 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 ()
+
would suggest to
include in our Emacs package site initialization file some custom code
(to activate our ELPA emacs packages) such as the one in the attached
'guix-elpa.el' file.
guix.el already takes care of that (info (guix) Emacs Initial Setup),
so that should be enough.
Unfortunately
Federico Beffa be...@ieee.org 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))
Federico Beffa be...@ieee.org 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
!
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, ...
Sounds good. I think I prefer ‘emacs-’ to ‘el-’ because that’s probably
what people expect.
To make those packages automatically available in Emacs without the
need
On Tue, Jun 16, 2015 at 6:24 PM, Mark H Weaver m...@netris.org 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
This seems like a great idea.
Federico Beffa be...@ieee.org 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
difference is that the
former include final .info and dir files. It is likely that there
are more differences that I didn't notice due to my limited knowledge
about Emacs packages.
To be concrete about what I'm proposing, attached you find:
- An ELPA package importer
- An 'emacs-build-system
commands)
and loads it. And on emacs startup ...-autoloads.el files for each
package are loaded, so that M-x ... for installed packages become
available.
So for the real “drop-in replacement”, the following should be done
(IMHO): Guix recipes for emacs packages should be modified to
additionally generate
Ludovic Courtès (2014-08-28 15:51 +0400) wrote:
Alex Kost alez...@gmail.com skribis:
[...]
So for the real “drop-in replacement”, the following should be done
(IMHO): Guix recipes for emacs packages should be modified to
additionally generate ...-autoloads.el (like it is done
m...@netris.org skribis:
I've attached patches to add new packages for 'magit', 'paredit',
'emacs-w3m', and 'emacs-wget'. While working on these packages, I found
that I needed a way to substitute multi-line s-expressions in the elisp
code, in order to replace initializers for variables.
l...@gnu.org (Ludovic Courtès) writes:
m...@netris.org skribis:
I've attached patches to add new packages for 'magit', 'paredit',
'emacs-w3m', and 'emacs-wget'. While working on these packages, I found
that I needed a way to substitute multi-line s-expressions in the elisp
code, in order
50 matches
Mail list logo
