- I just tried out the new-email setting with the example from the manual: `new-email=exec 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 tried if the `new-message-bell=true/false` affects it somehow, but it didn't.
- But a interesting detail is, that there was no bell sound to hear, neither with `new-message-bell=true` nor `new-message-bell=false`. But there was a signal recieved from the workspace in i3 that something happened.
- 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-fb3c790c5647%40www.fastmail.com>#<CHXOH8OVR7LC.2RI1NALZT2PX3@diabtop>
- 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
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=exec 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=true/false` affects it somehow, but> it didn't.
It does not.
> - But a interesting detail is, that there was no bell sound to hear,> neither with `new-message-bell=true` nor `new-message-bell=false`. 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-fb3c790c5647%40www.fastmail.com>#<CHXOH8OVR7LC.2RI1NALZT2PX3@diabtop>
Might very well be… 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
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=exec echo 12 > /home/areo/email_test
2) new-email=exec "echo 12 > /home/areo/email_test"
3) new-email=exec /usr/bin/echo 12 > /home/areo/email_test
4) new-email=echo 12 > /home/areo/email_test
5) new-email=/usr/bin/echo 12 > /home/areo/email_test
6) new-email=exec "/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 about
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=true/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=exec 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=true/false` affects it somehow, but> > it didn't.>> It does not.>> > - But a interesting detail is, that there was no bell sound to hear,> > neither with `new-message-bell=true` nor `new-message-bell=false`. 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-fb3c790c5647%40www.fastmail.com>#<CHXOH8OVR7LC.2RI1NALZT2PX3@diabtop>>> Might very well be… 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
On Sun May 1, 2022 at 4:40 PM CEST, Areotwister wrote:
> 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:>> […]> But didn't produce a file `email_test` >_<
have you tried sh -c "echo stuff > /tmp/works && touch /tmp/works"
(the second just to be sure)
This should *definitely* not be necessary though.
> > 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=true/false` and `new-mail` actually both triggered, by the> same thing, by the \Recent flag?
On that I am actually not too sure. Maybe someone else can fill in here.
It's been a while since I looked at that part of the code.
> That would imply, by considering Sherlock: "When you have eliminated the> impossible, whatever remains, however improbable, must be the truth."> 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 >_<
Can you check the log in that regard? Not sure if we're logging there,
but might be worth a shot,
> Thank you for taking your time to resolve my confusion with the bell ^_^
No worries!
Oh and regarding the block below this paragraph, please take a look at
https://man.sr.ht/lists.sr.ht/etiquette.md :)
> 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:> > […]
--
Moritz Poldrack
https://moritz.sh
> have you tried sh -c "echo stuff > /tmp/works && touch /tmp/works" (the> second just to be sure) This should *definitely* not be necessary> though.
I tried it out, but no file "/tmp/works" appeared there. Manually
running the command in the commandline works.
> Can you check the log in that regard? Not sure if we're logging there,> but might be worth a shot,
Oki, I checked it ^_^ The log file was quite long. I searched for
"works" and for "new-email" (and some other search words i don't
remember) but they only appeard in the email contents that appeared in
the log.
> Oh and regarding the block below this paragraph, please take a look at> https://man.sr.ht/lists.sr.ht/etiquette.md :)
Oh sry, i somehow overlooked that >_< It's funny like i did both, i
cited and kept the whole discussion history at the bottom xD
It's interesting how i just did that without even questioning the reason
for that. Just did that because so many other Emails I received did that xD
On the other hand, citing is only so easy if one is using Vim or Emacs Q_o
Thanks for the hint, i learned something new n_n
Thank you again for taking your time with my emails ^_^
Areo