Re: Another issue on OpenBSD

Sorry, I needed more coffee before I asked this. Newbie. Please ignore.

Re: Another issue on OpenBSD

I am also wondering if it would be possible to set signal traps for the script itself calling the trap program, rather than for a program following the trap block (like in the regular shells)? Thanks again.

Re: Another issue on OpenBSD

Works! Thanks!

Re: Another issue on OpenBSD

Now getting trap: fatal: unable to auto-trap signal 32: Invalid argument Thank you.

Another issue on OpenBSD

Hello, I am getting the following error when trying to use trap with -x: #!/usr/local/bin/execlineb -W define VAR THISISAVAR trap -x { SIGQUIT { importas VAR VAR foreground { echo $VAR } } SIGTERM { importas VAR VAR foreground { echo $VAR } } SIGINT{ importas VAR

Re: multidefine segfault

Thanks Laurent! Out of curiousity, what kind of bug was it in terms of what was happening to the memory? Also, in the above example, I would like to feed a three word input (string or line in regular terminology?) to the first multidefine, and extract the two of the words out of $msg with the

Re: multidefine segfault

'multidefine' segfaults on a recent OpenBSD snapshot: The execline script like : #!/usr/local/bin/execlineb -W withstdinas line importas -u line line multidefine -r $line { cmd msg } multidefine -r $msg { key val } $ echo ' test ' | ./testmult Segmentation fault (core dumped) It's the

Re: multidefine failing for some reason

I am not sure if I am doing anything wrong in the above execlineb syntax-wise, or there's a bug. At some point multidefine segfaulted (I think I fed the execline script a single newline from stdin or something similar), but I forget now exactly what I did to make it segfault. Will try again, and

multidefine failing for some reason

Greetings, I am trying to run the following script: #!/usr/local/bin/execlineb -W withstdinas line importas -u line line multidefine -r $line { cmd msg } multidefine -d"," $msg { key val } and I get a fatal error, but I don't understand why: $ echo 'command test,test test' |

Re: execline: Segfault with the define program

Works now. Good designs are often quirky. DJB-like software is often considered quirky or even hated as well... execline is awesome! OpenBSD is awesome! Thank you!

Re: execline: Segfault with the define program

on explaining the motivation behind this that I found in the archives: https://marc.info/?l=openbsd-misc=148762033002663=2 On Wed, Apr 5, 2017 at 11:49 AM, fff iii <fr3akyid...@gmail.com> wrote: > On Wed, Apr 5, 2017 at 4:08 AM, Laurent Bercot <ska-skaw...@skarnet.org> > wrot

Re: execline: Segfault with the define program

On Wed, Apr 5, 2017 at 4:08 AM, Laurent Bercot wrote: >> define TESTING \#testing >> define TESTING2 /test1/test2/test3/test4/\\${TESTING}/test6 > > > Works for me. > > Please make sure you're running the latest version of execline, built > against the latest version of

execline: Segfault with the define program

Hello, I am sure I am doing something I am not supposed to, and getting a segfault with the 'define' program. How to reproduce: define TESTING \#testing define TESTING2 /test1/test2/test3/test4/\\${TESTING}/test6 Thanks!