See http://stackoverflow.com/q/103944/26428
On Tue, Nov 9, 2010 at 12:58 AM, Ajay Jain wrote:
> Hi,
>
> I use bash via Xterm. As a result I open multiple Xterm windows. When
> I type commands on the shell, they get saved only for that particular
> shell's history. I want to be able to collate tha
Greg Wooledge writes:
> Crap, libncurses5-dev isn't installed.
If you have neither libncurses nor libtermap then configure will use the
included termacp.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for som
On Tue, Nov 09, 2010 at 08:29:15PM +0900, OZAKI Masanobu wrote:
> Greg Wooledge wrote:
> > (On my system, there is no -a unary operator in the test(1) man page, but
> > the command apparently supports one, undocumented. Isn't this fun?)
>
> Neither on my system. I found descriptions of the -a u
> `clear' command works.
> $TERM is linux, and xterm: I've tested in both TTYs, and X11
>
>
> $ bind -p | grep clear
> "\C-l": clear-screen
>
> I've tried to un-bind (bind -r ^L), at this moment TTY beeps on Ctrl-L
> and re-bind (bind ^L:clear-screen): no beep, just new line
>
> the terminal ca
On Tue, Nov 09, 2010 at 04:38:21AM +0100, hum...@chorion.ath.cx wrote:
> the terminal can C-l, I use it with Debian's default /bin/bash
> (3.2.39(1)-release)
> but as soon as I go to /usr/local/bin/bash (where bash4 is), it doesn't work
> any more.
It would be helpful to indicate which version o
On the Austin Group mailing list, David Korn (of ksh93 fame)
complained[1] that bash's 'local' uses dynamic scoping, but that ksh's
'typeset' uses static scoping, and argued that static scoping is saner
since it matches the behavior of declarative languages like C and Java
(dynamic scoping mainly m
On Sun, Oct 31, 2010 at 09:24:24PM +0800, Clark J. Wang wrote:
> 2010/10/31 Lluís Batlle i Rossell
>
> > Hello,
> >
> > I don't think this problem is related to any recent bash version only. I've
> > seen
> > this since years I think.
> >
> > Nevertheless I'm using GNU bash, version 4.0.17(1)-rel
Hello.
On Mon, 2010-11-08 at 08:45:11 -0500,
Greg Wooledge wrote:
> On Fri, Nov 05, 2010 at 04:24:23PM -0500, Jonathan Nieder wrote:
> > >>> Please try
> > >>> % bash -c 'test ! -a . && echo true'
> > >>> and compare with the result of
> > >>> % bash -c '/usr/bin/test ! -a . && echo true'
>
On Tue, 9 Nov 2010, Eric Blake wrote:
On the Austin Group mailing list, David Korn (of ksh93 fame)
complained[1] that bash's 'local' uses dynamic scoping, but that ksh's
'typeset' uses static scoping, and argued that static scoping is saner
since it matches the behavior of declarative languages
Hello,
due to a typo I've unfortunately openned a 'Ctrl- does nothing' subject.
to make things clear, I paste here the answer that solved my case :
On Tue, Nov 09, 2010 at 14:45, Greg Wooledge wrote:
[snip]
> I've just built 4.1.9(1)-release on Debian 5.0 i386 using no options at
> all (straight
On 11/9/10 4:52 PM, Eric Blake wrote:
> On the Austin Group mailing list, David Korn (of ksh93 fame)
> complained[1] that bash's 'local' uses dynamic scoping, but that ksh's
> 'typeset' uses static scoping, and argued that static scoping is saner
> since it matches the behavior of declarative langu
Eric Blake wrote:
In static scoping, function f2 does not shadow a declaration of a, so
references to $a within f2 refer to the global variable. The local
variable a of f1 can only be accessed within f1; the behavior of f2 is
the same no matter how it was reached.
If it matters (I already kno
12 matches
Mail list logo
