orderless VS glow

orderless. A highly configurable completion style that matches multiple patterns in any order against minibuffer completion candidates.

An example relevant to your list would be some changes many people are taking with their completion framework - using package that leverage core emacs functionality rather than replacing it with a complete package that 'overrides' it. Consult, vertico, orderless and associate packages come to mind here. If you do a bit of a search you'll find plenty of info. Here is a video from Prot on the subject, but there are many others as well. I think Prot actually went on to write his own completion system to overlay native emacs functionality as well.

You didn't mention, so I'll ask, are you using the orderless (https://github.com/oantolin/orderless) completion style?

Fuzzy completion ala Orderless would be awesome: hitting space during completion acts as a pattern separator.

I dunno—I like how Vertico+Counsel feel. I'm not sure how good the support for Orderless and Embark are in Ivy, but I really like how those packages compose so nicely with the Vertico+Consult ecosystem.

In general, you want either orderless or prescient, with my personal preference being the former.

You probably want to investigate completion styles. There are many builtin styles, from basic, which just does prefix completion, on up. But there are also 3rd party styles. One of the most powerful is called orderless. Considering all these styles, there really is a ton of flexibility in how you can get to a completion candidate like some-named-something (some, s-n-s, sns, soso, [a-z]{4}-na, e\b \bs, ...). You can even configure more than one style at a time (and usually do).

Well, I've written some general purpose Emacs packages (orderless and embark) that I use a lot, but I also write Emacs Lisp for one-off tasks.

I like it. Would be nice to see orderless-style (https://github.com/oantolin/orderless) completion, and a config not to enter the directory by narrowing the completion to one, requiring enter to be pressed.

To get started, install Mods and check out some of the examples below. Since Mods has built-in Markdown formatting, you may also want to grab Glow to give the output some pizzazz.

I recently started using markdown in neovim (with an LSP) along with https://github.com/charmbracelet/glow to view markdown / navigate. Does everything I used to use Obsidian for minus the links / graph functionality which I don't really need and it's pretty snappy on an old Lenovo. Very customizable as well.

Yup, those seem to be the key challenges. I've been making good progress on them, but there's plenty more work to do!

On the topic of "AI-generated PRs", I used my tool to file a PR to the `glow` CLI tool. I don't know the go language, so I had aider make the changes to glow.

https://github.com/charmbracelet/glow/pull/502

I've also been able solve a couple of github issues that were file by users by just pasting the issue into my tool... it fixed itself. Links below:

https://github.com/paul-gauthier/aider/issues/13#issuecommen...

https://github.com/paul-gauthier/aider/issues/5#issuecomment...

I'm personally also quite fond of Glow. I use it pretty much every time I touch a markdown file.

Nice idea! I’m excited to check it out. I write a lot of docs in Markdown and this could be a great way to browse them.

Out of curiosity, have you seen glow[0]?

[0] https://github.com/charmbracelet/glow

Charm's Glow is a joy to use, a good example of having the Charm's Bubbletea usage - but from the code perspective, it's a bit difficult to navigate as many code paths are put in the same package

thanks! Yeah all the markdown is handled through glow, which is one fairly awesome tool.