On Wed Jun 04, 2025 at 22:24, bptato <bptato@chawan.net> wrote:
> On Tue, Jun 03, 2025 at 10:55:59PM +0200, Jan Černohorský wrote:
>> [...]
>> > "If img2sixel(1) is isnstalled and your terminal emulator supports
>> > displaying images using the sixel protocol, use the builtin html-unsafe
>> > filter (to allow external URLs to be loaded) in interactive mode with
>> > explicit sixel inline images enabled"
>> 
>> This is all true for images that are linked externally.
>> 
>> The problem arises however, when we try to open an email with those
>> `cid:...` links. As the html viewer receives ONLY the HTML part of the email
>> and no other attachments, it has no way of getting to those images that are

2025. jún. 3. 11:49:04 Sebastien Binet <s@sbinet.org>:

> hi there,
>
> since ~a week now, one of my accounts (Office365, IMAPS) displays the 
> error above when syncing the local maildir (with mbsync).
>
> I don't when (nor with which exact revision) this appeared exactly, but 
> this morning this was still happening (even after removing the folder 
> that was complaining, and the Inbox, refetching everything anew) and I 
> was using 3023b3a4.
>
> Since ~11h00, I have reverted to 2ecb8770 (ie: release 0.20.1), and it 
> didn't happen so far.

On Tue May 27, 2025 at 12:19, Andrea Pappacoda <tachi@debian.org> wrote:
> Hi,
>
> On Tue May 27, 2025 at 10:47 AM CEST, Bence Ferdinandy wrote:
>> In case of imap, aerc itself as you know does not have mechanism for 
>> getting the initial token, but how I've been using aerc with imap is 
>> to use oama to fetch the token and then inject that into aerc. 
>> Once-ish. I can't find the oneliner now though that Koni Marti came up 
>> with. I'm not sure where I lost it ... And I think oama since then 
>> added a better way to retrieve the refresh token.
>
> I'm interested in this one liner :)
> If you can find it, let me know!

On Thu May 22, 2025 at 11:07, Andrea Pappacoda <tachi@debian.org> wrote:
>
> Never heard of oama (if it was mentioned already on the list, I'm sorry, 
> I might have missed some messages). But aerc has its own token handling 
> mechanism, so what would such an app do? A refresh token typically has 
> to be generated only once (unless the account password is changed).

In case of imap, aerc itself as you know does not have mechanism for getting
the initial token, but how I've been using aerc with imap is to use oama to
fetch the token and then inject that into aerc. Once-ish. I can't find the
oneliner now though that Koni Marti came up with. I'm not sure where I lost it
... And I think oama since then added a better way to retrieve the refresh
token.

On Wed May 21, 2025 at 15:53, Andrea Pappacoda <tachi@debian.org> wrote:
> Hi!
>
> I was thinking about adding a pair of client_id and client_secret for 
> aerc to be used when logging into Gmail.
>
> This way, each Gmail user no longer has to register an application on 
> the Google Cloud Console just to login into aerc.
>
> Yes, App Passwords are sometimes an alternative, but they don't work 
> with all accounts (accounts enrolled in the Advanced Protection 
> Programme, some institutional accounts, etc.)
>

On Tue May 20, 2025 at 17:11, Simon Martin <simon@nasilyan.com> wrote:
> Navigating through the folder list can be very tedious if one has many
> folders. This patch addresses this usability limitation by introducing a
> new command with two modes:
>   - ":go-to-folder -i" (with a default binding to C-g) opens a dialog
>     where the user can select the target folder in a case insensitive
>     manner, and navigate to it.
>   - ":go-to-folder <name>" navigates to the only folder case
>     insensitively matching <name>, or shows an error if there are 0 or
>     several matches.
>
> This also improves ListBox to automatically select the first matching
> item, to remove one key-stroke to select the matching item when there's

On Sat May 03, 2025 at 02:14, Moritz Poldrack <git@moritz.sh> wrote:
> To make aerc more extensible, it would be useful to have custom commands
> that allow more complex scripting to happen. This could likely be
> expanded to allow for various use-cases like reporting spam, printing,
> or translating mails.
>
> Signed-off-by: Moritz Poldrack <git@moritz.sh>
> ---

GREAT NEWS that someone started to work on this, thanks Moritz!

>
> TODO: fill message text, write docs.

On Fri Apr 04, 2025 at 07:58, Piotr Dabrowski <Piotr.Dabrowski@posteo.de> wrote:
> Hello everyone,
>
> I am using scripts to create some typical mails that I need to write on a
> regular basis. The scripts are in the form:
>
> aerc mailto:bla@blub.com?subject="Something"\&account=myaccount\&body="stuff"
>
> This used to work. Unfortunately, since I updated to aerc 0.20.1, the signature
> of the account "myaccount" appears at the top of the message, not underneath the
> body as it should.
>
> I tried moving the account to the back of the command, and it does not change

On Sun Mar 30, 2025 at 22:58, Robin Jarry <robin@jarry.cc> wrote:
> There is absolutely no point in checking for typos in email addresses
> nor URLs.
>
> Moreover, completely ignore the contents of git trailers that hold
> contributor's names and email addresses.
>
> Cc: Diederik de Haas <didi.debian@cknow.org>
> Signed-off-by: Robin Jarry <robin@jarry.cc>
> ---
>  .codespellrc | 2 ++
>  1 file changed, 2 insertions(+)
>

On Sun Mar 30, 2025 at 20:52, Robin Jarry <robin@jarry.cc> wrote:
> Diederik de Haas, Mar 30, 2025 at 19:51:
>> Build failed because it doesn't like my email address? :-D
>>
>> It suggested 'didi' -> 'did'.
>
> Yeah, codespell can be a little overzealous. Can you submit a v2 with
> didi added in ignore-word-list of .codespellrc?

Shouldn't email addresses be somehow generally not included in codespell?
Adding every contributor's name that triggers codespell doesn't seem like the
best choice here.