Zhexuan Chen

This pull request fixes two things: 1. `evil-easymotion` will still push a jump point even if a user passes nil for both :push-jump and :scope, I think most users would...

I'm not sure about whether the second commit is appropriate, but it seems to work pretty well with both built-in evil-jumps and third-party better-jumper. Internally, evil-mode also use `evil-set-jump` to...

> Hey, so I took a look at this. It's definitely clear that `evil-set-jump` is the correct thing to use. However, to fix the argument passing I think there is...

The solution you suggest is done. > 1. I think it's okay if we break backwards compatibility here, since this behavior wasn't described in the docs. Sorry, I did not...

No, I just think it takes too long to merge this request. I guess you may have some considerations on your side. It seems that's not the case. I will...

> If I don't misunderstand it, in mutli-threads server, when two threads handle two request at same time, then make a call of server stop with parameter soft set to...

`slime-c-p-c.el` contains quite an amount of legacy/old code, rewriting it needs time and motivation. A quick and dirty fix would be: ```emacs-lisp (with-eval-after-load 'slime (defun my--slime-completion-at-point () (let ((slime-current-thread :repl-thread)...

You can't specify both a vector and a stream to be read from. Change ```lisp (make-input-buffer :vector (make-octet-vector size) :stream stream) ``` to ```lisp (make-input-buffer :stream stream) ```

:sweat_smile: I overlook something in the source of `fast-read-byte`, samuel-hunter is right, it will read from the vector first and then the stream. But from the documentation, it seems that...