-
Notifications
You must be signed in to change notification settings - Fork 11
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
[feature request] Signatures (non-crypto) #81
Comments
I've implemented this on the |
Thanks, I'll check it out! Despite my patch, I don't code in Mercury, otherwise I'd be submitting more patches (and fewer feature requests). I surveyed Mercury a year or two ago for feel and decided it wasn't my cuppa, and anything more complex than the most trivial copying of a pattern (as I did with the spam patch) is beyond my Mercury knowledge. |
It works well, thank you! One question: when replying to a message, after the quoted section there's a line in the message that says (in plain text)
Is that intended? e.g.:
|
That used to be generated by |
They would, normally, be part of the multipart metadata, but without a MIME separator it's interpreted as part of the message body. I didn't see them before the sig change -- was templatization part of that? |
I think you've confused two different things, at least I'm not sure what you're referring to. We started constructing our own reply templates about a year ago in order to support #28, and I simply mimicked the I've merged the signature change. |
Probably. I was talking about the fact that, when replying, I'm getting an inline |
I would like to be able to specify a file in the config that bower would append to the email template; this would allow a user to specify a (non-cryto) inline signature.
Such a feature might look like an addition to
bower.conf
:and if this option is set, bower would append this file to the file created by
create_temp_message_file()
before opening the editor.Edit 2021-04-30
I'm getting this behavior by having my editor command set to append the sig file:
The same could be done with
vim
too, obviously. This would be an acceptable work-around except for the fact that any invokation of the editor appends the file, meaning if a composition is closed and then edited again before sending, the sig will be added again.Although not in the original request, what I'd like to have is how Astroid mail handles signatures. Like Bower, there's some built-in support for markdown -> HTML support. Astroid has a configuration option to append one signature for plain-text messages, or a second when the user toggles HTML messages.
The text was updated successfully, but these errors were encountered: