| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | | |/
| |/|
| | |
| | | |
This normalizes the indent of the file to be much more readable.
|
| |\ \ \
| |_|/
|/| | |
document SIGINT handling
|
| |/ /
| |
| |
| |
| | |
This adds documentation for SIGINT signals to the html and man pages,
and removes a "this is useful for.." comment on SIGUSR1.
|
| |\ \
| |/
|/| |
alot: replace email.Utils with email.utils
|
| |/
|
|
|
| |
In python 3 email.Utils doesn't exist, in python 2.7 both do, but Utils
is deprecated.
|
| |\
| |
| | |
Use python-gpg instead of pygpgme
|
| | | |
|
| | |
| |
| |
| |
| | |
This splits the loop into a closure and a call to any, which makes it a
little bit easier to read and understand.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This converts from the now abandoned pygpgme project for wrapping gpgme,
to the upstream gpgme python bindings (which are descended from the pyme
project, before they became official).
Largely this change should not be user visible, but there are a couple
cases where the new bindings provide slightly more detailed error
messages, and alot directly presents those messages to users.
This patch has been significantly revised and updated by Dylan Baker,
but was originally authored by Daniel Kahn Gillmor.
Fixes #1069
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
'z', the value currently passed to get_key isn't a valid value, so it
raises GPGMEError with a code of INV_VALUE. However, if an actual email
is passed a KeyNotFound exception is raised instead.
The existing test is valid and should remain, since it catches a
potential bug, but it doesn't test for a missing key, it tests for an
invalid key. This patch renames the existing test and adds a new test to
cover an actual missing key.
|
| | |
| |
| |
| |
| | |
This breaks the build with pygpgme, but it seems like too big of an
unrelated change to shove in with the main pygpgme -> gpg patch.
|
| | |
| |
| |
| |
| | |
This adds two new tests for the list_keys function that assert that the
private flag is honored.
|
| | |
| |
| |
| | |
travis allocates ~2 cores per machine, so -j3 should speed things up.
|
| |/
|
|
|
| |
to save time on cloning a whole repo that's just going to be thrown
away.
|
| |\
| |
| | |
Fix issue 1113
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently anything except "user@domain" (such as
"User Name <user@domain>"), will not work with the sign command, because
settings.get_account_by_address wants just the "user@domain" bit, and we
don't split it.
Fixes #1113
|
| | |
| |
| |
| |
| | |
These tests exercise issue 1113, which has to do with extracting the
mail correctly from the 'From' header.
|
| | |
| |
| |
| |
| | |
I wrote these looking at a bug, but they turned out not to be helpful
there, but they should be useful all the same.
|
| |\ \
| | |
| | | |
Fix Issue 1110
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Currently it's possible to set sign_by_default without setting a default
key. This is obviously not a good plan for all sorts of reasons. This
fixes the two failing tests from the last commit.
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This adds tests to exercise #1110.
These tests operated on a twisted async method, based on the
inlineCallbacks decorator (which creates a deferred, but looks like
synchronous code). The tests therefore have to use twisted's trial
module for unittest. These seem to operate mostly correctly using the
standard python unittest runner, pass and fail work right, but expected
failure does not. Instead of an expected failure, you get pass.
I really am not impressed with trial. After several hours of mucking
with it I never got it to run any tests, just spit out errors or do
nothing. pytest can run these tests just fine, and if we're going to
change test runner I'll again say that pytest is much nicer to work
with.
|
| |/ |
|
| |\
| |
| | |
Add `move next matching` command in thread buffer
|
| | | |
|
| | |
| |
| |
| |
| | |
If the querystring did contain an OR the results where misleading as the
AND binds stronger.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
The move command in thread buffers can recognize some predefined targets
to move to. All other arguments are interpreted as notmuch queries and
the next or previous matching message is moved to.
|
| | |
| |
| |
| | |
quantifiedcode shut down and we are now generating coverage stats on travis.
|
| |\ \
| | |
| | | |
add codeclimate config
|
| | | |
| | |
| | |
| | | |
this will hopefully disable complexity issues
|
| |\ \ \
| | | |
| | | | |
travis: generate coverage report
|
| | | |/
| |/|
| | |
| | | |
Generate a coverage report and upload it to codacy.com.
|
| |\ \ \
| |/ /
|/| | |
Format class decorators
|
| |/ / |
|
| |\ \
| | |
| | | |
docs: mention 'content' part in threadline theming
|
| | |/
| |
| |
| |
| | |
... which displays a prefix of the msg contents.
This feature was missing in the docs.
|
| |\ \
| | |
| | | |
Fix tests failing on other repos other than pazz's
|
| | | |
| | |
| | |
| | |
| | | |
You apparently need to use one style, either the directories method or
the not directories method.
|
| | | |
| | |
| | |
| | | |
This is required to get gpgme tests running.
|
| |/ /
| |
| |
| |
| |
| |
| | |
This can create circular imports in unittests, which causes difficult to
debug errors.
Fixes #1076
|
| |\ \
| |/
|/| |
Fix message count in statusbar after tagging
|
| |/
|
|
|
|
|
|
|
|
|
|
| |
When the else branch was hit the count was already updated by
SearchBuffer.rebuild() before the hitcount calculation was done and the
final result was obviously off. This fixes it by just counting the
messages in the search result directly.
The same code is implicitly already called in the other branch of the if
statement. So it is hopefully not a big overhead.
Fixes #1098
|
| |\
| |
| | |
Clean up doc source generators
|
| | | |
|
| |\ \
| | |
| | | |
command/envelope: Prompt before sending an encrypted message with Bcc
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently alot cannot encrypt to Bcc recipients, and it isn't obvious
how to implement encrypted BCC without a metadata leak (the key ids of
the Bcc recpients would be visible to the to and cc recipients as well
as the other bcc recipients). As such it hasn't been implemented yet
(although #949) is opened for such encryption.
In the mean time alot doesn't encrypt to bcc recipients at all, making
the message all but useless (it might be useful to send it to yourself
as a blind recipient, or to two email addresses of the same person).
Since most people don't know that alot has this limitation, we should
really warn them. This adds a prompt before constructing the message
for that case.
|
| |\ \
| |/
|/| |
Submit/update docs
|
| | |
| |
| |
| | |
Since the original patch that added the support didn't.
|
