Skip to content
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

:Toc does not work with other quickfix list plugins #603

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

KSR-Yasuda
Copy link
Contributor

:Toc does not work with other quickfix list plugins such as itchyny/vim-qfedit:
it checks location list line validity, so vim-markdown's modified TOC lines are dropped.

So dropped TOC location list modifications.

@KSR-Yasuda KSR-Yasuda force-pushed the bugfix/Toc branch 3 times, most recently from f8af808 to 41c10cb Compare September 28, 2022 02:46
@KSR-Yasuda KSR-Yasuda force-pushed the bugfix/Toc branch 3 times, most recently from 5b745ad to d7f9b07 Compare September 28, 2022 03:27
@KSR-Yasuda
Copy link
Contributor Author

For :Insert{,N}Toc, added preceding-# removal again.

Instead, in :Toc, add # prefix to indicate heading level
(Originally it added spaces, though, it is not readable with location list file path).

@KSR-Yasuda
Copy link
Contributor Author

Also tried to fix tests, though,
I could not handle :Toc window size (test/toc-autofit.vader).

@KSR-Yasuda
Copy link
Contributor Author

Fixed test/toc-autofit.vader anyhow, however,
now g:vim_markdown_toc_autofit setting would not work as expected:

as the same of normal location list window,
the former fix shows file name and line / column position before heading text.

So current :Toc lines come to be much longer than autofit window width.

@KSR-Yasuda
Copy link
Contributor Author

For :Insert{,N}Toc, added preceding-# removal again.

Instead, in :Toc, add # prefix to indicate heading level (Originally it added spaces, though, it is not readable with location list file path).

Changed heading level indication to N# (e.g. 3# for lv.3).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant