Hey, nice project, any way to configure the background color scheme?

Description

The reason is

• jobstart("mytask") runs the task in shell.
• jobstart({ "mytask" }) runs the task directly in the operative system.

That means if you are defining your PATH in the shell, it won't be available, like it's the case on termux. This provokes termux can't find the executable.

Possible solutions

Option 1

• Let's try to run it without {}. Windows shouldn't be stupid enough to spawn a shell process. Ideally neovim takes care of it.

Option 2

Use this option if 1 don't do the trick.

• Instead of running jobstart directly, create a wrapper, so we can choose one or the other depending the OS.
• That way we could run directly on windows, and on shell on UNIX.

I'm noticing that the Markmap commands cannot run in Neovim when the filename contains spaces.
Additionally, a notification would be beneficial to easily spot problems.

Docs says MarkmapWatch:
Unlike |MarkmapOpen|, this command will update the
markmap in real time when changes are made to
the markdown file.

However, changes are displayed only after save operation :w

Would be better to reflect changes in realtime, for example, like markdown-preview plugin does - https://github.com/iamcco/markdown-preview.nvim

@Zeioth I wonder if it would make sense, instead of tracking the last execution over a grace period to rather capture the buffer that is currently served and monitor the last write time. Then go and reset the grace period when the buffer was recently written, as one could assume that you are still working on the document. I haven't looked up what the default grace period is but serving just randomly stopped after ~1h when I was still editing the document.

open and watch currently don't work anymore. I suspect an issue with the temp path, that could've been introduced in d995509. When you run MarkmapWatch it creates a file named --watch in the cwd. This could be because no default opts are provided. So if you don't explictly configure the paths in your options it will lead to a "" situation.

It is currently possible to launch markmap from any buffer regardless of filetype. There should be something that guards vim.bo.filetype == "markdown" and just do nothing if current file is not of type markdown.

Am I getting annoying yet? 😂

Environment

Windows 10: 10.0.19045

NVIM v0.9.4
Build type: RelWithDebInfo
LuaJIT 2.1.1696883897

Checkhealth

markmap: require("markmap.health").check()

markmap.nvim ~
- Neovim Version: v0.9.4
- OK Using stable Neovim >= 0.8.0
- OK `git` is installed: Used for core functionality such as cloning markmap.nvim
- OK `node` is installed: Used for core functionality such as running markmap-cli
- WARNING `yarn` is not installed: Used to install markmap-cli. This operation can also be performed using npm instead, or even manually. See README.md for more info:/nhttps://github.com/Zeioth/markmap.nvim
- OK `markmap` is installed: Used to for the main functionality of the plugin. markmap-cli must be executable in a terminal.

Swapping markmap with markmap.cmd in

https://markmap.js.org/docs/magic-comments