Closed jterk closed 10 years ago
Jason Terk notifications@github.com writes:
If I compose a message that contains non-latin characters and send it using async-smtpmail-send-it the message fails to send because the asynchronous process hangs prompting for a coding system. The contents of the temporary emacs buffer when this happens:
Lisp expression: Select coding system (default raw-text):
Yes I have same problem here with mail containing special characters like bullet and square as we can find in this thread:
https://github.com/emacs-helm/helm/issues/438
Thierry Get my Gnupg key: gpg --keyserver pgp.mit.edu --recv-keys 59F29997
Jason Terk notifications@github.com writes:
If I compose a message that contains non-latin characters and send it using async-smtpmail-send-it the message fails to send because the asynchronous process hangs prompting for a coding system. The contents of the temporary emacs buffer when this happens:
Lisp expression: Select coding system (default raw-text):
An example message body that causes this problem:
"Umlaut" refers to a historical sound shift in German. In German, umlauts are found as ä, ö and ü. The name is used in some other languages that share these symbols with German or where the Latin spelling was introduced in the 19th century, replacing marks that had been used previously. The phonological phenomenon of umlaut occurred historically in English as well (man ~ men; full ~ fill; goose ~ geese) in a way cognately parallel with German, but English orthography does not write the sound shift using the umlaut diacritic. Instead, a different letter is used.
Should be fixed now (sent with mu4e and async-smtp)
Thierry Get my Gnupg key: gpg --keyserver pgp.mit.edu --recv-keys 59F29997
Fix confirmed.
If I compose a message that contains non-latin characters and send it using
async-smtpmail-send-it
the message fails to send because the asynchronous process hangs prompting for a coding system. The contents of the temporary*emacs*
buffer when this happens:An example message body that causes this problem:
Sending a message with the same body using
smtpmail-send-it
works correctly.