You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just downloaded and started using this plugin today. This is a pretty slick plugin, and I think I'll be getting a lot of use out of it, so thanks!
When I started using this plugin, I would get this annoying warning that Autocommands were nested too deep. It doesn't seem to cause a major issues, but it drives OCD people like me crazy :)
Looking through the plugin, I can see where you set an auto command for "FileType todo" to call the VimTodoListsInit function. In the VimTodoListsInit function the first line issues a "set filetype=todo", creating the infinite loop that triggers the autocommand nesting error.
I fixed this in my local plugin with a quick and dirty hack (probably not the best way to do it, but it works for me) by:
Rename the VimTodoListsInit function to VimTodoListsPostInit
Delete the "set filetype=todo" from the VimTodoListPostsInit function
Create a new function named VimTodoListsInit that ONLY sets filetype=todo
Change the "autocmd FileType todo call VimTodoListsInit" to call VimTodoListsPostInit
I'm sure there is a better way to fix this, but please find my work around attached. vim-todo-lists.txt
The text was updated successfully, but these errors were encountered:
Jef-coder
pushed a commit
to Jef-coder/vim-todo-lists
that referenced
this issue
Apr 8, 2021
Closesaserebryakov#37, Closesaserebryakov#38
Correct the issue with the autocommand infinite loop. Smart indent
breaks the indenting, setlocal nosi. Added the option to have a date
appended when an item is complete (let g:VimTodoListsDateCompleteEnable
= 1 in .vimrc).
I just downloaded and started using this plugin today. This is a pretty slick plugin, and I think I'll be getting a lot of use out of it, so thanks!
When I started using this plugin, I would get this annoying warning that Autocommands were nested too deep. It doesn't seem to cause a major issues, but it drives OCD people like me crazy :)
Looking through the plugin, I can see where you set an auto command for "FileType todo" to call the VimTodoListsInit function. In the VimTodoListsInit function the first line issues a "set filetype=todo", creating the infinite loop that triggers the autocommand nesting error.
I fixed this in my local plugin with a quick and dirty hack (probably not the best way to do it, but it works for me) by:
I'm sure there is a better way to fix this, but please find my work around attached.
vim-todo-lists.txt
The text was updated successfully, but these errors were encountered: