By invoking 'print' for ics files from neomutt we can simply
add it to our local calendar directly from the interface.
Neat little 'cheat' to provide custom functions for specific
file types.
Synchronizes a git repository for the taskwarrior data directory,
automatically committing any changes after each command; and pushing and
pulling on syncing taskwarrior.
Fixed taskopen script not opening the correct numbered task
when passed one (either on the command line with `to <id>`
or through taskwarrior with `t <id> open`).
Now it does directly open the correct note.
Changed some colors, some keymaps and made it more flexible for new mail
account setups. Also removed most of the static gmail-related account
stuff since I don't need this in my public repo.
Simple wrapper for xdg-open functionality. Simply refers
to xdg-open except if there exists mimeo on the system
which it will refer to instead.
So, a simple preference modificator for mimeo over
xdg-open since that is my preference too.
Also gave it a short name so I can do open whenever I
want and don't have to tax my left hand with tying xdg.
Add a hash sign in front of 'project' tags received from
taskwarrior (i.e. where it is `project:something` it will
end up as #something in timewarrior.
Similarly, add a plus sign in front of tags: `+mytag`.
Only descriptions will be left as-is in translating from
taskwarrior to timewarrior.
This should make finding tags and projects specifically
much easier in timewarrior (e.g. for counting up the total
time spent on a single project).
Updated key mappings to use `,` as the 'local-prefix' (or 'macro-prefix') which
allows easier setup for an additional functionality layer.
Also make `dd` the standard way to delete a whole sub-thread instead of
single mail by single mail of a conversation. That functionality can now
be achieved with `dD` instead, while `dd` removes a whole thread (not
just sub-thread).
If no hook should be run before syncing (or a user-defined hook) then
the warning should fall under that and not be run as part of it.
Additionally takes care of multiple decryption requirements in a row.
I am using card (in conjunction with my vdirsyncer setup) to quickly get
an overview of my contacts and use them for email sending. This adds a
very simple config to the repo which gets khard up and running.
Extended active task listing to show both the active task from
taskwarrior, but also any currently 'tracking' task from timewarrior.
Ideally, those should be the same - but if they mismatch or timwarrrior
is not correctly tracking the active task, this is still good
information to have at a glance.
Added configuration for urlview which neomutt uses to parse out urls
from emails to, by default, make use of xdg-open to decide which program
to open them in instead of sending them to lynx.
Added page up/down movement with the C-u/d/b/f key combinations, as well
as message and thread removal with dd (message), dT (thread) and dt
(sub-thread) chords.
Replies have been changed to rr (reply all) or ro (reply one).
The 'new' flag can be toggled by s (for seen) as previously, though now
other flags can be toggled with S and all messages can be marked as seen
with C-s.
Other things are mostly the same, though threads can be collapsed with
za (one) or zA (all) and moved between with gt/gT.
The beginning of what I hope can be a useful integration: send mails to
taskwarrior as tasks and open the corresponding mail from tasks in
taskwarrior.
To make a task out of an e-mail, in neomutt, simply press `t` when the
mail is selected or opened. It will create an automatic task in
taskwarrior with the description "Reply to [mail] by [sender]" and tag
it as mail.
If you press `T` instead, you can give the task your own description and
tags.
In taskwarrior, you can simply `t open <taskid>` on a task that came
from neomutt to show the message content on the command line (using
notmuch). This is still a bit rudimentary and I would like an improved
display, but it works for now.
Since I am striving for closer connection between my task management, my
mail suite and my calendar appointments, it makes sense to unify all
'office' tasks into the single office module instead of keeping
taskwarrior outside of it.
Marty Oehme