Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Emacs 31: An unofficial guide to Markdown-ts-mode

rahuljuliato.com

Post reply on HN
Print view View original

81–90 of 92 posts

Re: Emacs 31: An unofficial guide to Markdown-ts-mode

#81

Post by setopt »

lurght wrote: post #24
RahulMJ wrote: post #15

A bit of extra info: - `ts` stands for "tree-sitter", meaning this mode uses tree-sitter under the hood, which is, among other things, very performant. - There's support for the CommonMark spec and GFM, so things like `- [ ]` checkboxes and ~~strikethrough~~ work out of the box, along with many other small QoL features. - This mode is BUILT-IN, so no extra packages are needed. - This is currently in the experimental…

I think in 31 registering the file types isnt necessary any more, the mode opens automatically for me (and i did manually delete the old markdown-mode)

Are you using the 31 release or prerelease? The mode was changed to experimental right before release.

Just FYI, I think the comment you replied to is by the author of the mode and an upstream Emacs contributor, so I would assume their instructions are up to date for the 31 release.

Re: Emacs 31: An unofficial guide to Markdown-ts-mode

#82

Post by cpach »

mplanchard wrote: post #80
jlokier wrote: post #76

Earlier quoted context omitted.

It's still reasonable to ask what's different about markdown-ts-mode compared with markdown-mode. I read that article, and I didn't notice anything that stands out as different from markdown-mode (the non Tree Sitter version). Regular markdown-mode also highlights everything, hides markup if you like, cycles section visibility if you like, fills paragraphs in bullets, etc. With poly-markdown-mode it also does languag…

Mostly same as with any treesitter mode: it’s easier to build structurally-aware features, and it automatically supports any minor mode that’s enabled by treesitter (examples from my own config include structural movement, folding, selection, indentation guides, etc.). So, rather than every language having to reinvent the wheel, and every user having to install six different language-specific packages to get feature…

That sounds like an improvement. Thank you for explaining!

Re: Emacs 31: An unofficial guide to Markdown-ts-mode

#83

Post by dleslie »

BeetleB wrote: post #67
dleslie wrote: post #61

Earlier quoted context omitted.

It launches with a scratch buffer, menu bar with populated menus, a functional mini buffer, and so on. All of this is opinionated defaults and configurable with elisp. And yes, much of Emacs is broken out of the box and it's been that way a long while. That's not a good thing. Emacs isn't ready for the masses. Broken defaults, and a brittle experience once features are made working is standard. I've used Emacs for th…

> Emacs isn't ready for the masses. It never will be. It's simply not a goal they have. It's tiring to keep hearing people point it out. Emacs is also not ready to be your web server. Or your Jira replacement. It's not a lot of things - we don't need to itemize them all. I've written a lot of stuff. Some of it I released publicly. None of it is for the masses. There are better tools for the masses - let them use thos…

The best tool is the one that makes completing tasks better: faster, easier, cheaper, or superior.

It takes significant usage and training to overcome the overhead that Emacs imposes. There are other tools that are fast, free, and capable which do not have this problem.

Even tools which are reasonably extensible. Like VSCode. There's good reason that all the new agentic development environments aren't forks of Emacs or NeoVim.

Re: Emacs 31: An unofficial guide to Markdown-ts-mode

#84

Post by BeetleB »

dleslie wrote: post #83
BeetleB wrote: post #67

Earlier quoted context omitted.

> Emacs isn't ready for the masses. It never will be. It's simply not a goal they have. It's tiring to keep hearing people point it out. Emacs is also not ready to be your web server. Or your Jira replacement. It's not a lot of things - we don't need to itemize them all. I've written a lot of stuff. Some of it I released publicly. None of it is for the masses. There are better tools for the masses - let them use thos…

The best tool is the one that makes completing tasks better: faster, easier, cheaper, or superior. It takes significant usage and training to overcome the overhead that Emacs imposes. There are other tools that are fast, free, and capable which do not have this problem. Even tools which are reasonably extensible. Like VSCode. There's good reason that all the new agentic development environments aren't forks of Emacs…

