Skip to content
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

Thunderbird rich text not supported #10

Open
finex opened this issue Feb 21, 2021 · 3 comments
Open

Thunderbird rich text not supported #10

finex opened this issue Feb 21, 2021 · 3 comments
Labels
!?!? What on earth is happening here? I have no clue. Send help.

Comments

@finex
Copy link

finex commented Feb 21, 2021

Hi, I've tried to use Emacs Everywhere to compose a couple of emails using Mozilla Thunderbird.
If I wrote a plain text email everything is fine. If I try to compose a rich text email, line returns does not works. and all the lines are merged.

Probably the line return character is not translated to the correspondent "new line" (probably a <br> or a </p><p>, I did not check).

Thanks again :-)

@tecosaur
Copy link
Owner

Huh, I'm able to reproduce this is certain apps but I'm not sure what's going on.

@tecosaur tecosaur added the !?!? What on earth is happening here? I have no clue. Send help. label Feb 22, 2021
@finex
Copy link
Author

finex commented Feb 23, 2021

Let me know if I can help in some way.

@sebmiq
Copy link
Contributor

sebmiq commented Mar 6, 2021

FWIW, changing (call-process "xclip" nil nil nil "-selection" "clipboard" buffer-file-name) to (call-process "xclip" nil nil nil "-selection" "primary" buffer-file-name) in emacs-everywhere-finish fixes this for me.

WillForan added a commit to WillForan/emacs-everywhere that referenced this issue Feb 3, 2022
defcustom for alternative methods of handling the clipboard on linux
also added documentation of the added as well as other customizations

Overlaps with issue tecosaur#28 and maybe also a fix for issue tecosaur#10

The modifications have at least a few weak spots.
  1. emacs-everywhere-paste-cmd should maybe be a function
  2. organization of added functions and vars
  3. (eval `(... ,@Args)) is (apply ...) elsewhere

1. There's a solid argument that it's easier to use as a list:
the intent is clearer and there is little ceremony.
but it is weaker (can't drop into elisp) and inconsistent with
emacs-everywhere-filename-function and emacs-everywhere-linux-copy-function

2. I get the sense things were well organized before I started poking around.
But I'm not deep enough into to understand what should go where.

3. `emacs-everywhere-call` uses
    (apply #'call-process command nil t nil (remq nil args))
  Just saw that. That looks cleaner than using eval. I'm here to
  practice lisp. Got carried away in emacs-everywhere-paste-cmd?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
!?!? What on earth is happening here? I have no clue. Send help.
Projects
None yet
Development

No branches or pull requests

3 participants