'mapfile -O1 array' breaks '[[ -v array ]]'

2023-04-17 Thread Wiley Young
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-g> uname output: Linux localhost-live 6.0.7-301.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC> Machine Type: x86_64-redh

With DEBUG trap, resizing window crashes script

2023-05-10 Thread Wiley Young
From: liveuser To: bug-bash@gnu.org Subject: With DEBUG trap, resizing window crashes script Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -

Error message: cannot find _struct in shared object

2023-05-27 Thread Wiley Young
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASS

Segfault, 29 May '23

2023-05-29 Thread Wiley Young
Hi, While trying to capture line numbers in an array to print with the rest of the shell's debugging info, a segfault .. Wiley [liveuser@localhost-live]$ bash ... $ set -x + set -x $ echo $SHLVL + echo 2 2 $ declare -n n=BASH_SOURCE; declare -n e=LINENO; shopt -s expand_aliases + d

double free SIGSEGV and SELinux AVC denial

2023-06-03 Thread Wiley Young
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASS

double free SIGSEGV and SELinux AVC denial

2023-06-03 Thread Wiley Young
Attachments: SELinux is preventing false from read access on the fifo_file fifo_file. * Plugin catchall (100. confidence) suggests ** If you believe that false should be allowed read access on the fifo_file fifo_file by default. Then you should report this as a bug.

`verb=(--) declare -ax verb` causes an ENOTSOCK segfault

2023-06-15 Thread Wiley Young
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASS

xmalloc error involving functrace, int trap and ps4

2023-06-24 Thread Wiley Young
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASS

Stdout from arg group of Debug trap redefines PS4

2023-06-25 Thread Wiley Young
Hi, [liveuser@localhost-live scf]$ reset; ./findscan rm_stale foo bar -ab /tmp |& cat -n Beginning at line 217 of `cat`s numbering of this xtrace output log, the read prompt from the Debug trap prints some info for a few lines, and then one line before #218, the PS4 prompt is displayed again, if

Re: Help fixing NativeMessaging host: read 32-bit message

2023-06-27 Thread Wiley Young
> It is politics. All human activity is political in nature. Writing for portability is about building a widget that will appeal to a larger group of customers. Thanks for your thoughts. Wiley

'${#@}' expands to an integer

2023-07-05 Thread Wiley Young
Here's some code as observed "in the wild:" `[[ ${#@} -ne 0 ]] && ...` Perhaps the parser is reading this as an incomplete parameter transformation? It seems from context that the original intent was simply... `[[ $# -ne 0 ]] && ...` As it happens, the effect appears to be the same either w

git amend commit with backticks on cli causes tty to crash

2023-07-20 Thread Wiley Young
Hi, I'm seeing this behavior on Fedora 38. Possibly it's just some user error again, since i'm figuring out how to use vim and git at a slightly above novice level. :-) #+++ $ uname -a Linux localhost-live 6.3.7-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Jun 9 15:21:11 U

A few suggestions for the GNU Manual

2023-07-31 Thread Wiley Young
Hi, Regarding the "Invoking Bash" page, https://www.gnu.org/software/bash/manual/html_node/Invoking-Bash.html It might be more consistent and therefore perhaps more clear for all of the newbies out there if the description of "--restricted" also began with "Equivalent to -r," as the very next des

Assignment to RO variable

2023-08-15 Thread Wiley Young
So this behavior of `bash`s seems like a bug to me. I stumbled across it by accident. >From within a stack of x3 functions called from a case within a for loop, when trying to assign a value to a read-only variable, `printf` and `read` both fail with exit codes of 1, and the functions, `case` and

