Fork me on GitHub
#spacemacs
<
2017-12-05
>
kvlt01:12:06

Anyone having issues with spacemacs throwing this error

Debugger entered--Lisp error: (file-error "Cannot open load file" "No such file or directory" "up-core")
  require(up-core)
  eval-buffer(#<buffer  *load*-21701> nil "/Users/me/.emacs.d/elpa/use-package-20171203.1313/use-package.el" nil t)  ; Reading at buffer position 1691
  load-with-code-conversion("/Users/me/.emacs.d/elpa/use-package-20171203.1313/use-package.el" "/Users/me/.emacs.d/elpa/use-package-20171203.1313/use-package.el" nil t)
  require(use-package)
  spacemacs-bootstrap/init-use-package()
This is a fresh clone of spacemacs with a newly generated .spacemacs file

ag01:12:30

use-package is broken. use melpa-stable. the easiest way is to switch to develop branch of spacemacs and set dotspacemap-use-spacelpa to t

kvlt02:12:07

Ah thank you!

kvlt02:12:25

I’ll give it a shot in a minute

paulspencerwilliams14:12:23

I'm using Spacemacs and have a working .eslintrc on a sample React App. When I invoke checking on a .js file, I expect it to list the issues present, but instead, it suggests that javascript-eslint is disabled, although enable-able: Syntax checkers for buffer App.js in react-mode: javascript-eslint (disabled) - may enable: yes - executable: Found at /Users/will/src/learning/eslint-with-react/node_modules/.bin/eslint - config file: found . I'm obviously being stupid, what am I missing? I've read the flycheck documentation but can't get my head around this configuration.

vuuvi16:12:20

so have you done a

fly-check enable
to get it to work again?

vuuvi20:12:26

everytime I delete something using the d command, hitting p will undo my delete command instead of pasting what I copied from my OS

chris20:12:33

yeah, unfortunately

chris20:12:53

this is solved in vim by using registers besides the unnamed register

chris20:12:22

I believe evil has these built in, but I'm not exactly sure how to make sure your clip register and kill register aren't the same

chris20:12:41

a work around is to kill into registers that aren't the default one

chris20:12:02

so "adip which kills the paragraph into the a register

eggsyntax20:12:14

@alexkeyes in other words, it is pasting what's at the top of your kill ring -- which is the thing you just deleted.

vuuvi20:12:05

that makes sense

vuuvi20:12:59

is there any way to learn more about registers that isn’t just trial and error?

eggsyntax20:12:20

You could also cycle through your kill ring to get to the previous thing (after you p). I forget the default binding for that, but each time you hit it it'll switch the pasted text to the next earliest thing.

eggsyntax20:12:54

Tons more online about various solutions to your particular issue too.

eggsyntax20:12:49

Looks like C-p is the default binding for cycling through kill ring.

eggsyntax20:12:57

Personally I rely less on the kill ring than on an OS-level register-history app -- CopyClip on Mac, CopyQ on Linux.

eggsyntax20:12:15

But I def turn to the kill ring when I need it

kvlt20:12:02

@ag thank you for your help last night, it worked!

vuuvi20:12:55

thanks for the info @eggsyntax!