public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Patrick Ohnewein <pohnewein@prodata.it>
To: cygwin@sourceware.cygnus.com
Subject: Basic Questions
Date: Thu, 13 Apr 2000 09:28:00 -0000	[thread overview]
Message-ID: <38F5F4C5.EAB7C16@prodata.it> (raw)

Sorry for this question, but I didn't find anything related in the docs
neither in the archives of the mailing list.

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 :-)

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

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?

thanks in advance

patrick

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

             reply	other threads:[~2000-04-13  9:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-13  9:28 Patrick Ohnewein [this message]
2000-04-13  9:38 ` Larry Hall (RFK Partners, Inc)
     [not found]   ` <4.3.1.2.20000413124827.00bad250@pop.ma.ultranet.com>
     [not found]     ` <4.3.1.2.20000414102032.00d87100@pop.ma.ultranet.com>
2000-04-20  1:24       ` Patrick Ohnewein
2000-04-20 13:59         ` Michael Hirmke
2000-04-20 14:13           ` Charles Wilson
  -- strict thread matches above, loose matches on Subject: below --
2000-04-13  9:44 Earnie Boyd
1997-08-05 14:46 basic questions sed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=38F5F4C5.EAB7C16@prodata.it \
    --to=pohnewein@prodata.it \
    --cc=cygwin@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).