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:content-type
	:content-transfer-encoding:date:from:to:subject:in-reply-to
	:references:message-id; q=dns; s=default; b=aMfTxTh+LeLW7/afNSHf
	6QEgljY/LR8Bk831lCMOAqBbKAb0M42dIAGPcJr1zTI9K5Au6FywtLQ6pbDUTtkB
	lGYrD6a3cVkr8Sr2CSzS+I3FEJ8BscHVxF2AuQAWtCkyD6DZI0yt6TUN5inVQf7f
	5/LciFL5KQIS+GC8bc3UwPc=
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
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Date: Sun, 07 Apr 2019 14:58:27 -0400
From: Chris Wagner <wagnerc@plebeian.com>
To: cygwin@cygwin.com
Subject: Re: base-files revisited
In-Reply-To: <CAAgpg9aoVkqmxHxsEjjbYFFftrtvfVJk9HLbUKh0h1r3LgweAQ@mail.gmail.com>
References: <CAAgpg9aoVkqmxHxsEjjbYFFftrtvfVJk9HLbUKh0h1r3LgweAQ@mail.gmail.com>
Message-ID: <769049fc1d34ef8567bcf1df3dfeda13@plebeian.com>
User-Agent: Roundcube Webmail/1.3.7

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