Re: Commit Access to Emacs-Guix
That's great news? Do you have a link to the project? How do you intend to receive contributions? Via a mailing list? Cheers! -- Pierre Neidhardt https://ambrevar.xyz/ signature.asc Description: PGP signature
Re: Emacs-Guix repository location moved to Savannah
Hi,
John Soo 写道：
Emacs-Guix has a new home! I just pushed
a42f66cb40a9e60611f429a403b08dbed29bae02 to Emacs-Guix on
Savannah.
Thank you for taking care of this, and innumerable thanks to Alex
for creating and maintaining emacs-guix for so many years.
My first order of business will be fixing the broken
subcommands. I
don't use many of them, though. If you have a command you want
fixed,
please let me know and I will priortize it.
I use it very infrequently and it currently won't start:
Starting Guix REPL ... [2 times]
geiser-repl--connection: No Geiser REPL for this buffer (try M-x
run-geiser)
Starting Guix REPL ... [2 times]
geiser-repl--wait-for-prompt: No prompt found!
Probably my fault somewhere. Still, it would be nice if this
‘just worked’ for those who don't have and want a custom Geiser
set-up.
What do you think about having conversations about Emacs-Guix on
guix-devel?
I think that's a good idea & better than creating a separate list.
Where do you accept patches? The one below is untested.
Kind regards,
T G-R
From 348ede3b9ba2e571e20af9e310d632de80331eae Mon Sep 17 00:00:00 2001
From: Tobias Geerinckx-Rice
Date: Tue, 12 Jan 2021 11:45:01 +0100
Subject: [PATCH] Remove all references to the ancient GuixSD name.
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
* README (About, Installation): Replace ‘GuixSD’ with ‘Guix System’.
* doc/emacs-guix.texi (Package Commands, Profiles, Generations, System)
(System From File, Services, Service Commands): Likewise.
* elisp/guix-about.el (guix-logo-file): Unuse ‘guixsd-logo.svg’.
* elisp/guix-utils.el (guix-guixsd?): Remove now unused procedure.
(guix-read-os-file-name): Update docstring.
* images/README: Refer to singular ‘guix-logo.svg’.
* images/guixsd-logo.svg: Delete file.
---
README |4 +-
doc/emacs-guix.texi | 14 +-
elisp/guix-about.el |9 +-
elisp/guix-ui-service-location.el|2 +-
elisp/guix-ui-service.el |2 +-
elisp/guix-ui-system.el |2 +-
elisp/guix-utils.el |6 +-
elisp/guix.el|2 +-
images/README|6 +-
images/guixsd-logo.svg | 1022 --
scheme/emacs-guix/system-generations.scm |2 +-
11 files changed, 21 insertions(+), 1050 deletions(-)
delete mode 100644 images/guixsd-logo.svg
diff --git a/README b/README
index 1513e42..55a6956 100644
--- a/README
+++ b/README
@@ -22,7 +22,7 @@ In short, Emacs-Guix provides the following features:
+ profiles
- + profile generations (including system generations for GuixSD)
+ + profile generations (including system generations for Guix System)
+ packages
@@ -94,7 +94,7 @@ the current commit of Emacs-Guix using [[file:guix.scm]] file:
guix package --install-from-file=guix.scm
#+END_SRC
-* IMPORTANT NOTE for non-GuixSD users
+* IMPORTANT NOTE for non-Guix-System users
If you installed Guix using [[https://www.gnu.org/software/guix/manual/en/html_node/Binary-Installation.html][Binary Installation]] method, most likely your
environment (in particular, =GUILE_LOAD_PATH=) does not know where Guile
diff --git a/doc/emacs-guix.texi b/doc/emacs-guix.texi
index 06e4ee2..9547953 100644
--- a/doc/emacs-guix.texi
+++ b/doc/emacs-guix.texi
@@ -339,7 +339,7 @@ Display installed packages. As explained above, @kbd{M-x
guix-installed-packages} uses an arbitrary profile that you can specify,
while the other commands display packages installed in 2 special
profiles: @file{~/.guix-profile} and @file{/run/current-system/profile}
-(only on GuixSD).
+(only on Guix System).
@findex guix-obsolete-packages
@item M-x guix-obsolete-packages
@@ -632,7 +632,7 @@ the default user profile
profile, populated by @code{guix pull}
@item /var/guix/profiles/system
-system profile (only on GuixSD)
+system profile (only on Guix System)
@item @env{GUIX_PROFILE}
(only if this environment variable is set and this profile is not the
@@ -739,7 +739,7 @@ date/time prompt,,, org, The Org Manual}).
@end table
-If you use GuixSD, you may also look at the system generations using
+If you use Guix System, you may also look at the system generations using
the similar commands (@pxref{System Commands}).
@node Generation Keys
@@ -783,7 +783,7 @@ with another marked generation.
@node System
@chapter System
-This chapter describes Emacs-Guix features related to GuixSD, in
+This chapter describes Emacs-Guix features related to Guix System, in
particular:
@itemize
@@ -802,7 +802,7 @@ particular:
@section System From File
@cindex system
-Your system configuration file (for GuixSD) contains
+Your system configuration file (for Guix System) contains
@code{operating-system} declaration (@pxref{operating-system
Reference,,, guix, The GNU Guix Reference Manual}).
@@
Re: Cuirass logo - artwork.
Hello Luis, > About the integration of this logo with the Guix look, I thought that this > logo was for Cuirass itself, not necessarily for the instance available in > https://ci.guix.gnu.org/. I thought it could be nice to use to logo for: - The Cuirass project page that would be hosted at https://guix.gnu.org/cuirass for instance. - The Cuirass Web UI page to replace or in addition to the Guix logo at https://ci.guix.gnu.org. - The favicon of Cuirass Web UI also at https://ci.guix.gnu.org. > If Cuirass Web UI supports theming, the Guix instance could easily change the > branding so that it is uniform with the style that has been used so far to > name and brand other components. So Guix components like GuixHPC, GuixData, > GuixCI, GuixDays, and so on, could use the same graphic style. > > (Maybe Guix could use a Guile library defining an SXHTML/CSS theme to make it > easier to style the websites of the different Guix components) That's a good idea, having some uniformity between all Guix websites would be nice. If there are no more voters, it looks like the 2B logo with the orange logo is the winner! Thanks, Mathieu
New Russian PO file for 'guix-manual' (version 1.2.0-pre3)
Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'guix-manual' has been submitted by the Russian team of translators. The file is available at: https://translationproject.org/latest/guix-manual/ru.po (We can arrange things so that in the future such files are automatically e-mailed to you when they arrive. Ask at the address below if you want this.) All other PO files for your package are available in: https://translationproject.org/latest/guix-manual/ Please consider including all of these in your next release, whether official or a pretest. Whenever you have a new distribution with a new version number ready, containing a newer POT file, please send the URL of that distribution tarball to the address below. The tarball may be just a pretest or a snapshot, it does not even have to compile. It is just used by the translators when they need some extra translation context. The following HTML page has been updated: https://translationproject.org/domain/guix-manual.html If any question arises, please contact the translation coordinator. Thank you for all your work, The Translation Project robot, in the name of your translation coordinator.
Re: Emacs-Guix repository location moved to Savannah
Hi Pierre! Pierre Neidhardt writes: > > - guix-devel-build-package-definition > > It seems that Geiser chokes on it because of the output. > I don't know if this can be worked around somehow. > If not, an alternative would be to invoke the `guix repl` executable > instead of using Geiser. > > - guix-devel-download-package-source > > Make it work with all kinds of sources, such as git URLs. Ok, noted. >> What do you think about having conversations about Emacs-Guix on >> guix-devel? > > No strong opinion! Alright, it would be most convenient to me if we can have conversations on guix-devel. Is that ok by the guix group? Thanks! - John
Re: Emacs-Guix repository location moved to Savannah
Hi Tobias, Tobias Geerinckx-Rice writes: > Hi, > > John Soo 写道： >> Emacs-Guix has a new home! I just pushed >> a42f66cb40a9e60611f429a403b08dbed29bae02 to Emacs-Guix on Savannah. > > Thank you for taking care of this, and innumerable thanks to Alex for > creating and maintaining emacs-guix for so many years. Yes, many many thanks to Alex for their work over the years. >> My first order of business will be fixing the broken subcommands. I >> don't use many of them, though. If you have a command you want >> fixed, >> please let me know and I will priortize it. > > I use it very infrequently and it currently won't start: > > Starting Guix REPL ... [2 times] > geiser-repl--connection: No Geiser REPL for this buffer (try M-x > run-geiser) > Starting Guix REPL ... [2 times] > geiser-repl--wait-for-prompt: No prompt found! > > Probably my fault somewhere. Still, it would be nice if this ‘just > worked’ for those who don't have and want a custom Geiser set-up. Does it still not start? As of (guix) commit f98e3adcd533a4a4c5482343a26d01076e946f92 I at least can start a repl without a crash. >> What do you think about having conversations about Emacs-Guix on >> guix-devel? > > I think that's a good idea & better than creating a separate list. > > Where do you accept patches? The one below is untested. That's also a good question. I would prefer to use the existing guix-patches. Is that ok by the standard mailing list administrators? As to the patch, I would like to apply it. Is Guix System still the preferred name? I thought another renaming took place. I am possibly very out of date on that info though. Best regards, John
Re: Emacs-Guix repository location moved to Savannah
Hi Ryan, Ryan Prior writes: > How do you feel about removing commands that nobody feels like fixing? It > might help Emacs-Guix build a reputation for reliability. I plan on trying to fix them all, but I may remove some if they are just not possible any longer. > I think it's a good idea. Conversing regularly on this list will keep people > abreast of what state things are in. Moving conversation to a dedicated > channel likely means nobody would read, which disincentivizes writing. If > discussion on this list reaches a level of volume where it's annoying, that's > the > signal to explore alternate channels. Thanks, good point. I think we'll stay here until it gets too noisy (if it is ok by the adminstrators). Best regards, John
Re: Emacs-Guix repository location moved to Savannah
Hi Pierre, I forgot to answer your other question. Emacs-Guix is a sub-project of Guix on Savannah https://savannah.gnu.org/projects/guix it is "Emacs interface to GNU Guix". The repository is available at https://git.savannah.gnu.org/cgit/guix/emacs-guix.git. - John
Re: Emacs-Guix repository location moved to Savannah
John Soo 写道： Does it still not start? As of (guix) commit f98e3adcd533a4a4c5482343a26d01076e946f92 I at least can start a repl without a crash. Good to know. I'll try again and let you know. Where do you accept patches? The one below is untested. That's also a good question. I would prefer to use the existing guix-patches. Is that ok by the standard mailing list administrators? I can't think of a better place nor can I imagine we'll be overwhelmed by emacs-guix patches. (And if we are, that's probably a good thing at this point?) As to the patch, I would like to apply it. Is Guix System still the preferred name? Yep. There's also no separate ‘System’ logo anymore[0]. Guix System being merely a different earthly manifestation of the one eternal Guix. I thought another renaming took place. I am possibly very out of date on that info though. Nope. Kind regards, T G-R [0]: http://guix.gnu.org/en/graphics/ signature.asc Description: PGP signature
Re: Emacs-Guix repository location moved to Savannah
> I can't think of a better place nor can I imagine we'll be overwhelmed > by emacs-guix patches. > > (And if we are, that's probably a good thing at this point?) That is my thought, too. >> As to the patch, I would like to apply it. Is Guix System still the >> preferred name? > > Yep. There's also no separate ‘System’ logo anymore[0]. Guix System > being merely a different earthly manifestation of the one eternal > Guix. > >> I thought another renaming took place. I am possibly >> very out of date on that info though. > > Nope. Ok, I pushed 825ab772f7f64700a9914ccbf9b079eb6aef6461 with a slight modification to the commit message. Thanks! John
