I'd love a link to that improved jump-to-def... 😄

this bug is so annoying! 😄 https://cl.ly/2c0E023f4230 and the funny thing is - sometimes it doesn’t happen at all

@bravilogy are you on the master or develop branch of spacemacs? I'm on master, and I noticed that @spfeiffer is on develop, so maybe it's a bug that's been solved in the interim?

I tried develop as well

He wrote master in the ticket.

yeah, in the ticket I wrote master

But yes, i am on develop, windows 10, Emacs 26.1…all those differences.

@jeff.terrell how about you? were you on master when you could reproduce it?

Yep, I was and am on master.

oh well.. it’s very difficult to determine what’s causing it as it’s difficult to determine when is it happening exactly 😄 it doesn’t happen always. for example, if i keep recording and then executing that macro over and over again, 90% of times it will happen but then there’s a little chance it doesn’t happen. fo and fi by themselves are nothing special but when using in words like format and find, it’s annoying to see foormat and fiind typed after running a macro 😄 temporary solution for this project at work is to run a macro and then run search and replace throughout the project

to replace those malformed words

Whoa, are you telling me that it's not deterministic? Like in the exact same context it will sometimes be correct and sometimes wrong? Or could that be because there's something about where the expansion happens that is influencing whether it's correct or wrong?

yeah, it’s not deterministic. at first I thought there was something going on with vim registers, because in a few cases I recorded a macro, where I used o to start typing on a new line. and then, a few minutes later I recorded another macro (on the same key - q in this case), but instead of o I used i to start typing on the same line. and when I executed it, it inserted a new line instead

as if it had saved o from the last one

then I thought - maybe it’s because I’m using an external keyboard 😄 but it was the same behaviour on my macbook keyboard too. I will try to re-install everything - emacs and spacemacs and start from scratch I guess

Yeah…that's kinda tedious, but a great way to narrow down the problem, bisecting the packages installed and whatnot. I'd be interested to hear if you narrow it down! That'd be a heck of a bug report.

so.. deleted spacemacs, deleted emacs. removed all configs from my machine. installed emacs 26.1, cloned spacemacs to .emacs.d, hit f e d, typed

qq i fo ESC q @q

I’ll switch to develop now and will report back. if it’s happening there as well, I just give up 😄

wait, I read it yesterday, reproduced it in my machine, but somehow didn’t thought of it as a bug. Today I read it again - reproduced it, and then I got that it is indeed a bug 😄

I’m on develop btw

ok so far so good - it’s not happening on develop at the moment, for me. now I’ll start adding packages in, the ones I had before. here’s the list

'(themes-megapack
     html
     yaml
     javascript
     react
     elm
     (clojure :variables
              clojure-enable-fancify-symbols t)
     ;; ----------------------------------------------------------------
     ;; Example of useful layers you may want to use right away.
     ;; Uncomment some layer names and press <SPC f e R> (Vim style) or
     ;; <M-m f e R> (Emacs style) to install them.
     ;; ----------------------------------------------------------------
     helm
     auto-completion
     ;; better-defaults
     emacs-lisp
     markdown
     org
     (shell :variables
            shell-default-shell 'multi-term
            shell-default-height 20
            shell-default-position 'bottom)
     version-control
     mc-column
     (git :variables
          git-gutter-use-fringe t)

     ;; syntax highlighting
     (syntax-checking :variables
                      syntax-checking-enable-tooltips nil)

@troglotit what version of emacs do you have?

is it 26.* as well?

25.3.1

I installed from brew the one with bug-fix for magit performance (maybe sth like emacsport) emacs-plus

I used brew cask install emacs and it installed 26.1 version

ok so as soon as I set dotspacemacs-editing-style to 'vim, the issue comes back

otherwise it works fine

dotspacemacs-editing-style 'nil

I think that’s because of fd - which is <escape> used to escape to normal mode

happens on hybrid as well. doesn’t happen on 'emacs

time to learn emacs I guess 😄

@bravilogy - Like you have a fresh install and .spacemacs file, and that's literally the only change you make to the .spacemacs file for this behavior to start? If so, it might even be a bug in evil-mode, which would be kinda epic. I think you can move your ~/.emacs.d folder elsewhere before you start emacs to just run vanilla emacs. From there, I think M-x package-install will let you install packages like evil.

I’ll give it a shot now. and yes, that’s literally the only thing I’m doing

is it called evil?

Yep. That's what gives vim-like editing behavior.

If you can't reproduce the bug that way, then I'd start trying to figure out exactly which emacs packages spacemacs installs to support dotspacemacs-editing-style == 'vim.

it can’t find that package. I have a feeling I need to add this bit somewhere

(require 'package)
  (add-to-list 'package-archives '("melpa" . ""))
  (package-initialize)

Hmm, maybe so. Or maybe just run M-x package-initialize before you run M-x package-install.

(It's been a while since I used emacs without spacemacs.)

ok I tried evil mode in emacs and it works fine. so it has to be something within spacemacs editing style

Interesting. Do you have any idea what all evil packages spacemacs installs? I'm pretty sure it's installing more than just evil itself.

not really but I’m happy to dig deeper 😄 I’ll have another play around later on and see if I can find anything