| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| |
|
|
| |
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.
|
| | |
|
| |
|
|
| |
shlex expectes unicode in python3
|
| |
|
|
| |
This probably isn't completely right, but it's a start.
|
| |
|
|
| |
This module moved.
|
| |
|
|
|
| |
cStringIO doesn't exist in python 3.x, instead one simply uses
io.StringIO and python provided a C accelerated version if possible.
|
| |\
| |
| | |
fix ambiguous keys harder
|
| | |
| |
| |
| | |
always pass keyword arguments as thus, to prevent problems like this.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
As well as reducing duplication and adding screen size detection to
:pipeto and :pyshell, this ensures that the screen is always restarted,
resulting in cleaner error handling if an error occurs while the screen
is stopped.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This is caused by urwid/urwid#285; stopping and starting the whole
mainloop rather than just the screen works around this, but that's only
available in newer urwid versions.
This also affected the :pipeto and :pyshell commands.
|
| |\ \
| | |
| | | |
Fix templates with non-ascii characters.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Signed-off-by: Johannes Löthberg <johannes@kyriasis.com>
|
| |\ \ \
| |_|/
|/| | |
Fix `LANG=C alot` with custom bindings.
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Reproduction steps:
- Set a custom binding in your config file. E.g.:
[bindings]
S = toggletags spam
- start alot with LANG=C: LANG=C alot
- variant A: type ö
- variant B: type :search ö
Problem: the urwid encoding is set to 'narrow', such that all key events
are passed down as `str`, not `unicode`. At the same time, ConfigObj reads
the custom binding as a unicode string. The interaction of both leads to
crashes.
Related to #673
|
| |\ \
| |/
|/| |
Fix for issue 1164 - Cannot select key for encryption by number keys
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
error
* avoid endless loop if the selected key leads to an ambiguous key error again
* do not add the resulting key to the loop again instead add it directly
* use a list of keys as selection return values
* add fpr to visual key selection list to be able to select the expected key
* remove reversed call that should not be necessary
|
| | |
| |
| |
| | |
and a list of return objects for choices.
|
