vim-tohtml Activity
Official development repository for Vim's builtin TOhtml plugin
Brought to you by:
fritzophrenic
Activity for vim-tohtml
-
fritzophrenic modified ticket #28
Investigate using vim9 vimscript for speed improvement
-
Fake soft wrap to support fancy line wrapping options
-
See also https://sourceforge.net/p/vim-tohtml/issues/36/ (closed as duplicate)
-
Duplicate of https://sourceforge.net/p/vim-tohtml/issues/7/, closing.
-
See also #36 (closed as duplicate)
-
Some users do not like default font size
-
Duplicate of #7, closing.
-
Investigate global font size specifier
-
Investigate more than 4 diff windows
-
Check that synconcealed() changes don't break anything
-
Allow changing color of links
-
Some users do not like default font size
-
Improvement: look into :defer-based cleanup
-
Check for impact of less restricted group names
-
capture multiple windows not in diff mode
-
terminal window colors not supported by TOhtml
-
terminal window colors not supported by TOhtml
-
Note: Neovim cannot currently support vim9script, so maybe hold off on this until final solution is reached regarding vim9sript/Neovim. I guess there is some sort of compiler that might help in the future? https://github.com/vim/vim/pull/13039#issuecomment-1712859783
-
Update changelog with released Vim version
-
Added tag vim9.0_v2 for changeset be199e50007a
-
"hi link" not supported for top-level highlight groups
-
Tests added (all passing) in https://sourceforge.net/p/vim-tohtml/code/ci/be199e50007a5879663e1c0a88cf576a6a5db55f/
-
Add tests for color rules with linked highlight
-
Edge browser can't paste from <pre> sections correctly
-
This is overcome by events. It was written back before Edge became a Chromium-based browser. Testing shows that paste works fine in Edge now. Newlines are preserved and all text is pasted. In Google Docs, the pasted text even has formatting. Tested on docs.google.com and https://www.editpad.org/tool/online-rich-text-editor. Settings were entirely default: <meta name="settings" content="use_css,no_foldcolumn,prevent_copy=,use_input_for_pc=none"> Microsoft Edge Version 116.0.1938.69 (Official build)...
-
Need to write test, but fixed in https://sourceforge.net/p/vim-tohtml/code/ci/24672ba3a252c18ac1564de06cb7bc31205ea256/
-
Fix linked color groups
-
https://github.com/vim/vim/issues/1725 Github issue to go along with the vim_dev thread above.
-
Use tags file to allow creating links
-
Diff filler missing for added lines at bottom of file comparison
-
Fixed in https://sourceforge.net/p/vim-tohtml/code/ci/9cc72cb8d8e3/ and tests added in https://sourceforge.net/p/vim-tohtml/code/ci/e34d00fa1368842d765d0bdc1619ac6753b4361d/
-
Add tests for diff filler
-
Avoid extra eval while building FoldColumn
-
Improve URL/link detection
-
Fixed in https://sourceforge.net/p/vim-tohtml/code/ci/a173aba181a06fdec23526fba7cec44b6549b147/ and https://sourceforge.net/p/vim-tohtml/code/ci/9fc6fe66b5dde5b5017c3d1a4716794e258c1d6a/
-
Fixed in https://sourceforge.net/p/vim-tohtml/code/ci/a173aba181a06fdec23526fba7cec44b6549b147/
-
Use heredoc-style variable assignment
-
Fixed in a173aba181a06fdec23526fba7cec44b6549b147
-
Add vnu.jar test dependency and saved test outputs to .hgignore
-
Fix test failures introduced by preventcopy changes
-
Refactor string assignment and concatenation
-
Add diff filler if needed at end of buffer
-
Change default for g:html_use_input_for_pc
-
update to new Vim license (RIP Bram)
-
warn if using deprecated g:use_xhtml
-
Diff filler missing for added lines at bottom of file comparison
-
Note: investigation shows it happens any time there are new lines at the end of the file. It doesn't matter if the last line has changed. It also doesn't matter which side of the diff has the new lines.
-
Use CSS generated content for diff filler
-
Check for impact of less restricted group names
-
Especially see: virtual text! Probably this should be a new candidate for the "uncopyable text" feature.
-
This ticket is in progress but not yet complete as all options are not covered yet. Need to add additional tests to testdir, which only contains tests for newly added stuff and bugfixes at the moment.
-
Improvement: look into :defer-based cleanup
-
https://github.com/vim/vim/blob/master/runtime/doc/textprop.txt
-
Some users do not like default font size
-
Allow changing color of links
-
Update changelog for pre-release updates
-
Added tag vim9.0_v1 for changeset 502dd2d4f221
-
Removed tag vim9.0_v1
-
Typo in variable name
-
Fixed in vim9.0_v1 by including changes from Vim repo on github, fixing bugs, and adding tests
-
Added tag vim9.0_v1 for changeset ac9f545b2183
-
Update version description
-
Add tests for html_no_modeline and html_no_links
-
Fix html_no_doc in diff mode and add test
-
Pull in changes from upstream Vim repository, update version
-
Typo in variable name
-
Diff filler missing for added lines at bottom of file comparison
-
"hi link" not supported for top-level highlight groups
-
Check if any multiline conceal logic to remove
-
Check for "syn foldlevel" impact
-
Add support for text properties
-
Investigate using vim9 vimscript for speed improvement
-
Might be some relevant info in this discussion: https://groups.google.com/forum/#!topic/vim_dev/gCWZsXVUta0
-
As I responded via email: If there's a way to autodetect the color profile that would probably be best. Although we could leave that to a plugin if it is complicated or involves invoking a bunch of shell commands. I've done something like that before with a plugin on Windows to detect all the supported file encodings on the current system and add mappings for them to the file encoding logic. ( https://www.vim.org/scripts/script.php?script_id=3316 ) For this sort of thing, rather than an argument...
-
As I responded via email: If there's a way to autodetect the color profile that would probably be best. Although we could leave that to a plugin if it is complicated or involves invoking a bunch of shell commands. I've done something like that before with a plugin on Windows to detect all the supported file encodings on the current system and add mappings for them to the file encoding logic. (https://www.vim.org/scripts/script.php?script_id=3316) For this sort of thing, rather than an argument to...
-
cterm color code mappings are not correct
-
Use heredoc-style variable assignment
-
Update BitBucket references in README.md to new locations
-
URLs with embedded syntax highlighting convert to malformed link
-
I think I’ll need to rework how the links are processed if embedding formatting within the links is needed so this won’t be easy. Right now IIRC it’s just a simple :substitute command that runs after the conversion is done.
-
Upload attachments from original issue.
-
Convert BitBucket references to SourceForge
-
Bram Moolenaar committed [41d34c]
updated for version 7.0001
-
Various changes
-
updated for version 7.0018
-
updated for version 7.0020
-
updated for version 7.0023
-
updated for version 7.0021
-
updated for version 7.0 dev
-
updated for version 7.0019
-
updated for version 7.0 dev
-
updated for version 7.0074
-
updated for version 7.0052
-
updated for version 7.0128
-
updated for version 7.0 development
-
updated for version 7.0 development
-
updated for version 7.0 development
-
updated for version 7.0163
-
updated for version 7.0e02
-
updated for version 7.1a
1 >
