On Sun, Nov 19, 2023 at 10:31:59AM +0700, Robert Elz wrote:
> | $ history -c; fc -0
> | Segmentation fault (core dumped)
> |
> | Can someone else confirm this?
>
> Which bash version are you using?
>
> I just tried that on
> GNU bash, version 5.2.21(1)-release (x86_64--netbsd)
>
Date:Sat, 18 Nov 2023 21:55:23 -0500
From:Jason Franklin
Message-ID:
| $ history -c; fc -0
| Segmentation fault (core dumped)
|
| Can someone else confirm this?
Which bash version are you using?
I just tried that on
GNU bash, version 5.2.21(1)-r
Greetings:
I recall reporting a long time ago that "fc -0" would cause a segfault.
It appears that this behavior remains when the history is cleared prior
to invoking the "fc -0" command...
$ history -c; fc -0
Segmentation fault (core dumped)
Can someone else confirm this?
Best,
--
Jason
Date:Sun, 19 Nov 2023 07:40:00 +1000
From:Martin D Kealey
Message-ID:
| The fact that you don't *want* the output of xclip connected to tr
| (because it makes tr wait for xclip *and all its children* to finish,
| while the shell waits for tr to finish) does no
On Nov 18 2023, Daniel Barrett via Bug reports for the GNU Bourne Again SHell
wrote:
> If it's helpful, here's another interesting piece of the puzzle: the
> "xsel -i" command (which also copies stdin to the X primary selection,
> like "xclip -i" does) works fine in the original pipeline, without
Perhaps some background would help here; I start by highlighting this
section in "man xclip":
-l, -loops
number of X selection requests (pastes into X applications)
to wait for before exiting, with a value of 0 (default) causing xclip to
wait for an unlimited number of reques
On November 18, 2023, Greg Wooledge wrote:
>On Sat, Nov 18, 2023 at 08:36:06AM -0500, dbarrett--- via Bug reports for the
>GNU Bourne Again SHell wrote:
>> echo foo | tee >(xclip -i) | tr o x
>>
>> The command does print "fxx" but then it hangs.
>>
>> The same command behaves correctly when run
On Nov 18 2023, Greg Wooledge wrote:
> On Sat, Nov 18, 2023 at 08:36:06AM -0500, dbarrett--- via Bug reports for the
> GNU Bourne Again SHell wrote:
>> echo foo | tee >(xclip -i) | tr o x
>>
>> The command does print "fxx" but then it hangs.
>>
>> The same command behaves correctly when run in
On Sat, Nov 18, 2023 at 08:36:06AM -0500, dbarrett--- via Bug reports for the
GNU Bourne Again SHell wrote:
> echo foo | tee >(xclip -i) | tr o x
>
> The command does print "fxx" but then it hangs.
>
> The same command behaves correctly when run in zsh.
For the record, here's what processes are
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2
uname output: Linux snorkack 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2
15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Machine Type: x86_64-pc-linux-gnu
Bas
10 matches
Mail list logo
