> I am facing a problem on the console with bash. Bash simply does
> not remember my commands in the right order. Most of the commands I
> type in a login session are forgotten in the next session. Moving the
> Up and Down arrow keys navigates a highly incorrect and incomplete
> command history
®om wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: i486
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
> -DCONF_OSTYPE='lin$
> uname output: Linux rom-laptop 2.6.24-21-generic #1 SMP Mon Aug 25
> 17:32:09 UTC$
Hello,
I am writing a System Report script for Ubuntu, and even 'though I have the
word exit on the last line of the script, when I run the script in terminal
I have to hit enter a second time after running the script to get the
terminal prompt back.
I'm uploading the script, have a look and tel
Chet Ramey a écrit :
®om wrote:
Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
-DCONF_OSTYPE='lin$
uname output: Linux rom-laptop 2.6.24-21-generic #1 SMP Mon Aug 25
17:32:
®om wrote:
> printf was only a way to send 0xe282ac on stdin of each tool, it doesn't
> matter how printf interprets the bytes. What is important is how the
> tool ("cut" for example, or read -n) interprets them :)
I don't have any control over the various implementations of `cut' out
there. The
Dear All,
Here's a rather controversial request, namely that bash should support
'goto'.
The reason I'd like to see it is to make debugging long scripts easier.
I'm working at the moment on a 2000+ line script, and if I want to test
stuff at the end, I'd really like to have something like th
On Mon, 2008-09-22 at 20:44 +0100, Richard Neill wrote:
>
How about...
> ---
> #!/bin/bash
>
> #initialisation stuff goes here.
>
if false; then
>
> #lots of stuff here that I want to skip.
> #Bash doesn't have a multi-line comment feature.
> #Even if it did, one can't do a mu
Julian Bradfield wrote:
> In every other shell I've used, the behaviour of ctrl-C in an
> interactive shell is to interrupt the current command-line and return
> to the shell prompt.
> This is, I think, the behaviour expected by the user in almost all
> circumstances. In the rare circumstance when
Richard Neill wrote:
> Dear All,
In the future please start a new message for a new thread of
discussion. When you reply to old messages from three months ago
those of us who actually keep months worth of email see the message
threaded with the previous discussion about variables and subshells.
I
Bob Proulx wrote:
Richard Neill wrote:
Dear All,
In the future please start a new message for a new thread of
discussion. When you reply to old messages from three months ago
those of us who actually keep months worth of email see the message
threaded with the previous discussion about vari
Richard Neill wrote:
> Bob Proulx wrote:
> >In the future please start a new message for a new thread of
> >discussion. When you reply to old messages from three months ago
> >those of us who actually keep months worth of email see the message
> >threaded with the previous discussion about variabl
Configuration Informatio= n [Automatically generated, do not change]:
Machine: powerpc
OS: darwin9.0
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='powerpc' -
DCONF_OSTYPE='\
darwin9.0' -DCONF_MACHTYPE='powerpc-apple-darwin9.0' -DCONF_VENDOR=
'apple' -
12 matches
Mail list logo
