Currently `trap` has no way to set a signal to the system default.
Rather `trap - PIPE` for example sets the signal handling to
the value it have upon entrance to the shell. It's common enough
for systems to disable SIGPIPE, so it would be useful to
support a shell wrapper that would renable stand
On Mon, Feb 25, 2019 at 4:01 PM L A Walsh wrote:
> ntc() { while IFS='' read -r input; do printf "$input;" ; done ; }
> printf $'\xc2\00\00\00\00'|ntc|hexdump -C
>
> both result in no output.
a) If you actually want the null bytes to be piped, the \0 has to be
interpreted by printf. Using $'' q
On Mon, 25 Feb 2019 12:59:38 -0800
L A Walsh wrote:
> In this case, the decode of \xc2 doesn't swallow the following
> character.
I want to clarify that \xc2 (and other characters in the range
mentioned above) can only swallow a \0. Other characters are
unaffected.
>
> But in 4.4.12, using IFS
On Sun, Feb 24, 2019 at 11:22 PM Robert Elz wrote:
> I think these are actually more the insertion of explicit null
> strings, rather than $@ when it contains null strings. These
> are essentially the same as the ${b+s ''} issue that was discussed
> a week or so ago, and which Chet already said
On 2/25/2019 11:32 AM, Chet Ramey wrote:
> On 2/25/19 11:17 AM, Olga Ustuzhanina wrote:
>
>
>
> This is an invalid multibyte character. The \xc2 is the valid first byte
> of a multibyte character, but the next byte read makes the sequence
> invalid. The read builtin resynchronizes on the followi
On 2/25/2019 6:53 AM, Chet Ramey wrote:
> Setting debugging mode in one of the startup files is an alternate way
> to start the bash debugger, equivalent to invoking bash with --debugger.
> It's been that way since the debugging support was introduced in bash-3.0.
>
I suspected that given the
On 2/25/19 11:17 AM, Olga Ustuzhanina wrote:
> Bash Version: 5.0
> Patch Level: 2
> Release Status: release
>
> Description:
> When using `IFS= read -r -d '' input` to read null-delimited
> strings on a system with bash 5.0+ and UTF-8 locale, you can
> encounter situation when
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: cc
Compilation CFLAGS: -fstack-clash-protection -D_FORTIFY_SOURCE=2
-mtune=generic -O2 -pipe -DSYS_BASHRC='/etc/bash/bashrc' -g
-Wno-parentheses -Wno-format-security uname output: Linux lase
On 2/24/19 3:50 PM, Dominick Grift wrote:
> I noticed that Bash5 requires some additional permissions that I found
> questionable.
>
> Mostly the listing of / and /home
>
> I am wondering whether there is a way to avoid the requirement for above
> permissions.
There is, at least in the most fr
On 2/24/19 9:39 PM, L A Walsh wrote:
> This is oddI wanted to turn on the file+line numbers on the function
> defs...thought it might help the debugger as it gets confused when
> functions are already in memory, but when I did that, now I get
> a weird error on login:
> /usr/share/bashdb/init/r
On 2/24/19 10:01 AM, Lukáš Bařinka wrote:
> Bash Version: 5.0
> Patch Level: 2
> Release Status: release
>
> Description:
> Equivalence class in shell patterns does not work as expected. On the other
> hand, equivalence class does work in regular expressions in bash.
>
> The problem is in shell
On 2/24/19 6:38 AM, Koichi Murase wrote:
>> Bash Version: 5.0
>> Patch Level: 0
>> Release Status: release
>>
>> Description:
>>
>> There are two problems: (1) The keymap `cmd_xmap' used to store the
>> command strings by `bind -x' is shared with all the keymaps. This
>> makes problem when one de
On 2/23/19 6:22 PM, andreas.kah...@abc.se wrote:
> Bash Version: 5.0
> Patch Level: 2
> Release Status: release
>
> Description:
>
> Two tiny spelling mistakes found in the bash manual.
>
> "abd" --> "and"
> "inital"--> "initial"
Thanks for the report.
Chet
--
``The lyf so
13 matches
Mail list logo
