Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

>You can duplicate the buffer side by side with the original buffer and in each window point will be at a different location.

I actually attempted that last night. It doesn't work unless you disable completion frameworks like company/LSP because as soon as a completion event triggers, both buffers snap to the completion location.



this is very odd. I both routinely have duplicate buffers visiting the same file and use LSP with company mode. I have never seen the snap effect you are describing. Why would completion trigger in both buffers? Maybe it is company vs ac-mode or some other completion system?


I use company with lsp. Perhaps it's dependant on language (server)? I was hacking some Go at the time.


I just tried it, can't reproduce. I'm programming in C++, so different server, but lsp shouldn't really care about the actual upstream server.

How do you open the second buffer visiting the file?


I was unable to reproduce this just now in emacs 26.3 using company/tide. I've been thinking about moving from tide to LSP, but that bug would drive me crazy so maybe I should wait for it to be fixed.


We haven't established that the bug isn't specific to users configuration.


Just tested this with company in a clojure buffer and did not observe this. I would suggest that something else responsible for the effect. Do you have any idea what causes this?


You are probably visiting the same buffer in a different window. What you want is clone-indirect-buffer-other-window.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: