summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* validate key before adding to encryption listJohannes Kulick2013-02-19
| | | | | | | | | we check whether a key is - revoked - expired - invalid - unable to encrypt - unable to sign
* complete key hints anywhereJohannes Kulick2013-02-19
|
* show UID information instead of KeyIDJohannes Kulick2013-02-19
| | | | This reads nicer then a hash string. The format is: name (comment) <email>
* pep8 fixesPatrick Totzke2013-02-19
|
* add auto completion of gpg keysJohannes Kulick2013-02-19
|
* add function to list all keysJohannes Kulick2013-02-19
| | | | We need that for auto-completion
* escape double quotes as wellJohannes Kulick2013-02-19
|
* handle more error codesJohannes Kulick2013-02-19
| | | | | sometimes if gpgme doesn't find a key it gives INVALID_VAL sometimes EOF, we now handle both
* if all encryption keys are removed set flag to falseJohannes Kulick2013-02-19
| | | | | If all the encryption keys are deleted from the encryption list set the encrypt flag in the enveleope to false
* automatically fill in recipients as encryption recipientsJohannes Kulick2013-02-19
| | | | | if the user doesn't supply encrypt with a list of encryption keys, the email addresses of the email recipients are used
* rmencrypt now accepts keyids/hints instead of indicesJohannes Kulick2013-02-19
| | | | | We use an own has function for that, since pygpgme doesn't implement __cmp__() or similar
* support multiple recipients in encryptionJohannes Kulick2013-02-19
| | | | | | | | Multiple recipient-keys can be specified. They are shown in the envelope buffer. A new command is introduced: 'rmencrypt' do remove a key from the encryption lsit. Unfortunately pygpgme doesn't implement __cmp__() so we have to either write something similar on our own or use this solution (index of the key in encryption list)
* add docs for (un)encryptJohannes Kulick2013-02-19
|
* show whether the mail will be encryptedJohannes Kulick2013-02-19
| | | | | We add a GPG encrypt line with the key to encrypt as description in the envelope buffer
* move key dissolving to commandJohannes Kulick2013-02-19
| | | | | It is more useful if we check wether the key is available directly when the user ask for encryption, rather than doing it before sending it
* give useful error message if key can't be foundJohannes Kulick2013-02-19
|
* add docJohannes Kulick2013-02-19
|
* pep8 correctionsJohannes Kulick2013-02-19
|
* add unencrypt and toggleencrypt commandsJohannes Kulick2013-02-19
|
* add encrypt documentationJohannes Kulick2013-02-19
|
* add key parameter to encrypt commandJohannes Kulick2013-02-19
| | | | | We now can define the key, we want to encrypt with as parameter of the encrypt command
* create PGP/MIME mail, if encrypt flag is setJohannes Kulick2013-02-19
| | | | | | | | | | | | | If the envelope has the encrypt flag set we encrypt the (signed if available) mail and create a PGP/MIME compliant mail TODOs: a) create a 'This is a PGP/MIME encrypted mail...' warning on top of all multipart parts b) find the correct key for encryption c) find a way to handle multiple recipients
* add encrypt commandJohannes Kulick2013-02-19
| | | | | The encrypt command sets the encrypt flag of an envelope, which we will use to later encrypt a message
* add encryption functionJohannes Kulick2013-02-19
| | | | | This function takes a plaintext string and encryptes it with a given gpg key and returns the encrypted text
* Merge branch '0.3.3-feature-movecmd-538'Patrick Totzke2013-02-19
|\
| * Notify for unknown movement.William Erik Baxter2013-02-19
| |
| * Conform to PEP 8.William Erik Baxter2013-02-19
| |
| * Implement move commands in globals.py. Add --redraw for bclose.William Erik Baxter2013-02-19
|/
* docs: updated autogenerated command docsPatrick Totzke2013-02-14
|
* Merge branch '0.3.3-fix-556'Patrick Totzke2013-01-30
|\
| * make sure urwid keeps track of updated TERM sizePatrick Totzke2013-01-30
|/ | | | | | ... after external processes terminate. fixes #566
* Merge branch '0.3.3-workers-love-555'Patrick Totzke2013-01-24
|\
| * Add some comments to the db manager async codeJustus Winter2013-01-24
| | | | | | | | Signed-off-by: Justus Winter <4winter@informatik.uni-hamburg.de>
| * Replace workers std{out,err} by pipes and log anything written to themJustus Winter2013-01-24
|/ | | | | | | | This will help us identify problems in libnotmuch and reduces visual artifacts (unfortunately libnotmuch writes messages to stderr that used to clobber the curses interface). Signed-off-by: Justus Winter <4winter@informatik.uni-hamburg.de>
* Merge branch '0.3.3-fix-411'Patrick Totzke2013-01-22
|\
| * Join worker processes and keep track of them in the logJustus Winter2013-01-22
|/ | | | | | | | | This also prevents a zombie from hanging around until the next worker is spawned by multiprocessing. Fixes 411. Signed-off-by: Justus Winter <4winter@informatik.uni-hamburg.de>
* Merge branch '0.3.3-fix-docs-552'Patrick Totzke2013-01-22
|\
| * don't mention that first run creates default configPatrick Totzke2013-01-22
|/ | | | | because it doesn't any more.. close #552
* Merge branch '0.3.3-fix-nowait-547'Patrick Totzke2013-01-19
|\
| * empty input queue as soon asPatrick Totzke2013-01-11
| | | | | | | | | | .. the current value cannot be prefix of any bound keysequence. fixes #547
* | Merge branch '0.3.3-fix-544'Patrick Totzke2013-01-15
|\ \
| * | deliver an empty ListBox[] on errorbjoernb2013-01-15
| | |
| * | fix 544Patrick Totzke2013-01-15
|/ / | | | | | | | | only sort messages with not-None date header, append the rest
* | Merge branch '0.3.3-fix-325'Patrick Totzke2013-01-08
|\ \ | |/ |/|
| * Ignore EINTR in workers when terminating due to SIGTERMJustus Winter2013-01-08
|/ | | | | | | | | | If the child process is killed using SIGTERM by the parent, send(2) can fail with EINTR. Install a signal handler for SIGTERM and ignore EINTR in this particular case. Fixes #325. Signed-off-by: Justus Winter <4winter@informatik.uni-hamburg.de>
* Merge branch '0.3.3-solarized-theme-fix-550'Patrick Totzke2013-01-08
|\
| * adjusted unread-threadline themingPatrick Totzke2013-01-08
| |
| * solarized_dark: improve 256 color approximationMichael Turquette2013-01-07
|/ | | | | | | | | | | | | | | | | | | | Solarized colors for 256 color palettes are not as closely approximated as they could be. 256_base0 is set to g66 in Urwid's 256 color palette. This corresponds to #a8a8a8 in Xterm. base0 should ideally be #808080. This matches g50 exactly, so switch to that grayscale value. 256_base1 is set to g70 in Urwid's 256 color palette. This corresponds to #b2b2b2 in Xterm. base1 should ideally be #8a8a8a. We can't get this exactly with Urwid's 256 color palette, but #848484 is a closer approximation. Switch to g52 to get this grayscale value. 256_cyan is set to #088 in Urwid's 256 color palette. This corresponds to #008787 in Xterm. cyan should ideally be #00afaf. This matches #0aa exactly, so switch to that value. Signed-off-by: Michael Turquette <mturquette@deferred.io>
* Merge branch '0.3.3-fix-locked-541'Patrick Totzke2012-12-16
|\
| * bug on exit if index not syncedPatrick Totzke2012-12-16
| |
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-06 07:21:18 +0000