Authentication-Results: mail-b.sr.ht; dkim=fail header.d=poldrack.dev header.i=@poldrack.dev Received: from mail.moritz.sh (mail.moritz.sh [202.61.225.209]) by mail-b.sr.ht (Postfix) with ESMTPS id 2220011EEFB for <~rjarry/aerc-discuss@lists.sr.ht>; Sun, 1 May 2022 13:07:30 +0000 (UTC) X-Virus-Scanned: Yes Mime-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=poldrack.dev; s=mail; t=1651410356; bh=WaLqXgJ7d4LUSySsnyw2G6RLO88Uoz6V2/IhMgGdb80=; h=Cc:From:To:Subject:References:In-Reply-To; b=WG2/ZAv4Xut74RD14Vd4wVKUR0NVHiJSUrb1TJLNnprIUHVYDAuzJ6DSUn4iAWYWE fQaRarbuvJoqwZ5VL4kDidOFkZxz85vG9Ur2EpsgKQNWuqzwdIWf38nB4aG0orTOGL AzQgSg5ZtXVVM84dEaBOUeGtJwmtJXSdeTF08TeBN1xDQQdMTsMTXD1F4fIkRJxPam j+tTZ0XjDLf5JFeMWaSA4J6f3Lrx8YAs5mY1I+Vnu4GzvTkxXleIr52keOMpZKR6Va NaAzlD9cJe5JLLehnGViSZRYHxxv9VpO33/kwagfmBHfklMx3hbM9avYTstVGeXRre qB/uL6mQeF8mrslDe0ihuUK4tGt/dJLa+svPsVDoajoTiODbVF4+2ComlXU21xxJYj CfGV6WT7PgfGcinHCWs2csU8oKpL2LcuYmWLh68IXBwj45L0pgR4zO8ZlFweGTc6fR IAg3NPrV7oMRPPRDHN8+6K6Bp+JYNPcDLE8oedscfA3CmH8Yp+YCLAJ+WO/yGdzFt2 WFhWxKHpcVL8RPtDzQgnqtyPZBWEQlXzkZI/prMxNINcVn5fUgdbyBO6OmW5iHauv9 uZ9pPyyJaXhri1w6MYrGij3rUvZjGS42jzTbcZ2GZuUwt5g6ZivcEg/ZhCoHzqWnd8 zvF6zIiYr2ylMPXlJb340Wt4= Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Sun, 01 May 2022 15:07:23 +0200 Message-Id: Cc: From: "Moritz Poldrack" To: "Areotwister" , <~rjarry/aerc-discuss@lists.sr.ht> Subject: Re: new-email setting not working with example References: In-Reply-To: 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, 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=3Dtrue` nor `new-message-bell=3Dfalse`. Bu= t > 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/# 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