Pressing `Enter` on a view that has not yet loaded messages (e.g. at
startup) would return `nil` from `Selected()`. Accessing `msg.Uid` on a
`nil` reference crashes aerc.

This patch moves the `msg == nil` check before accessing `msg.Uid` thus
avoiding the crash.

To test this patch repeatedly press `Enter` on startup.
---
 commands/account/view.go | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/commands/account/view.go b/commands/account/view.go
index b287406..aab9052 100644
[message trimmed]

One more thing (sorry for the reply spam):

> +add_header Strict-Transport-Security "max-age=63072000; includeSubDomains; preload" always;

"preload" can be dangerous if enabled on a whim:

https://hstspreload.org/#opt-in

Preload + hstspreload.org submission will make browsers *always* use 
HTTPS for sr.ht + subdomains with no workaround (if cert is invalid 
there won't be a "load site anyway" button in the browser UI).

In 2019 SSL certs are available for free so it's not a big problem but I 
think it's good to point out the ramifications of this process: removing

Hi Kyle,

> +add_header Upgrade-Insecure-Requests "1" always;

Upgrade-Insecure-Request seems to be a request header (that is sent by 
clients, not servers). More info on MDN:

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Upgrade-Insecure-Requests

and in the spec:

https://w3c.github.io/webappsec-upgrade-insecure-requests/#preference

Kind regards,

On 25.05.2019 22:40, Drew DeVault wrote:
> Interesting idea, but I'd like to explore ways of implementing this that
> don't require extra intervention from users. Ideally we would find a
> solution that just works by default.

Got it. For the record git has "am.messageid" configuration variable 
that can be set once and it will "just work".

I generally enjoy git's "stupid content tracker" motto and that it 
doesn't try to be too "smart" but I'd be interested in looking at how 
would the automatic detection work.

Kind regards,
Wiktor

Hello,

I just found out that git am accepts "--message-id" option that causes 
it to embed Message-ID from the patch e-mail into the commit message.

Would it be useful for SourceHut to detect such embedded Message IDs and 
re-use it for cross-linking and automatic management of patch status? 
(For example if a commit with Message-ID is pushed then the relevant 
patch e-mail can be marked as "merged").

Kind regards,
Wiktor

--

Signed-off-by: Wiktor Kwapisiewicz <wiktor@metacode.biz>
---
I don't know if line doesn't need to be re-flowed to adjust to line
limit.
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 9687d30..321e99d 100644
--- a/README.md
+++ b/README.md
@@ -113,7 +113,7 @@ With `git send-email` configured, you can clone the project and set it up for su
 
 Contributors must agree to the [developer certificate of origin](https://developercertificate.org/),
[message trimmed]

Hi Elias,

> Or a special mailing list address could turn all emails into tickets
> more or less automatically, just like Zendesk
> and the like.

I like that idea.

I'm actually wondering why it wasn't pursued as on first sight a bug 
tracker could be easily modelled using a mailing list where for each 
thread there is a little bit of metadata stored (status, label) that 
could be changed via e-mail interface. I guess that would be similar to 
Debbugs in some aspects.

On 22.01.2019 11:27, Wolf480pl wrote:
> W dniu 22.01.2019 o 00:29, Ludovic Chabant pisze:
>> I found some interesting blog post from FastMail (the email provider I
>> use and, arguably, one of the top paid providers) about why they don't
>> plan to support "format=flowed":
>> https://fastmail.blog/2016/12/17/format-flowed/
>>
>> (basically nobody supports it so as a result... nobody supports it :) )
> 
> They have an interesting point about patches getting broken.
> 
> The format=flowed RFC supports having lines that are explicitly meant
> not to be wrapped (they call them "fixed lines") but looks like
> many format=flowed MUAs don't give you a way to write such lines

On 19.01.2019 00:01, Wolf480pl wrote:
> I looked at the format=flowed spec[1] several days ago,
> and it looked like a pretty good standard, and was pretty simple IMO.
> 

Yes. For display only it should be pretty straightforward: if the
message is format=flowed then all lines ending with a space would be
concatenated with previous line. Then they can be wrapped for display
purposes even with CSS "white-space: pre-wrap" [0] or something similar.

Currently reading the threads on mobile is not an easy task.

Kind regards,
Wiktor

Hi,

There is also `--export-filter` option to GnuPG that can be used to
minimize the exported key size. For example `keep-uid` parameter will
only export selected User ID:

$ gpg --export-filter keep-uid='mbox = EMAIL' --export EMAIL

Details here:
https://lists.gnupg.org/pipermail/gnupg-devel/2016-July/031294.html

Kind regards,
Wiktor