Re: Any interest in using HTML for locally-installed Texinfo documentation?

> From: Gavin Smith > Date: Tue, 9 Apr 2019 00:46:09 +0100 > Cc: guix-devel@gnu.org, Texinfo > > I'm still trying to implement very basic functionality in the Qt code. > I will probably push on with it and see how far I get. If GTK is used > instead, the needed functionality would be present,

Re: guix.gnu.org sub-domain

Hi Julien, Thank you for working on this! Julien Lepiller writes: > I'm still unsure about how to update the certificates with the dns > challenge. I found a script that could help us with updating the zone > served by knot when it's configured as a master. > > We could use that to update the r

Re: Any interest in using HTML for locally-installed Texinfo documentation?

On Mon, Apr 08, 2019 at 05:12:17PM +0200, Ludovic Courtès wrote: > Neat! > > From a “social” viewpoint, I think WebKitGTK would be more appropriate, > GTK+/GNOME being affiliated with GNU. It's the "social" viewpoint that will make it a success. We don't just need a proof-of-concept or something

Re: #guix logs no longer updated

Ludo', Ludovic Courtès wrote: Here’s a mission for you, dear reader: write a service that starts znc, with suitably posed duct tape and chewing gum, and modify so that it’s automatically started. I started writing

Re: Video narration

Hi Ricardo, > This is probably my mistake. I didn’t pay much attention to frame > rates when I first built the scripts for generating the CLI videos. > Ok, thanks. This is fixed in commit 7180fff4ecb46cfed41c6214579a53af6a636a21. The new frame rate is 25 fps. This is the European standard fo

Re: #guix logs no longer updated

Hello! Ricardo Wurmus skribis: > This coincided with the reconfiguration of bayfront. The logger is > really just znc held together with duct tape and chewing gum. It’s > working again. Sorry. Here’s a mission for you, dear reader: write a service that starts znc, with suitably posed duct ta

Re: wip-netlink

Hi there! Gábor Boskovits skribis: > I've pushed a branch with some preliminary work on the netlink wrapper > for guix, so that > we can have ipv6 static network configuration, and a bunch of other > goodies, including hopefully container networking. > This is in quite an early stage, I was most

Re: Any interest in using HTML for locally-installed Texinfo documentation?

Hello, Gavin Smith skribis: > On Tue, Apr 02, 2019 at 09:46:05AM -0700, Per Bothner wrote: >> Both Electron and QtWebEngine have mechanisms for communicating between >> the "browser" window and the main application, which is not sandboxed. >> (For QtWebEngine the main application is regular non-

Re: custom kernel config

Hello, Efraim Flashner skribis: > title: Creating and using a custom Linux kernel on Guix System > date: 2019-04-04 00:00 > author: Efraim Flashner > tags: kernel, customization Really nice! > (define-public linux-libre-E2140 > (let ((base > ((@@ (gnu packages linux) make-linux-lib

Re: guix.gnu.org sub-domain

Le 8 avril 2019 10:59:36 GMT+02:00, "Ludovic Courtès" a écrit : >Hello Julien, > >Ricardo Wurmus skribis: > >> I just went through the list of things that we wanted to accomplish >> before releasing 1.0. One of them is the use of a guix.gnu.org >> sub-domain. >> >> Could you please let us know w

Re: Any interest in using HTML for locally-installed Texinfo documentation?

On Tue, Apr 02, 2019 at 05:02:19PM -0400, George Clemmer wrote: > Gavin Smith writes: > [...] > > A manual with this interface added is at > > https://www.gnu.org/software/texinfo/manual/texinfo-html/Overview.html. > > All the important keyboard commands that work in the Info viewers are > > imple

Re: Any interest in using HTML for locally-installed Texinfo documentation?

On Tue, Apr 02, 2019 at 09:46:05AM -0700, Per Bothner wrote: > Both Electron and QtWebEngine have mechanisms for communicating between > the "browser" window and the main application, which is not sandboxed. > (For QtWebEngine the main application is regular non-sandboxed C++ code.) > For a desktop

Re: (current-filename) behaves differently in environment|build

Hello, wldhx skribis: > Discovered following behaviour while setting up GNUnet CI: > > Given > > ./gnu/packages/a.scm: >... >(source (local-file (dirname (current-filename >... It’s enough to write: (local-file ".." #:recursive? #t) since ‘local-file’ already takes care of r

Re: Installer & services

Ludovic Courtès skribis: > In commit 7d1030a63592aa2f94f6617786f22cfa83fb346f I added a dialog to > select networking services, currently sshd and Tor. > > I realized that for a server kind of installation, it’d be nice to > have NetworkManager or connman in there. I’ll see if I can add it. Don

Re: What is the philosophy behind shepherd?

Hello Katherine, Katherine Cox-Buday skribis: > A couple weeks ago, I was watching a video called "The Tragedy of > Systemd"[1]. In it, Benno Rice discusses the need for a so-called > "system layer" which is responding to the many complicated signals > coming into a system from thing happening (

Re: guix.gnu.org sub-domain

Hello Julien, Ricardo Wurmus skribis: > I just went through the list of things that we wanted to accomplish > before releasing 1.0. One of them is the use of a guix.gnu.org > sub-domain. > > Could you please let us know what the current status is regarding the > Knot DNS server configuration?

Re: bug#34407: [PATCH] shepherd: Delete the socket file upon exit.

Hello, iyzs...@member.fsf.org (宋文武) skribis: > Yes, I have the 'rm /run/user/1000/shepherd/socket' workaround in my session > script too... I never had to do that because /run is wiped at boot time, like Danny wrote. > According to 'man 2 bind', the socket pathname should be deleted when no > l