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

✨ emacs-everywhere-linux-copy-function emacs-everywhere-paste-cmd #40

Closed
wants to merge 2 commits into from

Conversation

WillForan
Copy link
Contributor

@WillForan WillForan commented 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 #28 and maybe also a fix for issue #10

The modifications have at least a few weak spots.

  1. emacs-everywhere-paste-cmd should maybe be a function instead of a list passed onto call-process
  2. organization of added functions and vars
  3. (eval (... ,@Args))when(apply ...)` is used 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?

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?
make-local-variable hide change from taking effect and even without it
the variable change is buffer local
@tecosaur
Copy link
Owner

tecosaur commented Feb 9, 2022

I think the idea here is decent, I'm just inclined to do it a bit differently. Expect to see this in a commit soon :)

@tecosaur tecosaur closed this Feb 9, 2022
@tecosaur
Copy link
Owner

tecosaur commented Feb 9, 2022

Implemented in d20adad.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants