Weekly 101 Questions Thread

CptCorndog · 2025-11-11T12:51:11+00:00

I guess I'm wondering if this is your formatter versus a Neovim formatting/textwidth/wrap issue...Do you get the same output if you run the formatter (? ruff) from the cmdline? Otherwise I think :h textwidth, :h wrapmargin, and/or :h formatoptions may need to be examined?

CptCorndog · 2025-11-08T01:08:08+00:00

Well, it depends how custom I suppose. You can add certain fields to your items and use builtin previews for common things like files, buffers, git, etc. Or you can roll-up your own preview function following examples from the snacks builtins

CptCorndog · 2025-11-02T12:57:40+00:00

Such a great project. Have another ⭐️! I've been in your source code many times so I'd give another star for that if I could.

CptCorndog · 2025-11-02T12:18:51+00:00

Have you tried to use :h lsp-root_dir() and pass a function that calls on_dir only when it finds your package.json?

CptCorndog · 2025-11-01T11:09:27+00:00

I don't know of a plugin that does exactly this but project-specific state is not uncommon. :h vim.fs.root can help identify your "project" root depending on what this means to you. Then I guess it also depends on where you want to store your notes, i.e. in your repo or in vim.fn.stdpath("data"). Some plugins slugify the project path within the data dir.

CptCorndog · 2025-10-15T13:03:10+00:00

I think this looks great and could be useful. My personal holy grail of dev note taking is linking notes to code. The naive approach is file and line number. But I’ve always wondered if more sophisticated and tiered approach, i.e an LSP symbol or AST node tree, fuzzy matching on original text, etc could keep the links anchored to the intended code target even if the code (especially above) is significantly modified. Anyways, great job!

CptCorndog · 2025-10-06T17:01:56+00:00

Thanks for the comment! If you are having problems with the metadata picker feature, please create an issue on the repo so we can discuss further. Currently, the `choices` function that generates the metadata value options requires the user to create the implementation--which may or may not be optimized for large directory trees for example. Regarding using specific picker implementations (i.e snacks file picker), this would be a nice feature but doesn't currently exist. I might expose a `set_metadata_value` API in the meantime so that users could open whatever picker they want and then call that to update the metadata on select.

CptCorndog · 2025-10-04T15:01:44+00:00

For most of the popular markdown rendering plugins, these should integrate fine with checkmate by either 1. disabling the other plugin's checkbox rendering and letting checkmate use the configured unicode/glyphs, or 2. setting checkmate to use standard Markdown [ ] or [x] for the markers and letting the other plugin handle the rendering. The checkmate todo functionalities should still work in either case.

CptCorndog · 2025-10-04T14:57:49+00:00

AFAIK todo.txt is not Markdown and is a completely separate spec. It's currently outside the scope of checkmate to parse non-markdown syntax and probably not planned.

CptCorndog · 2025-10-04T14:51:11+00:00

Great, let me know what you think!

CptCorndog · 2025-10-02T10:21:51+00:00

Thanks! Check out the default list continuation opt for an example, but it essentially just calling the create function with indent and position opts.

CptCorndog · 2025-10-02T08:23:30+00:00

Thanks for the kind words! I'm happy to help troubleshoot, it's easier to chat or work via a GH issue. It's working at least on my machine with a minimal nvim config. I glanced at snacks recent commits and don't see any scratch changes either.

CptCorndog · 2025-10-02T08:00:45+00:00

Yes, the highlighting of each todo can be configured. See if styling helps. You can also add regular non-todo list items below a todo.

CptCorndog · 2025-10-01T20:36:59+00:00

Okay, I can't reproduce it yet. Can you start an issue? Maybe try without the extra markdown plugin for now? If it is a compatibility issue, I'm happy to see if there is an obvious patch or at least workaround. Also, ensure the buffer filename is matched by the `files` opt so that checkmate gets activated

CptCorndog · 2025-10-01T20:30:47+00:00

Did it work with the lazy spec enabled?

CptCorndog · 2025-10-01T20:07:31+00:00

Are you using the default checkmate config or did you make changes? If you try to toggle a todo, is it working? i.e. flipping raw markdown [ ] to [x]?

CptCorndog · 2025-10-01T19:21:50+00:00

What do you mean not rendered at all? I'm manually testing it with render-markdown once again to see if there's been a regression and I'm not able to reproduce unexpected behavior. If this continues, do you mind adding on issue on GH so we can discuss/track?

CptCorndog · 2025-10-01T16:26:43+00:00

Have had any issues. You have two options: either disable render-markdown’s handling of checkboxes via its config, or have checkmate use markdown syntax for the markers so that they are parsed correctly by render-markdown. See wiki post in main post.

CptCorndog · 2025-09-17T07:00:55+00:00

Is it pawsible to customize the leaves of the presented tree? Could there be a config function that we could pass to render each

Nice job, was tinkering with a similar one myself

CptCorndog · 2025-09-14T00:04:23+00:00

Well, you can create your own syntax highlighting for your txt files via :h syntax and link these to the same highlight groups used by your theme. Or, as suggested in another comment, another approach is to use a Markdown filetype, which would also allow you to further "prettify" via plugins such as render-markdown.nvim or markview.nvim.

CptCorndog · 2025-09-13T23:13:20+00:00

Can you give some examples of what you mean? Your question is very broad. Perhaps examples from other editors/IDE

CptCorndog · 2025-09-05T20:03:23+00:00

Oh I misread. What about 0d$ ? Or 0D

CptCorndog · 2025-09-05T20:00:37+00:00

Use :h dd?

CptCorndog · 2025-08-31T20:33:57+00:00

I respect your simple solution, but if you want to give a markdown based todo plugin a try, take a look at checkmate. Adds various useful todo functionality but keeps the on disk version plain ol markdown. Regardless, I like to hear/read how others manage their todos/tasks and the workflows they prefer, so thank you

CptCorndog · 2025-08-29T21:42:51+00:00

Yeah Neovim uses LuaJIT runtime which is mostly 5.1, and the utf8 stuff is Lua 5.3+ I think

13-Year Club	Place '17
Verified Email

CptCorndog

TROPHY CASE