LaTeX
formula evaluations are placed above text rather than overlaid.
A way around this is to use a separate plugin for LaTeX
and disable that feature
in this plugin. Different plugins will have different setups, below are some examples:
{
{ 'ryleelyman/latex.nvim', opts = {} },
{
'MeanderingProgrammer/render-markdown.nvim',
dependencies = { 'nvim-treesitter/nvim-treesitter', 'echasnovski/mini.nvim' },
opts = {
latex = { enabled = false },
win_options = { conceallevel = { rendered = 2 } },
},
},
}
{
{ 'jbyuki/nabla.nvim' },
{
'MeanderingProgrammer/render-markdown.nvim',
dependencies = { 'nvim-treesitter/nvim-treesitter', 'echasnovski/mini.nvim' },
opts = {
latex = { enabled = false },
win_options = { conceallevel = { rendered = 2 } },
on = {
attach = function()
require('nabla').enable_virt({ autogen = true })
end,
},
},
},
}
Note
These plugins can rely on a specific conceallevel
to work properly, which
you will need to configure in this plugin like in the examples above.
Telescope has a special way of previewing files that does not work like a standard buffer: info
Due to this the events this plugin relies on to attach to and render buffers do not get triggered.
Should no longer be an issue on any version of neovim if up to date.
Since telescope
performs several mode change operations to enable previewing and
other nice things like setting marks
when changing buffers there are scenarios
where a markdown
file will not render when it is initially opened through telescope
.
An example of this is when opening a file using live_grep
and default settings.
The issue stems from telescope
running two normal
mode commands in the process
of opening a file. At the time of writing these are:
Something about the way these are done causes the file to appear be opened in insert
mode despite being in normal
mode. Additionally there is no ModeChanged
event
that occurs after this to go back to normal
mode.
Should no longer be an issue when using neovim >= 0.10.0
.
Text that extends beyond available space will can overwrite content.
This is no longer the case as of which-key
v3 release.
Since which-key
interjects when writing commands it can effectively limit the
number of modes available to the user.
This varies by configuration. An example is having the operators
preset enabled
will prevent the user from entering the operator pending mode. Since this mode cannot
be reached this plugin cannot not do anything special in the operator pending state,
since it effectively does not exist.
This is expected behavior by which-key
: ISSUE #534