Was just playing around seeing how the sigint
being ignored in children acted. wrote short
function: This behavior seems limited to testing
this as a foregnd function, not a shell script.
I.e, sourcing the function, then
execute the function:
lnch
function lnch {
set -o monitor # fy
On 10/14/15 4:08 AM, isabella parakiss wrote:
> What's the point of these two warnings in builtins/complete.def ?
To indicate to users that when you run compgen from the command line
(or complete, for that matter), you don't have the same behavior as
when you're using it from programmable completi
Has anyone successfully compiled and used the set0 and readc builtins
from the bashdb project on non-Linux platforms such as FreeBSD and Hurd?
They fail to load at least in Debian. I have documented the issues as I
have found them at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801665 .
What's the point of these two warnings in builtins/complete.def ?
if (Farg)
builtin_error (_("warning: -F option may not work as you expect"));
if (Carg)
builtin_error (_("warning: -C option may not work as you expect"));
Can they be removed? It's stupid to provide a function, and wa
