From: Chris Wagner <wagnerc@plebeian.com>
To: cygwin@cygwin.com
Subject: Re: base-files revisited
Date: Sun, 07 Apr 2019 18:58:00 -0000 [thread overview]
Message-ID: <769049fc1d34ef8567bcf1df3dfeda13@plebeian.com> (raw)
In-Reply-To: <CAAgpg9aoVkqmxHxsEjjbYFFftrtvfVJk9HLbUKh0h1r3LgweAQ@mail.gmail.com>
Personally I wouldn't want to see yet another .directory in home.
Endless fractionation of config is one of the things about unix that
irks me. This is not to say that there aren't perfectly valid use cases
for YACF (yet another config file).
Perhaps this would be best served by a new shell configurator package.
Or possibly some other already existing shell manager. If someone had a
use for a non standard shell config, he could install and run
shell-configurator which would walk him through all of the various
possibilities for shell initialization. Whether to use foo.d, special
files to include, color, etc. It could also save these settings to its
own init file that could be applied to new users for organizational use
or just to backup your own settings.
Thanks.
On 2019-04-06 10:08 am, John Morrison wrote:
> Hi,
>
> I've been asked at work to get the standard base-files extended with
> specifics for the company I work for and wondered if this would be a
> good
> time to revisit how the .bashrc file in particular is put together.
>
> What I was considering would be introducing a ~/.bashrc.d/ folder and
> splitting the existing ~/.bashrc file into its component parts;
>
> * alias.bashrc
> * completion.bashrc
> * functions.bashrc
> * history.bashrc
> * shell.bashrc
> * umask.bashrc
>
> and changing .bashrc to source all the *.bashrc files.
>
> This would allow easier extension of the bashrc with, in my case,
> company
> specific options (proxies, common aliases etc).
>
> I was also thinking of taking some more of the sample from
> https://www.tldp.org/LDP/abs/html/sample-bashrc.html, for example the
> colours and some more of the aliases and adding them into the existing
> sets.
>
> Thoughts?
>
> I think Achim Gratz took over the base-files from me. Achim, are you
> still
> around? Open for a discussion?
>
> Kind regards
>
> John.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-04-07 18:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-06 14:08 John Morrison
2019-04-07 18:58 ` Chris Wagner [this message]
2019-04-08 7:05 ` Brian Inglis
2019-04-08 17:46 ` John Morrison
2019-04-08 16:56 ` Achim Gratz
2019-04-08 17:37 ` John Morrison
2019-04-08 18:25 ` Achim Gratz
2019-04-08 19:04 ` Brian Inglis
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=769049fc1d34ef8567bcf1df3dfeda13@plebeian.com \
--to=wagnerc@plebeian.com \
--cc=cygwin@cygwin.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.
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).