On Fri, Jan 20, 2023 at 11:50:52PM +0100, Martin Schulte wrote:
> Hello Nicolas!
>
> > bash-5.1$ echo () { echo test }
> > > echo test
> > > }
> > bash-5.1$ echo
> Most probably you want to insert a ; before the first closing }:
>
> echo() { echo test ; }
>
> But even now bash
Hello Nicolas!
> bash-5.1$ echo () { echo test }
> > echo test
> > }
> bash-5.1$ echo
You have defined a function echo that
- calls itself with the first argument 'test' and the second argument '}' (!!!)
- calls itself with the first and only argument test
Try
type -a echo
and
On Sat, 21 Jan 2023 at 09:24, N R wrote:
> I ran into a segmentation fault running bash --posix. Here are the
> steps to reproduce :
> bash-5.1$ echo () { echo test }
> > echo test
> > }
> bash-5.1$ echo
> Even though I'm not sure what is causing this seg fault, I'm sure
On 1/20/23 2:35 PM, N R wrote:
Bash Version: 5.2
Patch Level: 15
Release Status: release
Description:
I ran into a segmentation fault running bash --posix. Here are the
steps to reproduce :
bash-5.1$ echo () { echo test }
> echo test
> }
bash-5.1$ echo
Even though
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2
uname output: Linux manwelinux 5.15.85-1-MANJARO #1 SMP PREEMPT Wed Dec 21
21:15:06 UTC 2022 x86_64 GNU/Linux
Machine Type: x86_64-pc-linux-gnu
Bash Version:
On 1/19/23 7:08 PM, Peter wrote:
Currently, in the event bash or something below it crashes, that
session's command history is lost.
It would be nice if bash saved it somewhere periodically, it doesn't
have to be too often, let's say on every second command.
Use PROMPT_COMMAND to run `history
