Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <20000413164418.19614.qmail@web119.yahoomail.com>
Date: Thu, 13 Apr 2000 09:44:18 -0700 (PDT)
From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To: earnie_boyd AT yahoo DOT com
Subject: Re: Basic Questions
To: Patrick Ohnewein <pohnewein AT prodata DOT it>, cygwin AT sourceware DOT cygnus DOT com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

--- Patrick Ohnewein <pohnewein AT prodata DOT it> wrote:
> Sorry for this question, but I didn't find anything related in the docs
> neither in the archives of the mailing list.
> 

Don't know why you can't find it in the archives.  See
http://www.eGroups.com/message/gnu-win32/19503?&start=16756 for reference.

> Now is there some doc for cygwins-bash B20 available somewhere. I need
> to set bell-style=visible, because the beeping annoyes my coworkers. Now
> I tried to create an .inputrc file in my home dir, which seams to not be
> read. performing set bell-style=visible doesn't work, doing it in the
> .bashrc (which get's read from my HOME dir) doesn't work neither. So I
> tried to set the environment in the startup .bat-file. But it seams the
> shell doesn't care about the env var.
> 
> How can I deactivate this horror bell :-)
> 

I know that it can be done.

> Another question how can I change LS_COLOR for ls, where do I get docs
> related dircolors
> 

You should be able to find all documents for FSF GNU supported software at
http://www.gnu.org.


> Where should I perform calls to bind, to change keymapping, because
> .inputrc doesn't get read and calling bind in .bashrc doesn't have
> effect. And may be a BUG in bind:
> 
> # bind -p > ~/bindings
> # bind -f ~/bindings
> 
> sometimes does output that the file bindings doesn't exist and when it
> doesn't output any error message it doesn't change bindings.
> 
> I am only able to change bindings from command line, how should I make
> them persistent?
> 

The problem is the file format.  ~/.inputrc does get read.
 

=====
---
   Earnie Boyd: <mailto:earnie_boyd AT yahoo DOT com>
            __Cygwin: POSIX on Windows__
Cygwin Newbies: <http://www.freeyellow.com/members5/gw32/index.html>
           __Minimalist GNU for Windows__
  Mingw32 List: <http://www.egroups.com/group/mingw32/>
    Mingw Home: <http://www.mingw.org/>

__________________________________________________
Do You Yahoo!?
Send online invitations with Yahoo! Invites.
http://invites.yahoo.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com