| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
this essentially merges AccountManager into SettingsManager,
making the former obsolete
|
| | |
|
| |
|
|
| |
thos should not depend on user settings
|
| |
|
|
|
| |
unfortunately, you cannot be more specific as to validation errors
in subsections as "in this global section something went wrong".
|
| | |
|
| |
|
|
|
|
| |
this makes Theme objects check the integrity of their given
configs by instanciating urwid.AttrSpec objects in ther constructor,
so that invalid attribute strings don't raise errors at runtime
|
| | |
|
| | |
|
| |
|
|
|
| |
to new names for themespec and default theme
and corrected issue with 1c mode lookups (bg undefined)
|
| | |
|
| | |
|
| |
|
|
|
| |
and replace them with calls to settingsmanager.
this removes the highlighting feature for now!
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
that will return a doct containing normal and foccussed AttrSpecs
and translated string as given in
config subsections
[tags]
[[footag]]
fg =
bg =
focus_fg =
focus_bg =
translated =
|
| |
|
|
|
| |
this changes all "small" calls to a config getter
toa theyr counterparts that call SettingsManager.get
|
| | |
|
| |
|
|
|
|
| |
bindings are now part of the config spec (alot.rc.spec),
the default theme is a valid (as of theme.sec)
.theme-file, provided in alot/defaults
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
that handles alot.rc, notmuch.rc and themes:
It is intended to be a uniform object that offers *all* user settings via getters:
* theming_attributes
* bindings
* notmuch/alot config entries
later on: construction of accounts
|
| |
|
|
| |
to simulataniously work on old and new specs
|
| |
|
|
| |
that read in theme config files and provide urwid.AttrSpec objects
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This moves the addition of a Date header from Envelope.construct_mail
to the envelope handling commands. This allows us to store
mails locally that contain this timestamp, but send out mails
that do not so that the MTA, that will append its own timestamp,
doesn not create a second entry.
issue #326
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Threads use a set of tagstrings internally. This fixes a missing
construction of a set obj for a given list.
issue #323
|
| |\
| |
| | |
Decode attachment filenames as well
|
| |/
|
|
|
| |
Attachment filenames can be quoted-printable as well just like
headers. Decode them before further work
|
| |
|
|
| |
after moving the source directory of the docs one level up
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This has been introduced previously to enable Account.store_mail to index newly created
message files. This functionality has been moved to SendCommand and SaveCommand that use
FlushCommand to write out to the index (that deals with DatabaseErrors correctly).
|
| |
|
|
| |
call flush and use "afterwards" callback for notification
|
| | |
|
| |
|
|
|
|
|
| |
this is done using FlushCommand from the individual accounts:
FlushCommand will ensure that upon a locked index,
the changes will be caried out later. moreover,
this deals with Exceptions, the account doesn't.
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
This wraps the transaction code for a single write-queue item
into a try/except and re-inserts the current queue entry
to the write-queue upon errors.
|
| | |
| |
| |
| |
| |
| |
| | |
instead of doing in every add_message, add/remove_tags
function call, read the notmuchrc config once for
the 'synchronize_flags' setting in the flush method,
right before it's used
|
| | |
| |
| |
| |
| | |
this adds add/remove_message functionality to the
flush method and adds some inline comments and TODOs
|
| | |
| |
| |
| |
| | |
just enqueue the requested changes to the managers internal
writequeue; the actual functionality will be moved to `flush`
|
