Date:Tue, 28 Nov 2023 19:27:17 -0500
From:=?UTF-8?Q?Lawrence_Vel=C3=A1zquez?=
Message-ID:
| the first argument after the command string (in my case "a", and
| in your case "-bash") is used as $0 while executing that command
| string, and the remaining
On Wednesday, November 29, 2023, Klaus Frank wrote:
> One thing though, I probably should already know that, but why is a $0
> needed even though a command was already specified? Shouldn't the command
> itself be $0?
No, $0 is used in error messages:
$ bash -c '"' foo
foo: -c: line
On Wed, Nov 29, 2023 at 12:37:55AM +, Klaus Frank wrote:
> One thing though, I probably should already know that, but why is a $0
> needed even though a command was already specified? Shouldn't the command
> itself be $0?
It's simply how sh -c has always worked. The first argument after -c
Hi,
thanks for the explanation. Esp. the parsing one at the bottom, that
explains why my tests were false positive.
One thing though, I probably should already know that, but why is a $0
needed even though a command was already specified? Shouldn't the
command itself be $0?
On
On Tue, Nov 28, 2023, at 5:33 PM, Klaus Frank wrote:
> sorry, but this is not true
It is true.
> I can clearly see that it exists. It may be
> an distro addition though. Is it specific to ArchLinux? Because I can
> see it being used and when I try to use it on my system it also clearly
>
On Tue, Nov 28, 2023 at 10:33:20PM +, Klaus Frank wrote:
> sorry, but this is not true, I can clearly see that it exists. It may be an
> distro addition though. Is it specific to ArchLinux?
Here's what I get on Debian:
unicorn:~$ bash -bash_input foobar -c 'read; declare -p REPLY'
bash: -_:
Hi,
sorry, but this is not true, I can clearly see that it exists. It may be
an distro addition though. Is it specific to ArchLinux? Because I can
see it being used and when I try to use it on my system it also clearly
works. But against it just being a distro specific thing is that I also
On 11/28/23 11:16 AM, ra...@c.mail.sonic.net wrote:
Bash crashes with a segfault, unless the variable LC_CTYPE or LC_ALL
are set to a valid value (I have tried C, C.UTF-8, and en_US.UTF-8),
before any "other" commands are executed.
This was fixed by patch 2 to
On 11/28/23 1:14 AM, Grisha Levit wrote:
If a funsub declares a local OPTIND, the calling context's getopts state
gets messed up.
Thanks for the reports and patches.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Configuration Information [Manually overridden, the bug happened a while ago]:
Machine: i386 (32-bit), also occurs on amd64 (64 bit)
OS: freebsd12.3-RELEASE-p6
Compiler: cc
Compilation CFLAGS: unknown, from a pre-built FreeBSD package
uname output: FreeBSD house.lr.los-gatos.ca.us 12.3-RELEASE-p6
On Nov 28 2023, Klaus Frank wrote:
> I just noticed that the man pages are missing documentation for the
> "-bash" (or better "-bash_input") parameter.
There is no such thing as a -bash or -bash_input parameter.
> be better readable when being passed as an argument itself to e.g. nspawn
> or
Hi,
I just noticed that the man pages are missing documentation for the
"-bash" (or better "-bash_input") parameter.
I just found the "-bash" parameter in a script and couldn't find any
documentation about it, after checking out the source code I found
"-bash_input" which after some testing
12 matches
Mail list logo
