-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR] 'Cycle bullet/checkbox' command #1
Comments
Hello. Thanks for using this plugin. If I implement that feature, I'll probably add a config option as shown below. Case1. Mimicking Obsidian's 'Cycle bullet/checkbox'require("markdown-toggle").setup({
enable_box_cycle_obsidian = true, -- new option
enable_box_cycle = true,
box_table = { "x" },
}) In this case, the cycle would look like this: hoge
↓
- hoge
↓
- [ ] hoge
↓
- [x] hoge
↓
- hoge
↓
- [ ] hoge
↓ Case2. In case of various markup cycles in addition to aboverequire("markdown-toggle").setup({
enable_box_cycle_obsidian = true, -- new option
enable_box_cycle = true,
box_table = { "x", "~", "!" }, -- for cycling between various states
}) Here's how the cycle would work: hoge
↓
- hoge
↓
- [ ] hoge
↓
- [x] hoge
↓
- [~] hoge
↓
- [!] hoge
↓
- hoge
↓
- [ ] hoge
↓ Case3. If you don't want to use the new featurerequire("markdown-toggle").setup({
enable_box_cycle_obsidian = false, -- new option
enable_box_cycle = true,
box_table = { "x" },
}) In this case, the cycle would be like this (same as the current toggle command): hoge
↓
- [ ] hoge
↓
- [x] hoge
↓
- [ ] hoge
↓ In addition, I'm planning to add a NEW config option for 'bullet list' as well. |
I've just implemented the Mimicking Obsidian feature: 4daa991 Please check the latest commit. |
@roodolv
|
I'm glad to hear that. |
Hi :)
Thank you for the wonderful plugin. It's very user-friendly, especially since I regularly use Obsidian.
I have assigned the 'Cycle bullet/checkbox' command to
Ctrl+Enter
in Obsidian. This command has a somewhat unique behavior as described below.I would appreciate it if you could consider this.
The text was updated successfully, but these errors were encountered: