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

61–70 of 92 posts

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

#61

Post by dleslie »

BeetleB wrote: post #54
dleslie wrote: post #42

Earlier quoted context omitted.

Emacs makes many opinionated choices about defaults; if it didn't, it would launch to little more than an elisp REPL by default. What's important is that _you can change it_. Good defaults ensure that Emacs doesn't repel new users and casual users and users who are not interested in fiddling. And this isn't a matter of color theme default, or font default; this is a shipped feature that _does not function_ without ch…

> if it didn't, it would launch to little more than an elisp REPL by default. I'm confused. Have things changed? The scratch buffer it starts with is for writing elisp. > this is a shipped feature that _does not function_ without changes to the defaults! Do you know how many shipped features come with Emacs that don't function without changes to defaults? A huge number of them! Stuff like hippie-expand, ibuffer, etc.…

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 thirty years now. I don't recommend it to new users.

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

#62

Post by taude »

iLemming wrote: post #55
iLemming wrote: post #27

Earlier quoted context omitted.

I love Org-mode and use it for many things - the outline format is great, even for some unexpected cases - Jira tickets, Slack, Reddit and HN threads, etc. But of course, hard to escape Markdown these days, so I burned some tokens to implement this https://github.com/agzam/prisma.el

For example, I just added the ability of seamlessly copy&pasting between two formats (prisma-yank-mode) - if the source was a markdown, and you're pasting it into org - it will convert and vice versa. And if you really need to insert it verbatim - you just call it with C-u arg.

That's a neat trick. I know about org-md for exporting generally to a markdown file but going in/out via buffers is useful.

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

#63

Post by mplanchard »

dleslie wrote: post #42
BeetleB wrote: post #41

Earlier quoted context omitted.

I speak only for myself and not the Emacs team, but ... IMO it shouldn't do this by default - unless there is a clear "winner" among all the choices. IIRC, for eglot I had to install a Python language server. There are a bunch of them. Why would I want it to pick one by default? I don't know if Emacs will ever have an IDE with TS and LSP working "out of the box" without some configuration. From my experience with Egl…

Emacs makes many opinionated choices about defaults; if it didn't, it would launch to little more than an elisp REPL by default. What's important is that _you can change it_. Good defaults ensure that Emacs doesn't repel new users and casual users and users who are not interested in fiddling. And this isn't a matter of color theme default, or font default; this is a shipped feature that _does not function_ without ch…

I think eglot often just works now. I recently started doing c++ stuff, and it just detected clangd and I was off to the races with no config. Same with rust-analyzer for rust projects.

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

#64

Post by mplanchard »

remedan wrote: post #6
edgyquant wrote: post #4

What are people’s workflows for using eMacs with generative coding? I’m trying to get a workflow where I can generate code and approve it like a PR (maybe leave comments for a next round of generation) but I’m new to eMacs and the ai coding package isn’t working with the latest eMacs

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

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

#65

Post by mplanchard »

internet_points wrote: post #40
edgyquant wrote: post #14

Earlier quoted context omitted.

It’s just called ai-code I’m new to eMacs so this popped up but had a bunch of issues I was trying to debug https://github.com/tninja/ai-code-interface.el

Never heard of that one. The most popular ways for agent stuff seems to be https://github.com/xenodium/agent-shell , or just opening a terminal in emacs and using claude code. If you want to run it through an emacs terminal, consider using https://github.com/dakra/ghostel#ghostel (or vterm, or eat)

Thanks for posting the ghostel link, I hadn’t heard of it. Excited to try it out and see how it compares to vterm

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

#66

Post by mplanchard »

cpach wrote: post #52

“You probably heard of this new markdown-ts-mode and decided to check it out.” Uhm, no, I haven’t. Why should I care if the Markdown mode uses Treesitter or not…? Does it affect the performance or UX somehow?

One option would be to read the section of the linked article talking about features: https://rahuljuliato.com/posts/markdown-ts-mode-emacs-31#a-q...

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

#67

Post by BeetleB »

dleslie wrote: post #61
BeetleB wrote: post #54

Earlier quoted context omitted.

> if it didn't, it would launch to little more than an elisp REPL by default. I'm confused. Have things changed? The scratch buffer it starts with is for writing elisp. > this is a shipped feature that _does not function_ without changes to the defaults! Do you know how many shipped features come with Emacs that don't function without changes to defaults? A huge number of them! Stuff like hippie-expand, ibuffer, etc.…

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 those!

> I don't recommend it to new users.

"New" to what? In general, I don't recommend Emacs unless someone shows genuine curiosity. I always tell people "Give me any task, and I'll find a better tool than Emacs." And "If you want to get up and running quickly for your task, Emacs is not a good choice." Followed by "What makes Emacs worthwhile is you get it all in one package where they can interact with one another." And "It's a lifelong journey."

Nevertheless, some not technically savvy users do use Emacs today because they needed help editing files on a remote machine and I couldn't teach vim because Emacs was all I knew :-)

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

#68

Post by skydhash »

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…

> I always tell people "Give me any task, and I'll find a better tool than Emacs." And "If you want to get up and running quickly for your task, Emacs is not a good choice." Followed by "What makes Emacs worthwhile is you get it all in one package where they can interact with one another." And "It's a lifelong journey."

That is the proper response. These tools are designed for someone that does need them as they are, not for someone that just need some tools. Software like vim and emacs are in fact a whole workshop that you need to make your own. If you just want a tool, there are better software out there, but people that usually go for emacs wants a workspace, not just one tool.

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

#69

Post by geokon »

taude wrote: post #11

One of the biggest reason I've stopped using Emacs, and I was a pretty heavy user before was that org-mode files weren't fully native Markdown files, which caused annoying friction when collaborating with others. It would be interesting for me to have a new markdown-centric org-mode thing. I'd love to vibe lisp to customize my workflows, and I don't totally love Obsidian, which is what I've setup and configured now.…

Asciidoc is a nice middle ground between the full suit of tools you get in Orgmode and bare Markdown.

To me Orgmode (after years of using it) feels like .docx. A weird poorly specified format that is only fully editable from one editor. Granted you ran read it from anywhere, but you won't want to edit it from anywhere other than Emacs. That feels like it defeats the point of using markup - which is supposed to be editable/usable from anywhere, even Notepad.

.adoc is usually sufficient (the only part I miss is tangle). Lots of options to specify at the top of a document like the images directory, or the CSS file to use, line SVG on HTML export etc. (which Markdown lacks). But the asciidoc converter runs from the command line or from code ( I write .adocs and convert them in Clojure). So you're less married to your editor.

Ideally there'd be some markup that's specified with a regex of PEGs or something that you could easily make a parse for in any context. I thought djot would be that, but it looks like making a grammar is secondary for them. I hope some day one could navigate to markup file in the browser and they'd automatically render with your own specified CSS.

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

#70

Post by [deleted] »

ggm wrote: post #58

So I can get bold at a cost of shift* to get the star. Or I can do ESC enable-this-mode-option and then press a single key. I'm struggling with this. If it's cheaper in keystrokes to type the codes inline why enable the mode? This isn't a vi vs emacs hate thing, It's a key count efficiency thing. I don't see the motivation even if translated to minimum prefix TAB complete terms. Its like 20x more presses.

[deleted]
Post reply on HN