[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Feature request: INFOKEY_FILE environment variable
From: |
Gavin Smith |
Subject: |
Re: Feature request: INFOKEY_FILE environment variable |
Date: |
Thu, 18 Mar 2021 20:18:00 +0000 |
User-agent: |
Mutt/1.9.4 (2018-02-28) |
On Wed, Mar 17, 2021 at 03:35:11PM -0700, Edwin Kofler wrote:
> Greetings,
>
> For the info program, it would be useful to have some "INFOKEY_FILE"
> environment variable that
> behaves similar to the '--init-file` option, so the configuration is read
> when info is
> launched from environments in which argv cannot be supplied or modified; for
> example, when
> other programs exec info using functions from the exec family. Because I
> prefer to keep my home directly
> clean by putting config in "$HOME/.config", having a way to set the file
> manually (just
> like $MOST_INITFILE, $INPUTRC, $SCREENRC, etc.), really helps. I really don't
> care what the
> env var is named - just that it works. Thoughts?
>
> Regards,
> Edwin
Would a better option be to look for the config file under the .config
directory as well as that seems to be a standard location for config
files? What are the conventions for that directory? How common is it
for this kind of environment variable to be used for this purpose -
you give three examples but I'm not familiar with them and they don't seem
to follow any pattern - INPUTRC is for the readline library, not a program,
and I assume that MOST_INITFILE is for the most pager and SCREENRC is for
GNU screen.