| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | | |
| | |
| | |
| | |
| | |
| | | |
.. from "caller" to "ui", as used throughout all subclasses.
The inconsistent naming causes the codacity code checker (pylint) to
complain every time we add a new command subclass.
|
| | |\ \
| | | |
| | | | |
crypto: Handle message that is encrypted, but the signature is invalid
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
One case of this would be not having the public key of the signer. If
the verification of the signatures fails, then use the signatures from
the error, and try to redecrypt without verification.
I have no tests yet, and this probably deserves tests.
Fixes #1157
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I had made the assumption early on that this would get bytes, but when I
added `assert isinstance(header, bytes)` alot would crash on startup,
changing `bytes` to `str` fixed that. I noticed this when trying to fix
the warning generated in the logging call.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We don't want to be comparing bytes anyway, the decode would use utf-8,
and that isn't right. Instead make the caller convert to a str of
Address first.
|
| | |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
currently _handle_signatures will pass `False~ for the error_msg if
there is no error, but the documentation for add_signature_headers says
it only accepts strings.
Don't do either of these, instead use None if there is no error,
otherwise a string, and updated the assert and documentation to match.
|
| | | |
| | |
| | |
| | |
| | | |
Commands running in a subprocess should return the terminal encoding so
we don't need to guess their encoding.
|
| | | |
| | |
| | |
| | | |
basically just remove hand rolling what try_decode does.
|
| |\| |
| | |
| | |
| | |
| | | |
This requires regenerating the accounts_table docs, as they've changed
for python 3.
|
| | |\ \
| | | |
| | | | |
Tag replied passed
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
maildir knows R and P flags which denote messages that have been replied
to resp. passed on (fowarded, bounced). They correspond to IMAP flags
\Replied and $Forwarded which are used by many clients and by
synchronisation software. E.g., mbsync syncs \Replied to R, a patch for
P is pending.
Implement replied_tags and passed_tags for alot which work similar to
sent_tags: sent_tags tags the sent message; replied_tags (resp.
passed_tags) tags the message being replied to (resp. being fowarded).
Basically, setting the replied_tags config to `replied` and replying to
a message has the same effect as doing `tag replied; reply`, but the
latter would tag even sending the reply is aborted or fails. The
implementation in this patch makes sure that the tagging is done only if
and when the reply resp. forward has been sent successfully.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
draft_tags works the same way as sent_tags, so provide the same defaults
and doc.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
force_list() converts single items to lists already. Thus, remove a
superfluous list() that could be mistaken for converting a single string
into a list of chars.
|
| |\| | | |
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
The code currently uses "cursor up", which seems wrong to me. This
corrects searching through prompt history only moving in one direction.
Fixes #1216
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
otherwise when we convert to utf-8 some programs (like w3m) honor the
encoding parameter in the HTML itself, which is now not correct. I'm not
sure if this is going to have side effects for other programs that
expect their data to be encoded in the terminal encoding.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
I can't reproduce this with arch, but it does reproduce in CI.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This reverts commit c7ec811b45d3c6c964cffbfc585f02d54d373ef3.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
I've run into a couple of emails now with badly formatted utf-8, so
let's use `errors='replace'`.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
the change to raw payload makes sense to me, we need to tell it to
decode using the content-transfer-encoding, and then transform tat back
into a str.
the need to join with '' instead of ' ' doesn't.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
There are a few that are still broken because of bytes to unicode
conversion, and this may not all be correct, but most of the tests pass
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The crypto code shouldn't use unicode strings, it should use byte
strings. The problem with using unicode strings (and doing the
conversion internally), is that the crypto code doesn't know what the
encoding should be. We can guess but it's better to just do bytes in
bytes out, and let the calling code deal with encoding and decoding.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This makes me a little nervous. I wonder if we're better off leaving the
bits that gpg works with as bytes while gpg is working with them and do
the string transformation later.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
In python 3 xrange is range, to get a list one must wrap range in list.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
in python3 dict.{keys,items,values} return views, which are similar to
iterators without some of the caveats about modifying the underlying
object. The iter* and view* methods have been removed, instead one warps
dict.x in iter or list to get those types.
|