> There are other tools that are fast, free, and capable which do not have this problem.

You are merely mirroring what I said.

> There's good reason that all the new agentic development environments aren't forks of Emacs or NeoVim.

And there's nothing wrong with the fact that Emacs will never be the tool people fork for agentic (or IDE, or for any other purpose). That's not a mark against Emacs.

Re: Emacs 31: An unofficial guide to Markdown-ts-mode

#85

Post by dleslie »

BeetleB wrote: post #84
dleslie wrote: post #83

Earlier quoted context omitted.

The best tool is the one that makes completing tasks better: faster, easier, cheaper, or superior. It takes significant usage and training to overcome the overhead that Emacs imposes. There are other tools that are fast, free, and capable which do not have this problem. Even tools which are reasonably extensible. Like VSCode. There's good reason that all the new agentic development environments aren't forks of Emacs…

> There are other tools that are fast, free, and capable which do not have this problem. You are merely mirroring what I said. > There's good reason that all the new agentic development environments aren't forks of Emacs or NeoVim. And there's nothing wrong with the fact that Emacs will never be the tool people fork for agentic (or IDE, or for any other purpose). That's not a mark against Emacs.

Emacs isn't the best code editor. It isn't the best note taker. It isn't the best document writer. It isn't even a good lisp.

What is Emacs the best at these days?

Re: Emacs 31: An unofficial guide to Markdown-ts-mode

#86

Post by iLemming »

jlokier wrote: post #75
iLemming wrote: post #49

Earlier quoted context omitted.

It's not that simple. The formats differ structurally. Org-mode is a proper tree - that's its fundamental basis. A tree where each branch can hold k/v pairs of metadata. Markdown is rather a flat sequence of blocks with level markers sprinkled in. Neither of that (proper tree or records) fundamentally supported in Markdown within an agreed spec - pandoc attach attributes on its own way, kramdown does it differently,…

It would probably be enough if Org files could use Markdown for the free text parts, tables, headings and blockquotes, while keeping Org format for its key-value properties and structure other than headings, when those optional parts are used. (Though Markdown's inability to nest Markdown inside HTML elements is a terrible default. HTML semantic elements containing marked up text is basically how I write documentatio…

Have you seen my other comment, where I mention https://github.com/agzam/prisma.el ? Check it out.

Re: Emacs 31: An unofficial guide to Markdown-ts-mode

#87

Post by iLemming »

mplanchard wrote: post #64
remedan wrote: post #6

Earlier quoted context omitted.

Agent Shell connected via ACP to local Claude Code. https://github.com/xenodium/agent-shell

Seconded, agent-shell is my favorite LLM interface bar none

Have you tried https://eca.dev ?

Re: Emacs 31: An unofficial guide to Markdown-ts-mode

#88

Post by BeetleB »

dleslie wrote: post #85
BeetleB wrote: post #84

Earlier quoted context omitted.

> There are other tools that are fast, free, and capable which do not have this problem. You are merely mirroring what I said. > There's good reason that all the new agentic development environments aren't forks of Emacs or NeoVim. And there's nothing wrong with the fact that Emacs will never be the tool people fork for agentic (or IDE, or for any other purpose). That's not a mark against Emacs.

Emacs isn't the best code editor. It isn't the best note taker. It isn't the best document writer. It isn't even a good lisp. What is Emacs the best at these days?

Why are you asking the person who said Emacs isn't the best at any particular thing?

If you want to engage, at least read the comments.

Re: Emacs 31: An unofficial guide to Markdown-ts-mode

#90

Post by iLemming »

mplanchard wrote: post #89
iLemming wrote: post #87

Earlier quoted context omitted.

Have you tried https://eca.dev ?

I haven’t! It seems akin to ACP, is that accurate? Do you recommend it?

No, ECA doesn't work like ACP, it's provider-independent and operates similar to an lsp-server. It is in fact, written by the maintainer of lsp-mode and author of clojure-lsp.

I've tried many different tools for AI tasks in Emacs, eca and gptel remain the bread-and-butter of my workflows.

Post reply on HN