On Tue, Sep 8, 2009 at 10:53 AM, Robert Lillack wrote:
> Hi,
>
> I seem to be unable to rebind Control-W – am I the only one experiencing
> this?
> ...
> What am I doing wrong?
>
> C-w is a binding inherited from the tty settings,
You can disable this with:
bind 'set bind-tty-special-chars of
Hi,
I seem to be unable to rebind Control-W – am I the only one experiencing
this?
I know this annoyed me years ago on FreeBSD and Solaris, and now I
stumbled upon this problem again on Mac OS X and Ubuntu:
$ bind -p | grep C-w
"\C-w": unix-word-rubout
$ bind '"\C-w": backward-kill-word'
$
sorry, It is sh_xfree but not xf_xfree.
On Tue, Sep 8, 2009 at 1:03 PM, Lookey Lam wrote:
> Hello:
> I am now using bash source code 4.0 to compile a binary with
> the configure option as following:
> --enable-prompt-string-decoding --enable-progcomp
> --enable-help-builtin --enable-hi
Hello:
I am now using bash source code 4.0 to compile a binary with
the configure option as following:
--enable-prompt-string-decoding --enable-progcomp
--enable-help-builtin --enable-history --with-bash-malloc=no
every thing goes smoothy but when I type tab key after i have
t
On Tue, Sep 08, 2009 at 11:39:02AM -0700, peter360 wrote:
> Thanks for the explanation. So my understanding of the way ssh works is
> still incorrect. I am confused about at which point the two parameters,
> "-c" and "ulimit -a" were converted into three, "-c", "ulimit", and "-a". I
> guess I n
Bob,
Thanks for the explanation. So my understanding of the way ssh works is
still incorrect. I am confused about at which point the two parameters,
"-c" and "ulimit -a" were converted into three, "-c", "ulimit", and "-a". I
guess I need to read the source of ssh and bash to really understand
On Mon, Sep 7, 2009 at 2:27 PM, Linda Walsh wrote:
> I was wanting to enter a colon in a file name that had to be readable on
> both Unix and Dos.
>
> Unicode has a 'display' colon: At U+FF1A, which works find -- I can enter
> it
> in bash in linux -- it displays as a colon on linux and on window
