DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:from:date:message-id:subject:to
	:content-type; q=dns; s=default; b=O12NYZY7ygseGANx7x1QC29sRuLyS
	6/jV48PwAeVU0cy+nA8a/aGWyWEv2lRCTL6TPaxFRldToQib3TY19Q1AdTSiR7ce
	7Qj0ovp1ItKj91S+ZCKrkjrn4biD6MDqTVqgtnfT3u/NG1JD5UbFKsEchk56kA6u
	oyOe4/9Ck1iZGg=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
From: John Morrison <john@morrison.ec>
Date: Sat, 6 Apr 2019 15:08:12 +0100
Message-ID: <CAAgpg9aoVkqmxHxsEjjbYFFftrtvfVJk9HLbUKh0h1r3LgweAQ@mail.gmail.com>
Subject: base-files revisited
To: cygwin@cygwin.com
Content-Type: text/plain; charset="UTF-8"

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