So there are several things.
- "=" is not a legit envvar name: envvar names cannot include a '='
character. "!" is absolutely a legit envvar name, though, and execline
uses it with commands such as background or pipeline.
- execline does not understand single quotes. '!' will translate into
On 9/5/22 22:15, alice wrote:
On Mon Sep 5, 2022 at 10:08 PM CEST, Songbo Wang wrote:
#!/usr/bin/execlineb -P
export ! 0
s6-test -v '\!'
changing this to
s6-test -v \\\!
works as expected.
Thanks for the reply. It indeed works. But there is one thing I find
counter-intuitive: s6-test expe
When the environment modification takes place with export is unintuitive; try
```
#!/usr/bin/execlineb -P
export ! 0
foreground { exit }
s6-test -v '\!'
```
On Mon Sep 5, 2022 at 10:08 PM CEST, Songbo Wang wrote:
> On 9/5/22 20:57, alice wrote
> > s6-test -v '\!'
> > seems to work for me, tested with
> > env !=1 s6-test -v'\!'
> > and without the env. maybe i'm misreading it?
> >
> Your example works for me on bash, but I just tested by the follow
On 9/5/22 20:57, alice wrote
> s6-test -v '\!'
> seems to work for me, tested with
> env !=1 s6-test -v'\!'
> and without the env. maybe i'm misreading it?
>
Your example works for me on bash, but I just tested by the following
execline script
#!/usr/bin/execlineb -P
exec -c s6-test -v !
which
On Mon Sep 5, 2022 at 8:42 PM CEST, Songbo Wang wrote:
> Hi,
>
> I've been recently playing with execline scripts and found out that
> s6-test -v !
s6-test -v '\!'
seems to work for me, tested with
env !=1 s6-test -v'\!'
and without the env. maybe i'm misreading it?
> is not able to test if the !
