$ strings /bin/bash | grep -c prefer-visible-bell
1
$ man bash | grep -c prefer-visible-bell
0
$ find /usr/share/doc/bash* -type f | xargs zgrep prefer-visible-bell | wc -l
0
Furthermore, one could finally do
$ run_readline_command dump-variables | grep bell
prefer-visible-bell is set to `on'
bell-style is set to `audible'
which is rather impossible, even if one does bind unbound commands.
Currently one must probably use script(1), bind the key, and then exit
and grep
On the bash page at the end of
Readline Command Names
The following is a list of the names of the commands and the default
key sequences to which they are bound. Command names without an accom-
panying key sequence are unbound by default. In the following descrip-
Hello,
below this mail you can find a minimal script misbehaving when
job-control is configured out (tested on linx with different archs,
libc's, and versions (including current git)).
Notice that the configure script disables job-control when a run-time
test (which could easily be a built-time t
On Sat, Sep 17, 2016 at 04:57:08PM -0400, Chet Ramey wrote:
> On 9/17/16 4:47 PM, Benoît Dejean wrote:
> > On Sat, Sep 17, 2016 at 01:12:24PM -0400, Chet Ramey wrote:
> >> On 9/16/16 9:25 PM, Ben wrote:
> >>> Hello,
> >>>
> >>> using bash-4.4, setting PS0 to '\[\033[1;36m\]started at
> >>> \t\[\033
On 9/17/16 4:47 PM, Benoît Dejean wrote:
> On Sat, Sep 17, 2016 at 01:12:24PM -0400, Chet Ramey wrote:
>> On 9/16/16 9:25 PM, Ben wrote:
>>> Hello,
>>>
>>> using bash-4.4, setting PS0 to '\[\033[1;36m\]started at
>>> \t\[\033[0m\]\n' makes it output PS0 with a non-printable \x01\x02
>>> prefix and
On Sat, Sep 17, 2016 at 01:12:24PM -0400, Chet Ramey wrote:
> On 9/16/16 9:25 PM, Ben wrote:
> > Hello,
> >
> > using bash-4.4, setting PS0 to '\[\033[1;36m\]started at
> > \t\[\033[0m\]\n' makes it output PS0 with a non-printable \x01\x02
> > prefix and suffix.
>
> Yes, those are the expansions
On Sat, Sep 17, 2016 at 01:31:42PM -0400, Chet Ramey wrote:
> On 9/16/16 9:12 PM, Ben wrote:
> > Hello,
> >
> > bash-4.4 doesn't build with --enable-static-link. Buidling with an
> > additional --without-bash-malloc makes it work.
>
> Sigh. There's another function defined in the same file where
On 9/16/16 9:12 PM, Ben wrote:
> Hello,
>
> bash-4.4 doesn't build with --enable-static-link. Buidling with an
> additional --without-bash-malloc makes it work.
Sigh. There's another function defined in the same file where glibc
defines malloc/realloc/free, and it's using that function internall
On 9/16/16 9:25 PM, Ben wrote:
> Hello,
>
> using bash-4.4, setting PS0 to '\[\033[1;36m\]started at
> \t\[\033[0m\]\n' makes it output PS0 with a non-printable \x01\x02
> prefix and suffix.
Yes, those are the expansions of the \[ and \] escape sequences. Since
$PS0 is not being passed to readli
On 9/16/16 3:06 PM, Eric Pruitt wrote:
> Bash Version: 4.4
> Patch Level: 0
> Release Status: release
>
> Description:
> In Bash 4.3, "${var/*/text}" would generate "" if var was a zero-length
> string and "text" if it contained at least one character. In Bash 4.4,
> this
> is
On 9/16/16 1:51 AM, Eric Pruitt wrote:
> Bash Version: 4.4
> Patch Level: 0
> Release Status: release
>
> Description:
> I have a script that execute `if [[ "$(<"/proc/$1/cmdline")" = tmux*
> ]];`.
> All /proc/*/cmdline include null bytes, and as of Bash 4.4, this
> results in
>
On 9/12/16 11:11 PM, Martijn Dekker wrote:
> The command
>
> kill -l 0
>
> outputs T. I would expect EXIT as T is not a valid signal or
> pseudosignal name. Since T is the last letter of EXIT, I suspect a typo
> somewhere.
>
> AT&T ksh93 outputs EXIT. pdksh/mksh and zsh output 0 (presumabl
Chet Ramey wrote:
+== CHANGES ==
d. Readline's input handler now performs signal processing if read(2) is
interrupted by SIGALRM or SIGVTALRM.
---
It sounds like the ability for signal handlers to be called while
waiting for input has been restored.
h. Use psele
14 matches
Mail list logo
