From: Marius Bakke <marius@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>,
Jesse Gibbons <jgibbons2357@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: How to package inputrc
Date: Tue, 14 Jul 2020 00:01:27 +0200 [thread overview]
Message-ID: <87v9iraxc8.fsf@gnu.org> (raw)
In-Reply-To: <20200713183525.GD10256@E5400>
[-- Attachment #1: Type: text/plain, Size: 1452 bytes --]
Efraim Flashner <efraim@flashner.co.il> writes:
> On Mon, Jul 13, 2020 at 09:30:31PM +0300, Efraim Flashner wrote:
>> On Mon, Jul 13, 2020 at 11:26:59AM -0600, Jesse Gibbons wrote:
>> > > In order to achieve this more elegant I could write a simple service to
>> > > copy the file to /etc. Another option would be a small package.
>> >
>> > I like the service idea a lot better. It appears to me that Guix is designed for services to deal with the more customizable parts of the installation, whereas packages are standard. /etc/inputrc is one of those things each system admin would want to customize, just like most of the things in /etc.
>>
>> I'll go ahead and link to my os-release service here. It's a small
>> service that creates an /etc/os-release file. The service in action¹ and
>> the actual service itself. It would also be possible to create an even
>> simpler file than the one I made here², with something like this:
>>
>> (define %inputrc
>> (plain-file "inputrc"
>> "set show-mode-in-prompt on\n"
>> "set enable-bracketed-paste on\n"
>> "set editing-mode vi\n"
>> "Control-l: clear-screen\n"
>> "set bell-style visible\n"))
>
> The above wouldn't actually work. It needs a string-append or to not be
> multiple strings.
Or use 'mixed-text-file' instead of 'plain-file'. Though 'string-join'
might be clearer in this case. :-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-07-13 22:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 17:26 How to package inputrc Jesse Gibbons
2020-07-13 18:30 ` Efraim Flashner
2020-07-13 18:35 ` Efraim Flashner
2020-07-13 22:01 ` Marius Bakke [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-12 22:01 Jonathan Brielmaier
2020-07-13 1:17 ` Bengt Richter
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=87v9iraxc8.fsf@gnu.org \
--to=marius@gnu.org \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=jgibbons2357@gmail.com \
/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).