summaryrefslogtreecommitdiff
path: root/alot
Commit message (Collapse)AuthorAge
* port thread.TagCommand to search bufferPatrick Totzke2012-01-08
| | | | | | | | this replaces thread.RetagCommand and thread.ToggleThreadTag by a refactored version of search.TagCommand. This means that in search mode, tag, untag, retag and toggletags commands are available through different decorations of TagCommand. Note that 'toggletag' has been renamed to 'toggletags' for consistency
* remove set_tags for remove_rest parm to add_tagsPatrick Totzke2012-01-08
| | | | | | Thread.add_tags now receives a 'remove_rest' parameter just like the analogous Message.add_tags. This makes Thread.set_tags obsolete
* add helpstrings for individual decorationsPatrick Totzke2012-01-08
| | | | of thread.Tagcommand.
* fix widget updating for thread retagPatrick Totzke2012-01-08
| | | | issue #236
* add retag command for thread bufferPatrick Totzke2012-01-08
| | | | | | that tags selection with given tags and removes all other tags from the message(s) issue #236
* propagate remove_rest in Message.add_tagsPatrick Totzke2012-01-08
|
* cleanup refresh callback used in TagCommandPatrick Totzke2012-01-08
| | | | issue #236
* make MessageWidget rebuild summary widgetPatrick Totzke2012-01-08
| | | | | | on each rebuild(). previously, this subwidget would never change and hence was excluded from being rebuild.
* use callbacks for widget update in TagCommandPatrick Totzke2012-01-08
| | | | | | | this makes thread.TagCommand update the buffers widgets using the newly introduced callback feature offered by Message.[add|remove]_tag. issue #242,#236
* update local tags in Message and ThreadPatrick Totzke2012-01-08
| | | | | by extending the afterwards callback issue #242
* introduce callback for writequeuePatrick Totzke2012-01-08
| | | | | | and offer this option in the wrapper classes tag/untag/settags methods. issue #242
* add TagCommand for threads modePatrick Totzke2012-01-07
| | | | | | and introduce the derived user commands tag, untag and toggletags for thread buffer. issue #263
* add ThreadBuffer.get_messagewidgetsPatrick Totzke2012-01-07
| | | | that returns all displayed message widgets
* Merge branch 'message-sumary-212' into testingPatrick Totzke2012-01-07
|\
| * display outstanding tags in MessageSumary linePatrick Totzke2012-01-07
| | | | | | | | | | | | where outstanding means those tats present in the message but not for every message in its thread. issue #212, #27
| * intersection arg for Thread.get_tags()Patrick Totzke2012-01-07
| | | | | | | | | | return tags present in all contained messages instead of in at least one (union)
* | fix gitignore filePatrick Totzke2012-01-07
|/ | | | and reset VERSION
* print in backgroundPatrick Totzke2012-01-07
| | | | | hardcode Pipecommands background parameter to True for the subclass PrintCommand
* clean up PipeCommand codePatrick Totzke2012-01-07
| | | | pep8 etc
* version string vanityPatrick Totzke2012-01-07
| | | | | | actually use the version string generated by git describe if possible. Also, don't check in every change to the version file and let its fallback content be "0.21+"
* print --all --separately by defaultPatrick Totzke2012-01-07
| | | | muttprint doesn't mailboxes well
* adjust PrintCommand wrt new PipeCommand argsPatrick Totzke2012-01-07
| | | | | decode is obsolete and we use the new format parameter instead. this also fixes some neglected docstrings
* introduce format parameter to pipeto commandPatrick Totzke2012-01-07
| | | | | | | and remove ids and decode parameter in favour of this more general setting. this determines the output piped to a command and must be one of raw,decoded,id or filepath
* fix typoPatrick Totzke2012-01-07
|
* Merge branch 'testing' of github.com:pazz/alot into testingPatrick Totzke2012-01-07
|\
| * Merge pull request #239 from 0x64746b/fix_docuPatrick Totzke2012-01-07
| |\ | | | | | | Fix docu
| | * Add documentation on themeing focussed tagsdtk2012-01-07
| | | | | | | | | | | | | | | | | | | | | | | | So far the comment in the default config only explained how to theme unfocussed tags. This commits extends the example (syntax) to indicate how focussed tags may be themed.
* | | added `background` parameter to pipto commandPatrick Totzke2012-01-07
| | | | | | | | | | | | | | | | | | | | | this allows to disable stdin and ignore stdout of the shellcommand. e.g. `pipeto less` works as expected. As of now this functionality is switched off by default. issue #237
* | | docs: added warning for call_cmd helperPatrick Totzke2012-01-07
|/ /
* | checkin fallback VERSION filePatrick Totzke2012-01-07
| | | | | | | | this will need to be touched before a release
* | make sure __init__ only reads the VERSION filePatrick Totzke2012-01-07
| | | | | | | | | | | | | | and never writes it. The file /alot/VERSION will be provided in the future and contain the release version string. setup.py will try to overwrite this with the result of `git describe` which will suceed only if we are on a git checkout.
* | update docs in version.pyPatrick Totzke2012-01-07
|/
* Reset logging before configuringdtk2012-01-05
| | | | | | | | | | | | | | | | Some unknown piece of code causes the `logging` lib to create a default configuration, which includes a logging level of `logging.WARNING` and a `StreamHandler`. The existence of this default configuration prevents our call to `logging.basicConfig()` to set the configured values, which leads to `debug` and `info` messages not being logged and all messages being streamed to `stderr` (which is controlled and gets flushed by `urwid`) instead of being written to the configured log file. This commit removes the existing `StreamHandler` before calling `logging.basicConfig()` which makes the latter install the desired logging configuration. Closes #170.
* Purge logging objectdtk2012-01-05
| | | | | | | | | Consistently use module functions instead. Introduce a non-default log format that replaces the logger name with the module name. Cf issue #170. Closes #231.
* Merge pull request #232 from 0x64746b/fix_loggingPatrick Totzke2012-01-05
|\ | | | | Fix logging
| * Fix basic logging functionalitydtk2012-01-05
| | | | | | | | | | | | | | | | This commit roughly restores the broken logging functionality. The first few messages are still logged to `stderr` as well as to the specified log file. Closes #170.
* | Don't register UI with DBMandtk2012-01-05
|/ | | | | | | The DBMan doesn't use it (anymore). It was potentially used to send notifications to the user. Closes #229.
* Handle missing highlighting rulesdtk2012-01-04
| | | | | | | | | So far exceptions were raised upon detection of an absent or syntactically invalid `thread_highlight_rules` option. This commit changes the behaviour to logging an exception and returning an empty set of rules as a fallback which will lead to the disabling of all highlighting. Cf https://github.com/pazz/alot/pull/226#issuecomment-3354066.
* Adjust code to new FallbackConfigParser behaviourdtk2012-01-04
| | | | | | | | | | | | Some of the methods in `AlotConfigParser` and code using the config parser used `get()` from the `FallbackConfigParser` to determine whether an option existed by inspecting the return value. This commit accommodates the fact that since 5d8481e733757a376231594c11e5f2f21ebcf086 the `FallbackConfigParser` doesn't return `None` on error but raises a `NoOptionError`. Cf https://github.com/pazz/alot/pull/226#commitcomment-836371 and https://github.com/pazz/alot/pull/226#issuecomment-3356448.
* Make FallbackConfigParser raise exceptiondtk2012-01-04
| | | | | | | | | So far the `FallbackConfigParser` returned the requested option if it existed, or `fallback`, which defaulted to `None`. Now the `FallbackConfigParser` only returns `fallback` if it has been explicitly given. If the fallback default has not been overridden, it raises a `NoOptionError`. Cf https://github.com/pazz/alot/pull/226#commitcomment-836371.
* Raise parser specific exceptions in configdtk2012-01-04
| | | | Using more specific `ConfigParser.*Error`s offers better hints at what went wrong.
* Comply with PEP8dtk2012-01-03
|
* Highlight threads that match a querydtk2012-01-03
| | | | | | | | | So far only combinations of tags could trigger highlighting of threads. This commit enables the configuration of highlighting rules that map arbitrary notmuch queries onto themeing options. Threads matching that query will be themed with the specified options. Cf https://github.com/pazz/alot/pull/223#issuecomment-3334800.
* Teach thread to check whether itself matches a querydtk2012-01-03
| | | | | | | | So far a mail thread could be asked whether it was tagged with all tags in a given list. This commit enables a thread to check whether it matches against a given notmuch querty and uses that new capability. Cf https://github.com/pazz/alot/pull/223#issuecomment-3334800.
* [PoC] Highlight threads upon arbitrary queriesdtk2012-01-03
| | | | | This commit is a quick n dirty proof of concept that shows how themeing according to arbitrary notmuch queries might be implemented.
* pep8Patrick Totzke2012-01-03
|
* fix name of SaveCommandPatrick Totzke2012-01-03
| | | | | c/p error: forgot to rename SentCommand to SaveCommand, which resulted in two different classes with the same name.
* use envelope.attach in AttachCommandPatrick Totzke2012-01-03
| | | | | | this fixes an issue with email parts showing up in envelope.attachments instead of Attachment objects because the new envelope.attach method wasnt used before.
* Merge branch 'feature-sort-145' into testingPatrick Totzke2012-01-03
|\
| * add new search command: "sort"Patrick Totzke2012-01-03
| | | | | | | | | | | | to change the used sort order in current search buffer. This also integrates the --sort parameter to the refine command
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-26 23:47:09 +0000