From: Guillaume Le Vaillant <glv@posteo.net>
To: jgart <jgart@dismail.de>
Cc: 53738@debbugs.gnu.org
Subject: [bug#53738] [PATCH] gnu: nyxt: Add missing input.
Date: Thu, 03 Feb 2022 09:49:26 +0000 [thread overview]
Message-ID: <874k5gw9ok.fsf@kitej> (raw)
In-Reply-To: <20220202220516.24153-1-jgart@dismail.de>
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
jgart via Guix-patches via <guix-patches@gnu.org> skribis:
> * gnu/packages/web-browsers.scm (nyxt)[inputs]: Add sbcl-cl-gopher.
> ---
> gnu/packages/web-browsers.scm | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/gnu/packages/web-browsers.scm b/gnu/packages/web-browsers.scm
> index c49e3ceac5..1aec6d6adc 100644
> --- a/gnu/packages/web-browsers.scm
> +++ b/gnu/packages/web-browsers.scm
> @@ -639,6 +639,7 @@ (define-public nyxt
> ("cl-containers" ,sbcl-cl-containers)
> ("cl-css" ,sbcl-cl-css)
> ("cl-custom-hash-table" ,sbcl-custom-hash-table)
> + ("cl-gopher" ,sbcl-cl-gopher)
> ("cl-html-diff" ,sbcl-cl-html-diff)
> ("cl-json" ,sbcl-cl-json)
> ("cl-ppcre" ,sbcl-cl-ppcre)
Hi,
What issue is solved by adding cl-gopher to inputs?
As far as I can see the source code for Nyxt 2.2.4 doesn't contain any
reference to cl-gopher, so just adding it to inputs will not change the
produced nyxt program.
According to the upstream repository, support for Gopher and Gemini will
be in Nyxt 3.0.0, which has not been released yet.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2022-02-03 10:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 22:05 [bug#53738] [PATCH] gnu: nyxt: Add missing input jgart via Guix-patches via
2022-02-03 9:49 ` Guillaume Le Vaillant [this message]
2022-02-03 21:37 ` jgart via Guix-patches via
2022-02-03 22:20 ` bug#53738: " Guillaume Le Vaillant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874k5gw9ok.fsf@kitej \
--to=glv@posteo.net \
--cc=53738@debbugs.gnu.org \
--cc=jgart@dismail.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).