Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8
Date: Sun, 01 May 2022 16:40:08 +0200
Message-Id: <CJOI48T9B0F8.24BRRSPS8XW38@ArchPC>
Subject: Re: new-email setting not working with example
From: "Areotwister" <areotwister@gmail.com>
To: "Moritz Poldrack" <moritz@poldrack.dev>,
 <~rjarry/aerc-discuss@lists.sr.ht>
Cc: 
References: <CJOG1LC2HZQA.2AD0VLH0GVLAY@ArchPC>
 <CJOG58NM9MNI.1SX7IP63B951B@Archetype>
In-Reply-To: <CJOG58NM9MNI.1SX7IP63B951B@Archetype>

Thanks for your reply ^_^

> I had to prefix it with an exec for it to work, but my setup might be
> considered odd.

Ok, i've know tried out quite a few things:

```bash
1) new-email=3Dexec echo 12 > /home/areo/email_test
2) new-email=3Dexec "echo 12 > /home/areo/email_test"
3) new-email=3Dexec /usr/bin/echo 12 > /home/areo/email_test
4) new-email=3Decho 12 > /home/areo/email_test
5) new-email=3D/usr/bin/echo 12 > /home/areo/email_test
6) new-email=3Dexec "/usr/bin/echo 12 > /home/areo/email_test"
```
But didn't produce a file `email_test` >_<

> Bell means the terminal bell \a

Oh, and i was actually rly so naive to think there would be an actual bell =
sound xD
Cool, that's a rly nice trick with `sleep 10; echo -e "\a"`, didn't knew ab=
out
that before, thx ^_^

> I'm afraid I don't quite understand what you mean. Could you elaborate?
I previously misunderstood that the bell was actually working. Are the
`new-message-bell=3Dtrue/false` and `new-mail` actually both triggered, by =
the
same thing, by the \Recent flag?
That would imply, by considering Sherlock: "When you have eliminated the
impossible, whatever remains, however improbable, must be the truth." that =
it
actually got triggered, but the command just didn't execute correctly Q_o
And that's also the point where I'm out of ideas why the command doesn't
execute correctly >_<

Thank you for taking your time to resolve my confusion with the bell ^_^

Have a nice day and thanks again :D

Areo

On Sun May 1, 2022 at 3:07 PM CEST, Moritz Poldrack wrote:
> On Sun May 1, 2022 at 3:02 PM CEST, Areotwister wrote:
> > - I just tried out the new-email setting with the example from the
> > manual: `new-email=3Dexec notify-send "New email from %n" "%s"`, but no
> > message showed up in https://github.com/dunst-project/dunst. But the
> > command `notify-send "New email from %n" "%s"` executed  from the
> > commandline works. The folder that received the email within aerc, was
> > selected.
>
> I had to prefix it with an exec for it to work, but my setup might be
> considered odd.
>
> > - I tried if the `new-message-bell=3Dtrue/false` affects it somehow, bu=
t
> > it didn't.
>
> It does not.
>
> > - But a interesting detail is, that there was no bell sound to hear,
> > neither with `new-message-bell=3Dtrue` nor `new-message-bell=3Dfalse`. =
But
> > there was a signal recieved from the workspace in i3 that something
> > happened.
>
> Bell means the terminal bell \a
>
> > - The reason could propably be that Gmail isn't writing the \Recent
> > flag as Robin mentioned in one of his answers:
> > https://lists.sr.ht/~rjarry/aerc-devel/<fcd88f4e-cad1-4b99-801b-fb3c790=
c5647%40www.fastmail.com>#<CHXOH8OVR7LC.2RI1NALZT2PX3@diabtop>
>
> Might very well be=E2=80=A6 Gmail seems to have some trouble with this
> "following established standards"-thing
>
> > - It would be nice to maybe have a trigger not dependand on this flag,
> > but that just triggers if a message is received, because it's a rly
> > usefull feature to just zap through the messages in dunst to get the
> > info if new emails were received
>
> I'm afraid I don't quite understand what you mean. Could you elaborate?
>
> --
> Moritz Poldrack
> https://moritz.sh