lsp 2022-09-07 | Slack Archive

borkdude21:09:36

This is more an emacs noob question than lsp-specific probably, but here it goes: when I navigate to somewhere else using M-., how can I return to where I came from?

ericdallo21:09:23

I use evil-mode so, C-o works for me which means evil-jump-backward

☝️ 1

ericdallo21:09:34

also C-x <left> works for buffer navigation too

dpsutton21:09:57

M-,

☝️ 1

borkdude21:09:59

yes, but within the same buffer I mean

ericdallo21:09:16

so evil-jump-backward

borkdude21:09:19

ah yes, M-,!

dpsutton21:09:20

xref-go-back

👍 1

borkdude21:09:25

I don't use evil

👍 1

😇 2

👼 1

borkdude21:09:26

xref-pop-marker-stack

borkdude21:09:52

thanks a lot

dpsutton21:09:23

I have (define-obsolete-function-alias 'xref-pop-marker-stack #'xref-go-back "29.1") . Not sure which is obsolete and which is replacing haha

dpsutton21:09:44

pop-marker-stack is the obsolete name

borkdude21:09:53

xref-go-back wasn't defined in my emacs

28.1... am I behind?

it will be soon

i’m on 28.1

so what's exciting in 29?

borkdude21:09:43

will the "long line fix" land?

dpsutton21:09:07

i’m on

(defgroup xref nil "Cross-referencing commands."
  :version "25.1"
  :group 'tools)

so not an emacs version but the version of xref

dpsutton21:09:13

I’m so stoked about the long line fix

borkdude21:09:28

from the changelogs:

+++
** Emacs can now be used more easily in an executable script.
If you start an executable script with

    #!/usr/bin/emacs -x

Emacs will start without reading any init files (like with '--quick'),
and then execute the rest of the script file as Emacs Lisp.  When it
reaches the end of the script, Emacs will exit with an exit code from
the value of the final form.

lread21:09:29

Anybody know when the long line fix will be available?

lread22:09:20

And is the fixer accepting any donations?

dpsutton22:09:24

i found this: https://lists.gnu.org/archive/html/emacs-devel/2022-08/msg00481.html

👍 1

ericdallo22:09:16

I'm super excited for that as well @UE21H2HHD 😂

lread22:09:44

Eli-Zaretskii is the fixer, yeah? Would like to buy him a coffee/beer/whatever.

dpsutton22:09:10

I thought I saw someone else spearheaded it. Eli is the maintainer of emacs

lread22:09:14

Ah…

borkdude22:09:56

https://twitter.com/daveliepmann/status/1567073534047920130

borkdude22:09:32

https://lists.gnu.org/archive/html/bug-gnu-emacs/2022-07/msg00349.html

dpsutton22:09:26

yeah that’s what i was looking for. thanks @U04V15CAJ

lread22:09:42

https://lars.ingebrigtsen.no/about/ > My name is Lars Ingebrigtsen. My day job used to be a CTO in banking, but I relax by doing some Emacs work.

😂 2

borkdude22:09:18

@UE21H2HHD That's just the guy who wrote the blog. The fixer was Gregory Heytings

lread22:09:31

Ah…

borkdude22:09:57

I think I know similar people who relax during their early retirement by doing Clojure... @UE21H2HHD :)

lread22:09:57

I’ve no idea who you are talking about. 😇 Also I’m getting rather old.

lread15:09:07

So https://news.ycombinator.com/item?id=32808690.

borkdude15:09:02

I want it

dpsutton23:09:34

In the past I’ve noticed that lsp would really slow down when changing branches (in emacs at least). It would lock up the UI while figuring out all that had changed. Just noticed it was non-blocking when rebasing on 90+ commits with some pretty big changes. Thank you to whoever worked on that. It is appreciated.

ericdallo23:09:50

Awesome! Me and @U07M2C8TT worked recently on that thanks to @U0178V2SLAY issues reports and help debugging!

dpsutton23:09:14

It is 100% noticeable and greatly appreciated. Thanks to all of you

💜 1

➕ 1

2022-09-07

Channels