Re: [bug #66460] A documentation correction regarding an array nameref???

2024-11-20 Thread Wiley Young
"The nameref attribute cannot be applied to array variables." Some thoughts on English language Perhaps "attribute" could be more explicitly defined? ...as something like, 'a characteristic [ given to | assigned to | applied to | associated with | defining a ] parameter (or a parameter's util

Re: bug-bash Digest, Vol 264, Issue 31

2024-11-16 Thread Wiley Young
digest..." > > > Today's Topics: > >1. redirection / process substitution fails to read a file > descriptor (Mike Peters) >2. Re: redirection / process substitution fails to read a file > descriptor (Greg Wooledge) >3. Re: bug-bash Digest,

Re: bug-bash Digest, Vol 264, Issue 28

2024-11-16 Thread Wiley Young
| From: Martin D Kealey | "In the general case I agree; man | pages should be reference | manuals, not tutorials" We should value others' contributions. Most people, when they read something that they don't yet understand, if they wish to understand it, will seek out a more accessible

Re: String substitution bug

2024-11-26 Thread Wiley Young
Writing's more difficult than reading, and writing can be expensive. Synoptic reading, traditionally, is considered the "highest form" of reading (according to "How to Read a Book") (Hate mail to them, please, not me.). Writing from some definable point of view is inevitable. It might be worthwhi

Re: SHELLOPTS environment variable causes shell options to cascade

2025-01-06 Thread Wiley Young
On Jan 05 2025, Tobi Laskowski wrote: > "It may be safe, however, it is a bit tedious... Wow. I remember once I corrected an obvious flaw in a major project's CICD bash scripts involving quoting and the trap builtin. You'd have thought I'd have tried to chop somebody's fingers off. Wiley

Patch on shellmath.sh from bash-doc v.5.2.32, r.1.fc41

2025-02-04 Thread Wiley Young
Hi, Please say something if this patch should be sent someplace else. Shellmath's "runTests.sh" script returned x8 failing tests. This patch addresses all eight errors as well as shellcheck's various complaints. The full test suite now passes. These specific changes have been addressed: * doc/

An inconsistency of the outputs of help builtin

2024-12-20 Thread Wiley Young
Testing how bash's help builtin responds to each character. For some reason, while `help -d 'c'` prints the same thing as `help -c 'c*'` (note the asterisk), the same is not true when the character is left-bracket: `help -c '[*'. This issue persists on bash 5.3 beta. # Input: [liveuser@fedora ~]

Re: bug-bash Digest, Vol 265, Issue 40

2024-12-22 Thread Wiley Young
On Fri, 20 Dec 2024 08:09:40 -0500, Greg Wooledge wrote: > Assuming you meant -d not -c: Good eye. > Why did you expect them to be the same? A surprisingly hard question. Um, well, this report was from something I noticed a few months ago. As I recall, `help -d '('` returns information about

Re: SHELLOPTS environment variable causes shell options to cascade

2025-01-09 Thread Wiley Young
On Wed, 8 Jan 2025 08:44:06 +1000, Martin D Kealey wrote: > I invite anyone to provide an example of how If the documentation changes at all, I think just a "See also..." might be enough. Wuley

Re: Suggestion of wording for portion of man page

2025-01-18 Thread Wiley Young
On Sat, Jan 18, 2025 at 9:00 AM Greg Wooledge wrote: > So, if a sentence is ambiguous, then your assertion that it "can't not be read that way" must be false. I'm sorry you didn't get it on the first read through, Greg. Just think of how those professionals felt when they spun their wheels for ho

Re: Suggestion of wording for portion of man page

2025-01-18 Thread Wiley Young
"I would have preferred short papers that were a pleasure to read. However, as Peter Medawar (1979) truthfully has said, “Most scientists do not know how to write.” - Per Brinch Hansen, "Evolution of Operating Systems," 200, pg.2 http://brinch-hansen.net/papers/2001b.pdf "The basic goal was to pro

Re: Suggestion of wording for portion of man page

2025-01-18 Thread Wiley Young
Delving into the free Writing 101 lessons here On Sat, Jan 18, 2025 at 4:16 AM Lawrence Velázquez wrote: > " I find Wiley's main thesis -- that this sentence reads as a sort of topic sentence that implicitly prefixes "alphabetic" to every subsequent use of "character" -- to be pretty contrive

Re: Suggestion of wording for portion of man page

2025-01-16 Thread Wiley Young
hu, Jan 16, 2025 at 7:24 PM Lawrence Velázquez wrote: > On Thu, Jan 16, 2025, at 8:05 PM, Wiley Young wrote: > > In Parameter Expansions / Case Modification: > > > > [S1] > > The first sentence reads, "alphabetic characters," which can imply that > > whe

Suggestion of wording for portion of man page

2025-01-16 Thread Wiley Young
In Parameter Expansions / Case Modification: [S1] The first sentence reads, "alphabetic characters," which can imply that wherever else in the paragraph the word "characters" is used, that the intended meaning is "alphabetic characters," which is not the case. It can be read as something like a

Re: Suggestion of wording for portion of man page

2025-02-17 Thread Wiley Young
On Sat, 18 Jan 2025, Lawrence Velázquez wrote: > Ironic that someone who's spilled so much text about the importance of clear communication is now blaming a reader for misunderstanding an unclear sentence. > Exactly. Thanks for catching that. Wiley