From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Julien Lepiller <julien@lepiller.eu>
Cc: Disseminate Dissent <disseminatedissent@protonmail.com>,
51538@debbugs.gnu.org
Subject: [bug#51538] First Patch Submit Ever: Additions to the Cookbook Documentation
Date: Thu, 11 Nov 2021 18:04:06 +0100 [thread overview]
Message-ID: <20211111170354.5hf57jssxoh2yg5s@pelzflorian.localdomain> (raw)
In-Reply-To: <FC2C93E1-D906-4A5D-916B-F436E81AC35A@lepiller.eu>
On Mon, Nov 08, 2021 at 02:04:12PM -0500, Julien Lepiller wrote:
> Le 8 novembre 2021 12:18:50 GMT-05:00, "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> a écrit :
> >Bash always enables readline as far as I can see. Perhaps you used a
> >system that disabled C-l in the ~/.inputrc file, which would also
> >disable it for a Guix-installed bash? Some Slackware users complain
> >about non-working C-l on stackoverflow. Anyway I will leave this
> >patch for experienced guix commiters to decide; IMHO the clear command
> >should not be needed with Guix and the cookbook so far contains only
> >what can be done with Guix itself. Even though I like the idea of a
> >FAQ section and am happy about new Guix contributors such as you.
> I think this is fine. The cookbook should recommend using Ctrl-L and
> suggest you can install clear with the ncurses package. We get that
> question from time to time, so I think it belongs to a FAQ :)
One might expect terminal clearing with C-l or clear in an operating
system manual, but is role of Guix to be an operating system?
I’d think not, the manual/cookbook would blow up too much.
A command to search what package provides the program clear is what
belongs in the manual.
Regards,
Florian
next prev parent reply other threads:[~2021-11-11 17:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 23:56 [bug#51538] First Patch Submit Ever: Additions to the Cookbook Documentation Disseminate Dissent via Guix-patches via
2021-11-01 15:10 ` [bug#51538] TOC jgart via Guix-patches via
2021-11-04 15:17 ` [bug#51538] First Patch Submit Ever: Additions to the Cookbook Documentation Disseminate Dissent via Guix-patches via
2021-11-08 9:29 ` pelzflorian (Florian Pelz)
2021-11-08 9:53 ` pelzflorian (Florian Pelz)
2021-11-08 13:50 ` Disseminate Dissent via Guix-patches via
2021-11-08 17:18 ` pelzflorian (Florian Pelz)
2021-11-08 19:04 ` Julien Lepiller
2021-11-11 17:04 ` pelzflorian (Florian Pelz) [this message]
2021-11-08 13:52 ` Disseminate Dissent via Guix-patches via
2021-11-09 0:21 ` [bug#51538] (no subject) jgart via Guix-patches via
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=20211111170354.5hf57jssxoh2yg5s@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=51538@debbugs.gnu.org \
--cc=disseminatedissent@protonmail.com \
--cc=julien@lepiller.eu \
/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).