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

31–40 of 92 posts

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

#31

Post by [deleted] »

femiagbabiaka wrote: post #30
dleslie wrote: post #28

Earlier quoted context omitted.

Tree sitter support is half baked in the same way official LSP support is, only kind of worse. Eglot won't help you get your system ready for LSP work, it will only avail itself if what's there. It doesn't even auto detect and configure that, either. There's no user prompting, so you'll have to read the docs to know that this even needs to be done. Similarly, tree sitter support doesn't include the grammars! And thos…

In Emacs 31 none of what you’re saying is true. Grammars auto install and setting them up is easy. https://www.reddit.com/r/emacs/comments/1utghab/treesitter_s...

[deleted]

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

#32

Post by dleslie »

femiagbabiaka wrote: post #30
dleslie wrote: post #28

Earlier quoted context omitted.

Tree sitter support is half baked in the same way official LSP support is, only kind of worse. Eglot won't help you get your system ready for LSP work, it will only avail itself if what's there. It doesn't even auto detect and configure that, either. There's no user prompting, so you'll have to read the docs to know that this even needs to be done. Similarly, tree sitter support doesn't include the grammars! And thos…

In Emacs 31 none of what you’re saying is true. Grammars auto install and setting them up is easy. https://www.reddit.com/r/emacs/comments/1utghab/treesitter_s...

Well that's a nice change; I'm still on Emacs 30.

But note that this is not the default. Users have to enable that behaviour, and know to enable it. That's a bad default.

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

#33

Post by kodoman »

iLemming wrote: post #29
kodoman wrote: post #12

Earlier quoted context omitted.

What is wrong with markdown mode? Is it that you would rather do the org agenda or calendar via md rather then org? I do understand that if that is the case.

> What is wrong with markdown mode? Nothing. It's just not Org-mode, and thus many great features of Org just not possible - sparse tree search; timestamps with built-in calendaring features; outline features like narrow-to-subtree; editing the subtree in an indirect buffer; executable code blocks; embedded LaTeX snippets; real tables with spreadsheet-like capability; checkbox statistics cookies - [/] and [%]; org-so…

Else where in this thread you can see my argument is that all org-mode features such as calendar dates, todo's, take your pick could be implemented separate to and utilize markdown (or any other format) for actually rending to. I am familiar with org mode but dislike how it sometimes pushes against simply using elisp for things like setting up todo nodes and possible todo values. couple that with the fact that one could in theory just render this all out to markdown instead and come up with some way to render todos into md.

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

#34

Post by tom_ »

jwr wrote: post #26
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

I use cLaude cOde in my eMacs (through ghostel, which is unbelievably great!) to generate code :-) I then use mAgit to review it.

The iPhone autocorrects it to eMacs... it's so annoying.

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

#36

Post by Jtsummers »

kodoman wrote: post #33
iLemming wrote: post #29

Earlier quoted context omitted.

> What is wrong with markdown mode? Nothing. It's just not Org-mode, and thus many great features of Org just not possible - sparse tree search; timestamps with built-in calendaring features; outline features like narrow-to-subtree; editing the subtree in an indirect buffer; executable code blocks; embedded LaTeX snippets; real tables with spreadsheet-like capability; checkbox statistics cookies - [/] and [%]; org-so…

Else where in this thread you can see my argument is that all org-mode features such as calendar dates, todo's, take your pick could be implemented separate to and utilize markdown (or any other format) for actually rending to. I am familiar with org mode but dislike how it sometimes pushes against simply using elisp for things like setting up todo nodes and possible todo values. couple that with the fact that one co…

Markdown didn't even exist when org-mode was first developed and released with many of the features you describe. But also, once you start extending markdown to support all these things you start getting something that's not markdown, it's markdown-based but something distinct since you'd rapidly lose compatibility with other markdown tools if you start incorporating custom annotations into it.

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

#37

Post by skydhash »

kodoman wrote: post #25
taude wrote: post #22

Earlier quoted context omitted.

That's actually not a bad mindset, especially when lisp can be vibed so easily. I could actually see myself building out my own library that does the things I want over markdown. - have it look through all md files in a directory, collect all the todos into a main view - look for items tagged with a date - support customer tagging, and provide workflow exports for each one... - behind the scenes git management for fi…

My thinking was lean into lisp lists rather then the actual rendered format, so that instead of a text buffer (although you could always open up a text buffer that is the lisp list) you have a list that you can use normal elisp functions that is bindable to keys and highly customizable and your only really building fairly simple elisp machinery on top and you can just use an alist (though you could use a plist I thin…

You might just as well require a sqlite db as the persistence layer. Emacs has always been about using plain text files as both data and interface while lisp is the control mechanism.

That’s why you got org files and a handful of lisp functions to turn them into a living documents. Using lists take that aspect away while markdown is just not that good to serve such a role.

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

#38

Post by kodoman »

Jtsummers wrote: post #36
kodoman wrote: post #33

Earlier quoted context omitted.

Else where in this thread you can see my argument is that all org-mode features such as calendar dates, todo's, take your pick could be implemented separate to and utilize markdown (or any other format) for actually rending to. I am familiar with org mode but dislike how it sometimes pushes against simply using elisp for things like setting up todo nodes and possible todo values. couple that with the fact that one co…

Markdown didn't even exist when org-mode was first developed and released with many of the features you describe. But also, once you start extending markdown to support all these things you start getting something that's not markdown, it's markdown-based but something distinct since you'd rapidly lose compatibility with other markdown tools if you start incorporating custom annotations into it.

I really don't dislike org-mode and respect it and you are right that org-mode was first.

The point is that markdown could have todo's or virtually any other aspect that org mode supports put into it without changing the markdown standard and layer org functionality and various features on top for example todo's could simply be italic's starting with todo: so `# todo:todo hello` could be parsed as a todo entry marked as todo.

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

#39

Post by scoops_ »

sebastianavina wrote: post #17
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

I use windows 11, wsl2, WezTerm. emacs -nw directly on the shell. its like working on a linux computer, but from windows. I run vterm inside emacs, and claude code inside vterm. I have special commands for extracting file routes, and flow between dired and magit. Everything runs like magic. I also have copilot-chat and copilot-mode installed. From time to time I use it to review what claude has done, or to chat a lit…

I’m trying to use a similar workflow, but when I attempt to use Claude code in vterm, I have issues.

My use case is resuming a session and not being able to scroll back to the past history. Otherwise if I start a new session, it works fine.

It’s probably related to me being on an old version of vterm, but I’m just wondering if you ever have come across this.

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

#40

Post by internet_points »

edgyquant wrote: post #14
kreyenborgi wrote: post #5

Earlier quoted context omitted.

Which AI coding package? Agent-shell? Gptel-agent?

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)
Post reply on HN