Chet Ramey wrote:
Matthias Schniedermeyer wrote:
Hi
Version:
From Debian SID
bash --version
GNU bash, version 3.00.16(1)-release (i386-pc-linux-gnu)
As it seems it is not possible to append multiple command to the
"history", only replace the last command.
I'd classify this as a bug
Jeff Miller <[EMAIL PROTECTED]> wrote:
> It is possible on our test Solaris 8 system that the original
> calling bash shell will set the controlling process of the terminal
> to the pid that it originally forked to after the new process had
> been created. In this case is not the new bash process.
Matthias Schniedermeyer wrote:
> Hi
>
>
> Version:
> From Debian SID
>
>> bash --version
> GNU bash, version 3.00.16(1)-release (i386-pc-linux-gnu)
>
>
> As it seems it is not possible to append multiple command to the
> "history", only replace the last command.
I'd classify this as a bug rat
Jeff Miller wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: sparc
> OS: solaris2.8
> Compiler: gcc
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='sparc'
> -DCONF_OSTYPE='sol
> aris2.8' -DCONF_MACHTYPE='sparc-sun-solaris2.8' -DCONF_VENDOR='sun'
> -DL
[EMAIL PROTECTED] wrote:
> Bash Version: 3.0
> Patch Level: 16
> Release Status: release
>
> Description:
> I had been using ${HOSTNAME%%.*} in my prompt to show the local
> host name portion of my full host name (e.g. localhost instead
> of localhost.localdomain). After
William Park wrote:
>
> Description:
> 'declare -p' adds backslash (\) in front of newline. When this
> is fed back, the newline disappears. Should this happen?
>
> Repeat-By:
> 0 node1:~$ a='11
> > 22'
> 0 node1:~$ declare -p a
> declare -- a="11\
> 22
Configuration Information [Automatically generated, do not change]:
Machine: i386
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i386-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba
