X-Recipient: archive-cygwin AT delorie DOT com 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= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; 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; s=default; bh=3pMO0JYSLk3ZHquAn2wBnNa92I E=; b=jeGhcgayAP0Ix/+W23gj1262Gspy+R43nwuRWpd7CzrWGx1B8aH6kTbLi8 RmCRlXiyYNFZoPFfbai7bki+swFhZ7n3E0/QAfl/wfVuZeqcyGqKEheT4vG9nghD LNdr2FTkpW7/9Jx+8j56v3+Dx3eZ4O67x+yH5wMfI2uGrZuJ4= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-0.4 required=5.0 tests=AWL,BAYES_50 autolearn=ham version=3.3.1 spammy=abs, food, served, H*UA:Roundcube X-HELO: www16.qth.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 To: cygwin AT cygwin DOT com Subject: Re: base-files revisited In-Reply-To: References: Message-ID: <769049fc1d34ef8567bcf1df3dfeda13@plebeian.com> X-Sender: wagnerc AT plebeian DOT com User-Agent: Roundcube Webmail/1.3.7 X-IsSubscribed: yes 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