Re: /dev/tcp feature request...

2025-04-12 Thread MacBeth
On Wed, Apr 9, 2025 at 8:48 AM A. James Lewis wrote: > > Yes, this is how I am doing it currently, but remember that once you > cut that subshell loose, you cannot easily get a response from it and > certainly can't pass variables back... and you are more or less forced > to wait for a sensible ti

Re: /dev/tcp feature request...

2025-04-08 Thread MacBeth
On Tue, Apr 8, 2025 at 8:54 AM MacBeth wrote: > > On Mon, Apr 7, 2025 at 5:37 PM A. James Lewis wrote: > > > > I have always attempted to avoid > > using external programs where functionality within bash can meet a > > requirement. Doing this allows my script

Re: /dev/tcp feature request...

2025-04-08 Thread MacBeth
On Tue, Apr 8, 2025 at 8:54 AM MacBeth wrote: > > script begin ... sample output being: $ . tcp.sh HTTP/1.0 200 OK Done with: www.google.com HTTP/1.0 200 OK Done with: www.example.com sleeping... waiting on 8.8.8.9 sleeping... waiting on 8.8.8.9 sleeping... waiting on 8.8.8.9 sl

Re: /dev/tcp feature request...

2025-04-08 Thread MacBeth
On Mon, Apr 7, 2025 at 5:37 PM A. James Lewis wrote: > > I have always attempted to avoid > using external programs where functionality within bash can meet a > requirement. Doing this allows my scripts to be more reliable, and not > depend on those external tools being installed... > > I have ho

Re: /dev/tcp feature request...

2025-04-08 Thread MacBeth
On Tue, Apr 8, 2025 at 7:16 AM Zachary Santer wrote: > > Is there a good tutorial on how to actually use /dev/tcp? > I found a number of helpful results on google... https://www.google.com/search?q=%2Fdev%2Ftcp For instance: https://medium.com/@stefanos.kalandaridis/bash-ing-your-network-

Re: Heredoc with a multiline delimiter

2025-03-16 Thread MacBeth
h including in the doc to warn others. Otherwise the user is left to assume bash will do exactly what the doc says it will do, *unconditionally*. On Sun, Mar 16, 2025 at 1:12 AM Robert Elz wrote: > > Date:Sat, 15 Mar 2025 21:54:18 -0500 > From:MacBeth > M

Re: Heredoc with a multiline delimiter

2025-03-15 Thread MacBeth
On Sat, Mar 15, 2025 at 8:18 PM Robert Elz wrote: > > (line joining using \ isn't technically an escape sequence, but that > detail is irrelevant here). > bash(1) claims it to be: There are three quoting mechanisms: the escape character, single quotes, and double quotes. A non-quote

Re: Heredoc with a multiline delimiter

2025-03-15 Thread MacBeth
On Sat, Mar 15, 2025 at 12:33 PM Greg Wooledge wrote: > On Sat, Mar 15, 2025 at 16:14:00 +, Nikola Novak via Bug reports for the > GNU Bourne Again SHell wrote: > > How do you end the heredoc with a multiline delimiter such as the following: > > > > cat << "a > > b" > > You don't. > However

Re: history writes to process substitution but errors reading it

2025-02-14 Thread MacBeth
On Fri, Feb 14, 2025 at 4:31 AM MacBeth wrote: > > Ummm, isn't this supposed to work? I'm guessing there's a technical > reason why it doesn't...? > > # fails: > $ history -r <(echo 'echo bad') > Unless the reason is due to the file seek issu

history writes to process substitution but errors reading it

2025-02-14 Thread MacBeth
Ummm, isn't this supposed to work? I'm guessing there's a technical reason why it doesn't...? # fails: $ history -r <(echo 'echo bad') # succeeds: $ history -w >(cat -n) - $ help | head -n 1 GNU bash, version 5.2.37(1)-release (aarch64-apple-darwin23.4.0) $ echo 'echo good' > hist.txt $ cat

Re: Discussion on wait

2025-01-30 Thread MacBeth
On Thu, Jan 30, 2025 at 2:02 AM Robert Elz wrote: > Date:Thu, 30 Jan 2025 06:03:18 +0300 > From:=?UTF-8?B?T8SfdXo=?= > Message-ID: m3wdtjk0dfztgmfoggt2du...@mail.gmail.com> > > I'd suggest putting it in a function, something like > > wait_for_error() { >

Re: bash compat* issues?

2025-01-22 Thread MacBeth
On Tue, Jan 21, 2025 at 11:25 PM Lawrence Velázquez wrote: > On Tue, Jan 21, 2025, at 9:49 PM, MacBeth wrote: > > "Bash-5.0 is the final version for which there will be an individual > shopt > > option for the previous version. Users should use BASH_COMPAT on bash-5.0

bash compat* issues?

2025-01-21 Thread MacBeth
re: GNU bash, version 5.2.37(1)-release (aarch64-apple-darwin23.4.0) --- 1) `shopt compat50` does not exist. The manpage does specify that 'compat50' is a valid option for `shopt` under BUILTINS/shopt. Yet bash provides an error when trying to read or change it: > shopt compat50 bash: shopt: com

Re: 'read' sometimes truncates trailing field delimiter

2025-01-12 Thread MacBeth
On Sun, Jan 12, 2025 at 8:58 AM MacBeth wrote: > On Sun, Jan 12, 2025 at 8:24 AM Félix Hauri wrote: > >> Le Sat, Jan 11, 2025 at 10:49:50AM -0500, Greg Wooledge a écrit : >> > https://mywiki.wooledge.org/BashPitfalls#pf47 >> > "It's a feature." &g

Re: 'read' sometimes truncates trailing field delimiter

2025-01-12 Thread MacBeth
On Sun, Jan 12, 2025 at 8:24 AM Félix Hauri wrote: > Le Sat, Jan 11, 2025 at 10:49:50AM -0500, Greg Wooledge a écrit : > > https://mywiki.wooledge.org/BashPitfalls#pf47 > > "It's a feature." > > > -- how do we work around this nonsense? > > I've alredy noticed this, but never stictly tested them

'read' sometimes truncates trailing field delimiter

2025-01-11 Thread MacBeth
Configuration Information [Automatically generated, do not change]: Machine: aarch64 OS: darwin23.4.0 Compiler: clang Compilation CFLAGS: -DSSH_SOURCE_BASHRC -DDEFAULT_LOADABLE_BUILTINS_PATH='/opt/homebrew/Cellar/bash/5.2.37/lib/bash:/usr/local/lib/bash:/usr/lib/$ Machine Type: aarch64-apple-darwin