Amolith,

I agree with the others that it's a great post, I enjoyed reading it (me
agreeing with much of what's written there may have something to do with
it ☺).

One idea I had while reading it is that it might be good to highlight
the thigs you write in direct speech (thoughts) in italic (or with
punctuation, I'm not sure what's more appropriate). I've seen some books
and maybe posts do that with thoughts given literally. This way it
stands out from the rest of the text, and the readers who tend to jump
around when reading can identify it easier.

A comment I had for the post's contents:

On Sat Feb 25, 2023 at 9:44 PM CET, Bence Ferdinandy wrote:
> Sorry, my bad, I was mixing up stuff. For me timestamp-format="2006 Jan 01 15:04"
> does not print timezone. And yes, I also think it's not very intuitive really ...
>
> The curly bracket thing is go-templates, which is nowadays a lot of places in
> the config, that's why I thought of that ...

I realized my setting for timestamp-format was being overwritten
(*facepalms deep inside*) in my config file, and that was the reason my
changes had no effect.

Something like timestamp-format="2006 Jan 01 15:04" actually works for
me too, and doesn't show timezone.

https://pkg.go.dev/time?utm_source=godoc#pkg-constants

I've been reading this link that the timestamp-format config option
refers to. I tried different things, but I couldn't make it display date
+ time *without* timezone.

Whenever I put something like "2006-01-02 15:04" there, it automatically
adds "CET" or "CEST" to the end. Is there a way to make this Go function
do exactly what I want, i.e. maybe the behavior of date(1)?

I'm not a Go programmer, could anyone please help me do this?

Ivan

Robin,

I accept. One commit I made was very minor though :)

Ivan

On Mon, Feb 20, 2023 at 06:59:01PM +0100, Robin Jarry wrote:
>Hi all,
>
>as you may know, aerc is currently distributed under the MIT license.
>This prevents from shipping aerc with notmuch support always enabled
>(notmuch being GPL).
>
>After some multiple reported issues when building from source and

On Thu, Sep 22, 2022 at 12:00:58PM +0200, Vladimír Magyar wrote:
>I'm no expert in this and don't really know how it works, but could it
>be possible to sign emails with a smart card?

https://www.gnupg.org/howtos/card-howto/en/smartcard-howto-single.html#id2507486

If I remember correctly, GnuPG can work with smart cards directly. And
the interface for keys that are on smart cards is the same as for the
ones in your home directory—so it will probably be transparent for Aerc
once you add make your smart card work with GPG.

I never signed emails with smart card, and it's been a while since I
even used one, so I can't give you better pointers.

>Could you please open an issue at
>https://github.com/aperezdc/notmuch-addrlookup-c ?

Done! Sorry, I should have thought about it myself.

Ivan

>Also a minor note, as I'm always comparing this to my previous setup: it feels
>as good as gmail's, it's much better than online outlook and if you have
>multiple accounts it's better than both because of the unification.

Can you also make it respect NOTMUCH_PROFILE environment variable? I'm
using two separate notmuch configs, and this program doesn't work with
my setup.

For example, I call notmuch like so:

   NOTMUCH_PROFILE=default notmuch search kek

But if I try the same with notmuch-addrlookup, it fails:

>Have you tried 'M-left' and 'm-left'?

No, I haven't. Is there a reason it should work? Neither docs nor code
seem to mention it.

>Is it possible to bind modifiers besides Ctrl?
>Ones like <Alt-Left>?

By the look of config/bindings.go it doesn't look like Alt is
supported. If I understand the code correctly, this part of the file is
declaring the available keybindings:

   func init() {
     keyNames = make(map[string]KeyStroke)
     keyNames["space"] = KeyStroke{tcell.ModNone, tcell.KeyRune, ' '}
     keyNames["semicolon"] = KeyStroke{tcell.ModNone, tcell.KeyRune, ';'}
     keyNames["enter"] = KeyStroke{tcell.ModNone, tcell.KeyEnter, 0}
     keyNames["c-enter"] = KeyStroke{tcell.ModCtrl, tcell.KeyEnter, 0}
     keyNames["up"] = KeyStroke{tcell.ModNone, tcell.KeyUp, 0}

> In pager, show current displayed line numbers, and the length of message
> (in percentage) currently visible to the user. Should help in reading
> long messages.

Sounds like a great idea. Applying this to my local config.

Ivan