On 30 Oct 2020, at 14:41, Bernd Petrovitsch wrote:
> Perhaps try the script beforehand in a terminal:
I have. And I use | as delimiters all the time.
> snip
> {2}sed -e '|x|y|'
> sed: -e expression #1, char 1: unknown command: `|'
> snip
> So no, it's not.
Yes it is. As
On Fri, 2020-10-30 at 12:21 -0600, @lbutlr wrote:
> On 30 Oct 2020, at 11:25, Bernd Petrovitsch wrote:
> > On 30/10/2020 17:11, @lbutlr wrote:
> > [...]
> > > echo $1 | sed -e '||* {color:white !important;
> > > background-color: black !important; } |'
> >
> > What should the sed stuff do?
>
>
On Fri, 2020-10-30 at 19:57 +0200, Aki Tuomi wrote:
> > On 30/10/2020 19:25 Bernd Petrovitsch wrote:
> >
> >
> > On 30/10/2020 17:11, @lbutlr wrote:
> > [...]
> > > echo $1 | sed -e '||* {color:white !important;
> > > background-color: black !important; } |'
> >
> > What should the sed stuff
> "@lbutlr" == @lbutlr writes:
@lbutlr> On 30 Oct 2020, at 12:34, @lbutlr wrote:
>> I am not sure about the $1. I think filter just pipes the message (or part
>> of the message.
>>
>> I will see what happens without the echo I suppose.
>>
>> Nope, still the same.
>>
>> 32: starting
On 30 Oct 2020, at 12:34, @lbutlr wrote:
> I am not sure about the $1. I think filter just pipes the message (or part of
> the message.
>
> I will see what happens without the echo I suppose.
>
> Nope, still the same.
>
> 32: starting `:contains' match with `i;ascii-casemap' comparator:
>
> On 30/10/2020 20:34 @lbutlr wrote:
>
>
> On 30 Oct 2020, at 11:57, Aki Tuomi wrote:
> > But I think the sed here is missing 's' from start, so this does not
> > actually do anything...
>
> Copy/paste/edit error. The s is there in the file.
>
> darkmode.sh:
> #!/bin/sh
> echo $1 | sed
On Freitag, 30. Oktober 2020 18:11:46 CET @lbutlr wrote:
> echo $1 | sed -e '||* {color:white !important;
> background-color: black !important; } |'
echo $1 | sed -e 's||.* {color:white !important; background-
color: black !important; } |'
Perhaps?
On Fri, Oct 30, 2020 at 11:34 AM @lbutlr wrote:
> On 30 Oct 2020, at 11:57, Aki Tuomi wrote:
> > But I think the sed here is missing 's' from start, so this does not
> actually do anything...
>
> Copy/paste/edit error. The s is there in the file.
>
> darkmode.sh:
> #!/bin/sh
> echo $1 | sed -e
On 30 Oct 2020, at 11:57, Aki Tuomi wrote:
> But I think the sed here is missing 's' from start, so this does not actually
> do anything...
Copy/paste/edit error. The s is there in the file.
darkmode.sh:
#!/bin/sh
echo $1 | sed -e 's||* {color:white !important; background-color:
black
On 30 Oct 2020, at 11:25, Bernd Petrovitsch wrote:
> On 30/10/2020 17:11, @lbutlr wrote:
> [...]
>> echo $1 | sed -e '||* {color:white !important;
>> background-color: black !important; } |'
>
> What should the sed stuff do?
Changes to * {color:white !important; background-color: black
On 30 Oct 2020, at 11:26, PGNet Dev wrote:
> wrong, or different, I can't say. if helpful, for my script executions, I
> successfully do
>
> require ["vnd.dovecot.pipe", "vnd.dovecot.filter",
> "vnd.dovecot.execute", "copy", "environment", "variables",
> "vnd.dovecot.debug",
On Fri, 30 Oct 2020 at 20:12, @lbutlr wrote:
> So, I have the sieve working up to the point that it calls the script, and
> the script is called (I get different errors if the script is not there,
> for example).
>
> filter action
> execute program `darkmode.sh'
> [[EXECUTION ABORTED]]
>
>
> On 30/10/2020 19:25 Bernd Petrovitsch wrote:
>
>
> On 30/10/2020 17:11, @lbutlr wrote:
> [...]
> > echo $1 | sed -e '||* {color:white !important;
> > background-color: black !important; } |'
>
> What should the sed stuff do?
> TTBOMK '|' is not known by sed ...
>
> MfG,
> Bernd
On 10/30/20 10:11 AM, @lbutlr wrote:
So, I have the sieve working up to the point that it calls the script, and the
script is called (I get different errors if the script is not there, for
example).
filter action
execute program `darkmode.sh'
[[EXECUTION ABORTED]]
On 30/10/2020 17:11, @lbutlr wrote:
[...]
> echo $1 | sed -e '||* {color:white !important;
> background-color: black !important; } |'
What should the sed stuff do?
TTBOMK '|' is not known by sed ...
MfG,
Bernd
--
There is no cloud, just other people computers.
--
So, I have the sieve working up to the point that it calls the script, and the
script is called (I get different errors if the script is not there, for
example).
filter action
execute program `darkmode.sh'
[[EXECUTION ABORTED]]
There's no other error logged (for example, when I had
16 matches
Mail list logo
