-
-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tag mail directly after sending it #317
Comments
Nice idea. This would also be very helpful for my workflow. |
I expect this could be done already with custom headers and a custom notmuch post new hook. (Every email I send gets in my inbox so for me it's just easy to tag it right there). |
Hugo Roy writes on juli 5, 2017 14:48:
I expect this could be done already with custom headers and a custom notmuch post new hook.
You can configure custom tags to be added automatically already in the
config, but you can't manually add tags through the UI on the
'successfully sent message' yet.
|
Right. What happens if you manually add an email header in the text editor and send it to astroid? Will astroid discard the header? |
Hugo Roy writes on juli 5, 2017 14:52:
Right.
What happens if you manually add an email header in the text editor and send it to astroid? Will astroid discard the header?
At the moment yes, there is a issue regarding that (specifically the
Reply-To header).
|
Gaute Hope writes on juli 5, 2017 14:50:
Hugo Roy writes on juli 5, 2017 14:48:
> I expect this could be done already with custom headers and a custom notmuch post new hook.
>
You can configure custom tags to be added automatically already in the
config, but you can't manually add tags through the UI on the
'successfully sent message' yet.
This currently only works for messages that are saved directly and added
to the DB. It is possible to add ghost-messages in notmuch, but we're
not doing that in astroid at the moment.
|
Am 05.07.2017 um 14:55 schrieb Gaute Hope:
> You can configure custom tags to be added automatically already in the
> config, but you can't manually add tags through the UI on the
> 'successfully sent message' yet.
This currently only works for messages that are saved directly and added
to the DB. It is possible to add ghost-messages in notmuch, but we're
not doing that in astroid at the moment.
I don't know whether I expressed my proposal correctly. I don't want to
add the same tag to each mail I sent but individually for each message.
Using headers could be an option but I'd find it too hacky because of
missing or complicated auto completion of tags etc.
I could rather imagine having the possibility to add a tag before/after
sending the mail in the "new message" windows, ideally by using `l` as a
shortcut. However, I have no idea how to implement that in astroid
unfortunately...
|
yes, i like that idea too. as one uses an editor already a header-like entry would be nice that is retrieved by astroid (and removed) and given to notmuch instead... |
Would be nice too but IMHO usability-wise it would make most sense to tag the email via |
This will be a bit tricky without focusing the message in the entire
thread. So, first, this will only work for messages that are saved after
sending. Secondly, I think we will have to open the original thread, and
focus the just sent message.
|
Coming back to this issue because it would help me so much every day ;) After a message is sent, it should be quite easy to tag it from within astroid. We have the message id and it is saved in the notmuch DB, so we could basically run |
… in the db after sending
It would be awesome if astroid allowed us to tag a mail directly after (or shortly before) sending it.
Scenario: I write an email and I want to tag it with something like "waiting-for-reply" or "blocking" so I have a reminder for mails I have to remind people of.
Currently, this requires me to: write mail > go to sent mails > (open thread > ) tag single email.
Ideally we could tag the mail in the "New Message" window already with the known keybinding. If the mail has been sent, the tags are applied to it.
Would this be possible?
The text was updated successfully, but these errors were encountered: