Command name dequote does not work

2014-04-15 Thread ingo . krabbe
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKA

Re: Command name dequote does not work

2014-04-15 Thread Dan Douglas
Not sure we have enough info here. Have you tried "set -x" to see what's really going on? Have you also confirmed that it isn't actually calling your script and the script simply isn't functioning as expected? -- Dan Douglas

Re: Command name dequote does not work

2014-04-15 Thread Pierre Gaston
On Tue, Apr 15, 2014 at 10:32 AM, wrote: > Configuration Information [Automatically generated, do not change]: > Machine: x86_64 > OS: linux-gnu > Compiler: gcc > Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' > -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' > -DC

Re: Command name dequote does not work

2014-04-15 Thread Chet Ramey
On 4/15/14, 3:32 AM, ingo.kra...@eoa.de wrote: > Bash Version: 4.2 > Patch Level: 37 > Release Status: release > > Description: > I wrote a simple shell script using sed to convert \n into newlines and > other \\(.) to \\\1 and called that script dequote. > When I'm trying to call it nothi

Re: Command name dequote does not work

2014-04-15 Thread Ralf Goertz
Chet Ramey wrote: > On 4/15/14, 3:32 AM, ingo.kra...@eoa.de wrote: > >> Bash Version: 4.2 >> Patch Level: 37 >> Release Status: release >> >> Description: >> I wrote a simple shell script using sed to convert \n into newlines and >> other \\(.) to \\\1 and >> called that script dequote. When I'

Re: Command name dequote does not work

2014-04-15 Thread Dan Douglas
On Tuesday, April 15, 2014 05:46:07 PM Ralf Goertz wrote: > I am not the OP but on OpenSuse 13.1 I have > > $ type dequote > dequote is a function > dequote () > { > eval printf %s "$1" 2> /dev/null > } If you're already aware, for the benefit of others, that's a very dangerous func

Re: Command name dequote does not work

2014-04-15 Thread ingo . krabbe
I finally found it. I forgot to check the function names. It's a function of bash-completion, though I don't think that such a function name should be exported. --- Begin Message --- Not sure we have enough info here. Have you tried "set -x" to see what's really going on? Have you also confirmed

Re: Command name dequote does not work

2014-04-15 Thread Eduardo A . Bustamante López
On Tue, Apr 15, 2014 at 03:53:42PM +0200, ingo.kra...@eoa.de wrote: > I finally found it. I forgot to check the function names. It's a function of > bash-completion, though I don't think that such a function name should be > exported. bash-completion is a package apart from bash. So, you should r

Re: Issue when using job control and SIGCHLD with bash 4.3 (trap is not being run)

2014-04-15 Thread Chet Ramey
On 4/14/14, 4:25 PM, Eduardo A. Bustamante López wrote: > Hi, > > I was playing with set -m and trapping CHLD in a script, and found > the following error: Here's a patch. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocra

Re: bind -x and multiple prompt/command lines

2014-04-15 Thread Jesper Nygårds
I don't have any solution to offer, but I would like to second the wish for this to work better, and for the same reason: I have written several very useful functions for rewriting the command line, binding them with bind -x. Like Rob, I have concluded that it does not work well with a multi-line p

Re: Issue when using job control and SIGCHLD with bash 4.3 (trap is not being run)

2014-04-15 Thread Eduardo A . Bustamante López
On Tue, Apr 15, 2014 at 04:26:50PM -0400, Chet Ramey wrote: > Here's a patch. > > Chet Hi Chet, I compiled bash from the latest devel branch and I confirm that the issue is gone: dualbus@debian ~/local/src/bash % ~/bash/bin/bash bad x x x x x Thanks!