unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bengt Richter <bokr@bokr.com>
To: Jonathan Brielmaier <jonathan.brielmaier@web.de>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: How to package inputrc
Date: Mon, 13 Jul 2020 03:17:51 +0200	[thread overview]
Message-ID: <20200713011751.GA48314@LionPure> (raw)
In-Reply-To: <59c5cfc9-e39e-8038-f745-7f14480d0f82@web.de>

On +2020-07-13 00:01:32 +0200, Jonathan Brielmaier wrote:
> Hi folks,
> 
> an annoying thing for me in a default Guix installation is the lack of
> an inputrc definition[0]. So while using the shell I miss going through
> my bash history via "page up"/"page down" keys.
> 
> To tackle this issue I created a simple inputrc and copied to
> `/etc/inputrc`:
> ```

What hat are you wearing? Admin or user as logged in, or user as user
of a particular app, or?

Of course, as owner of your machine, you may do as you please, if you can ;-)

But IMO user preferences should stay out of the root directory, like /etc/...
so I would put your mods in $HOME/.inputrc, as your ArchLinux referece [0] discusses,
or maybe under ~/.emacs.d/ if it's just emacs you want to tweak.

As you say, other distros provide defaults, but unless you want to modify
everyone's experience who logs in on the machine, I would say stick to
$HOME/.something, where something IMO should not be more global in effect than need be.

Think twice about anything you need sudo to accomplish :)

I think it is a kind of namespace hygiene problem, when it is not clear who gets
to define names and what they do under what circumstances.

My 2¢ ;-)

> # alternate mappings for "page up" and "page down" to search the history
> "\e[5~": history-search-backward
> "\e[6~": history-search-forward
> ```
> 
> 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 think other distros provide one in the default, basic installation:
> ArchLinux[1], Debian[2] and openSUSE has even a longer one.
> 
> Are others missing that too? What do you think?
> 
> Good night
> Jonathan
> 
> [0] https://wiki.archlinux.org/index.php/Readline
> [1]
> https://git.archlinux.org/svntogit/packages.git/plain/trunk/inputrc?h=packages/readline
> [2] https://packages.debian.org/buster/all/readline-common/filelist
> 

-- 
Regards,
Bengt Richter


  reply	other threads:[~2020-07-13  1:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-12 22:01 How to package inputrc Jonathan Brielmaier
2020-07-13  1:17 ` Bengt Richter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-07-13 17:26 Jesse Gibbons
2020-07-13 18:30 ` Efraim Flashner
2020-07-13 18:35   ` Efraim Flashner
2020-07-13 22:01     ` Marius Bakke

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=20200713011751.GA48314@LionPure \
    --to=bokr@bokr.com \
    --cc=guix-devel@gnu.org \
    --cc=jonathan.brielmaier@web.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).