-
Notifications
You must be signed in to change notification settings - Fork 62
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
let*: Wrong type argument: consp, nil (cannot send or preview) #81
Comments
Please sent it to my personal email: jeremy.compostella@gmail.com.
Thank you.
…On Fri, Jan 8, 2021, 4:05 PM Morgan Willcock ***@***.***> wrote:
I have one particular mail which seems to trigger this issue, I guess it
is something specific to the HTML content.
If you could take a look, what would be the best way to send a copy of it?
it is probably best that I don't make the content public, just to be on
the safe side.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#81>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMACBAECM6WXHZ4TEFUXLDSY6FSPANCNFSM4V3CL4VA>
.
|
I've re-sent it to you, the subject contains the text "European Free Trade Association". |
Thank i have received it. I have a transfered it to my laptop. I'll have a
look at it later.
…On Sat, Jan 9, 2021, 7:32 AM Morgan Willcock ***@***.***> wrote:
I've re-sent it to you, the subject contains the text "European Free Trade
Association".
I imagine GMail will flag it as spam.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#81 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMACBG574VE6LK5JVSZA3LSZBSJVANCNFSM4V3CL4VA>
.
|
Also, could you describe the issue more precisely:
- is this when you hit reply or once you composed the reply and hit send ?
- enable debug (M-x toggle-debug-on-error), then reproduce and share the
content of the *Backtrace* buffer.
On Sat, Jan 9, 2021, 8:56 AM Jérémy Compostella <
jeremy.compostella@gmail.com> wrote:
… Thank i have received it. I have a transfered it to my laptop. I'll have a
look at it later.
On Sat, Jan 9, 2021, 7:32 AM Morgan Willcock ***@***.***>
wrote:
> I've re-sent it to you, the subject contains the text "European Free
> Trade Association".
> I imagine GMail will flag it as spam.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#81 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAMACBG574VE6LK5JVSZA3LSZBSJVANCNFSM4V3CL4VA>
> .
>
|
The reply buffer seems to work with no issues. It only happens when attempting to preview or trying to send the reply. I've included the backtraces below. When previewing:
When sending:
|
In some rare cases, the original email contains comments preceding the html tag. Most of the org-msg functions expects the html tag to be root the XML tree. This patch strips all the comments before turning the original email into an XML tree. This patch addresses #81. Signed-off-by: Jeremy Compostella <jeremy.compostella@gmail.com>
I think that the patch I have pushed on the experimental branch should fix this particular issue. Could you give it a try ? |
That change does fix it. Thank you. |
In some rare cases, the original email contains comments preceding the html tag. The `org-msg-html-buffer-to-xml' should return a XML tree which root tag is the HTML tag. This patch addresses #81. Signed-off-by: Jeremy Compostella <jeremy.compostella@gmail.com>
Thanks for testing. I was not very satisfied with my original solution. I find it a little bit too agressive. I made a more subtle fix. Could you verify that it also work for you? |
This change works too. |
This patch addresses #81. In some rare cases, the original email contains comments preceding the html tag. The `org-msg-html-buffer-to-xml' should return a XML tree which root tag is the HTML tag. Signed-off-by: Jeremy Compostella <jeremy.compostella@gmail.com>
fix pushed to master. |
I have one particular mail which seems to trigger this issue, I guess it is something specific to the HTML content.
If you could take a look, what would be the best way to send a copy of it?
it is probably best that I don't make the content public, just to be on the safe side.
The text was updated successfully, but these errors were encountered: