TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Ask HN: Why is Emacs-lsp TypeScript integration so far behind VSCode?

1 点作者 viksit超过 2 年前
I&#x27;ve been an emacs user since college with my first foray into common lisp, and over the years, I&#x27;ve exclusively worked with a souped up .emacs config based on prelude for Python, Rust, and Clojure.<p>However, I&#x27;ve found it really hard to set up emacs-lsp with Typescript to even remotely match what VSCode offers.<p>For instance,<p>- Auto linting<p>- Auto import of mentioned modules<p>- A reasonable auto-complete across modules<p>- A mechanism to see code definition in different sections of a monorepo<p>(I&#x27;ve messed around with tide, emacs-lsp config, a lot [1]).<p>Is this an issue with emacs? Or with free contributor times vs paid microsoft engineers? Is anyone using emacs with lsp for typescript and has pointers to a .emacs config?<p>[1] https:&#x2F;&#x2F;github.com&#x2F;viksit&#x2F;prelude&#x2F;blob&#x2F;master&#x2F;init.el

1 comment

throwawaysalome超过 2 年前
It&#x27;s like competing against the Japanese for best sushi knife. Typescript is a Microsoft invention, to say nothing of Emacs&#x27;s complete lack of financial incentivation.