summaryrefslogtreecommitdiff
path: root/alot
Commit message (Collapse)AuthorAge
* 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
| * propagate search parameter to commandline argsPatrick Totzke2012-01-03
| | | | | | | | | | this makes the --sort parameter available as a command line parameter
| * add '--sort' parameter to search commandPatrick Totzke2012-01-03
| |
| * introduce config switch 'search_threads_sort_order'Patrick Totzke2012-01-03
| | | | | | | | and make search buffers respect it
| * introduce sort orders in DBManagerPatrick Totzke2012-01-03
| | | | | | | | | | and make get_threads respect the given `sort` parameter. issue #145
* | Select highlight theme only once per refreshdtk2012-01-02
| | | | | | | | | | | | So far the highlight theme to use was calculated for every component although the result was always the same. Now it is only chosen once per screen refresh (rebuild() and render()).
* | Amend highlighting of date and mailcount in rebuild()dtk2012-01-02
| | | | | | | | | | | | This commit amends da5660132e9998b15b06d1bc235db0d7f72f4e5f that didn't enable highlighting of the date and mailcount components in the rebuild() method of ThreadlineWidget.
* | Comply with code conventions for private methodsdtk2012-01-02
| | | | | | | | | | | | Prefix private attributes with one underscore instead of two. This corresponds to the conventions proposed by PEP8. Cf https://github.com/pazz/alot/pull/204#issuecomment-3300899 et seqq.
* | Adjust default highlight themesdtk2012-01-02
| | | | | | | | | | | | Incorporate new feature to highlight tag combinations. Make default themes for unread and flagged threads more consistent and merge them into a default theme for unread, flagged threads.
* | Enable highlighting of tag combinationsdtk2012-01-02
| | | | | | | | | | | | | | | | | | | | | | So far, thread highlighting depended upon a single tag. This commit enables specification of a combination of tags to trigger a theme. So now it is possible to define a highlighting theme for a combination of tags like `unread AND flagged`. Cf issue #25.
* | Teach thread to check for several tagsdtk2012-01-02
| | | | | | | | | | So far a thread could only be asked whether it was tagged with a single tag. This commit enables a thread to check against a list of tags.
* | Don't fallback to lower priority tag themeingdtk2012-01-02
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | So far if the config provides no themeing for a threadline component for a given tag, the following highlight tags are checked. Only if no themeing has been provided for any configured tag, the untagged theme will be used. This leads to themes for different highlight tags being mixed if a higher priority tag doesn't define theming for a component a lower priority tag does. This commit disables fall-through to lower priority themeing in order to avoid mixing of themes. Therefore a missing themeing for the top priority highlight tag immediately triggers fallback to the themeing of the parent option. Cf issue #25. Closes #211.
* | Refine selection of default themeing for highlightingdtk2012-01-02
|/ | | | | | | | | | | | | | | The setting for config option `aaa_bbb_{component}_focus_{tag}_bg` doesn't fall back onto `aaa_bbb_{component}_focus_bg` because so far we only check if a config entry for `aaa_bbb_{component}_focus_{tag}_{fg|bg}` exists. If *one* of them exists (`fg OR bg`), we use that *combination*. If then the other entry does not exist, it falls back to `'default'`. This commit refines the fallback selection mechanism in that is tries recursively to select themeing for the parent option (`aaa_bbb_ccc_fg` => `aaa_bbb_fg`) before finally falling back to the default setting. Cf issue #25. Closes #208.
* don't double-quote pathsPatrick Totzke2012-01-01
| | | | | detect presence of quoting ticks in mime-handler fixes issue #140
* multi word commands for pipetoPatrick Totzke2012-01-01
| | | | | | | split commandline strings into lists in PipeCommands constuctor if the shellcmd comes as a string instead of a stringlist. if we let argparse do the splitting, t will try to interpret parameters itself. This fixes issue #117, this cmdline now works: pipeto all 'tee bla'
* don't display text/plain attachments in bodytextPatrick Totzke2011-12-31
| | | | | | | before, an attachment with mimetype text/plain would be displayed as part of the body text of a message in case no text/html part exists. this patch makes message.extract_body skip thse parts closes issue #220
* move signature adding to ComposeCommandPatrick Totzke2011-12-30
| | | | | | | | this also implements the feature that uses the 'signature_as_attachment' account option: if set to False, the signature file will be appended to the body text (if its mimetype is text). closes #173
* added account option 'signature_as_attachment'Patrick Totzke2011-12-30
| | | | | that causes the content of the signature file to be appended to the initial body text of an envelope instead of attached
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-29 03:10:27 +0000