Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "John Morrison" <john DOT r DOT morrison AT ntlworld DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: bash and the delete key
Date: Sun, 28 Jul 2002 18:06:17 +0100
Message-ID: <NCEBJJFMCAOKNNABBFIMOEDFCEAA.john.r.morrison@ntlworld.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-reply-to: <20020728165001.66579.qmail@web20005.mail.yahoo.com>
Importance: Normal

> From: Joshua Daniel Franklin
> 
> > The next generation of the profile package will, probably,
> > have a /etc/skel directory.  When /etc/profile creates a
> > home directory it will also copy the contents of /etc/skel
> > to that directory.
> 
> > I suggest that you take up with the bash maintainer the
> > (possible) creation of a /etc/skel/.inputrc file with
> > appropriate (default) contents :)
> 
> > It might even be possible to add two 'defaults' - a
> > /etc/skel/.inputrc (linux like defaults)
> > /etc/skel/alt/.inputrc.mimic.windows (or something like)
> 
> I think this is a great idea for readline (.inputrc), bash
> (.bash_profile), tcsh (.cshrc), etc. Actually I don't see
> why they couldn't all be in the 'profile' package, though maybe
> that's not exactly correct.

I'd rather [shell|X|...] specific skeleton files be kept with the
appropriate package, otherwise I'd have _far_ too much to maintain.

I don't mind adding something to the profile script which, given
a xxx.default when there is no xxx cp /etc/skel/xxx.default
/etc/skel/xxx before copying to the users home (if appropriate).

> Also perhaps these files could be
> not just useful but also instructional, with comments pointing
> out options, examples, and documentation. For example:
> 
> # Aliases for Windows equivalents; see 'info fileutils' for differences

I'm making an effort to try and comment all my files (starting
with 1.1-1), if I miss something or get it wrong, please
comment! :)

J.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/