Lessons from Creating a VSCode Extension with GPT-4

Re:Lessons from Creating a VSCode Extension with GPT-4 by anotherpaulg on Thursday May 25, 2023 @02:26PM (#36074217)

Good point, ctags is a bit old school! Most IDEs use Language Server Protocol now for similar purposes.

I added a few sentences of explanation and background on ctags to my writeup.

[ Parent | on HN ]

Re:Lessons from Creating a VSCode Extension with GPT-4 by cyrialize on Thursday May 25, 2023 @04:28PM (#36075753)

I'm a big fan of ctags. My old Emacs setup utilized Ctags when all else failed. So if I wanted to find a reference for something it would use LSP, then ctags if LSP returned nothing.

[ Parent | on HN ]

Re:Lessons from Creating a VSCode Extension with GPT-4 by RossBencina on Thursday May 25, 2023 @08:58PM (#36078488)

I've been thinking that there needs to be a LangChain or similar in-prompt Tool that allows the model to automatically query a Language Server Protocol server. Maybe your tool does everything that could be done that way anyhow. aider looks interesting, I will try it out.

[ Parent | on HN ]

Re:Lessons from Creating a VSCode Extension with GPT-4 by anotherpaulg on Thursday May 25, 2023 @09:58PM (#36078849)

Absolutely, LSP is strictly more capable than ctags for this purpose. I mention it in the future work section of the writeup I linked above.

The main reason I started with ctags is because the `universal ctags` tool supports a ton of languages right out of the box. Each LSP server implementation tends to only support a single language. So it would be more work for users to find, install and stand up the LSP server(s) they need for their particular projects.

I plan to try some experiments with LSP in the future.

[ Parent | on HN ]