Skip to content

Update installation instruction for 'ocaml.nvim.#3421

Open
Lucccyo wants to merge 1 commit into
ocaml:mainfrom
Lucccyo:main
Open

Update installation instruction for 'ocaml.nvim.#3421
Lucccyo wants to merge 1 commit into
ocaml:mainfrom
Lucccyo:main

Conversation

@Lucccyo
Copy link
Copy Markdown

@Lucccyo Lucccyo commented Dec 17, 2025

No description provided.

@Lucccyo Lucccyo changed the title add ocaml.nvim in the setup getting started Update installation instruction for 'ocaml.nvim. Dec 17, 2025
Comment thread data/tutorials/getting-started/2_00_editor_setup.md Outdated
Comment thread data/tutorials/getting-started/2_00_editor_setup.md Outdated
Comment on lines 164 to 166
There are two main ways to install and manage LSP servers.
- A newer, more recommended way is to use the new Neovim LSP API for versions newer than v0.11.0 via `vim.lsp`.
- A more traditional way is to use `nvim-lspconfig`. For more info, `kickstart.nvim` has a great example setup.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we still mention these ? Are they needed for the new plugin to work ? If not we should at least put the new plugin information first.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It can be useful as it removes the need to configure the lsp yourself (it provides configuration files ). However this is generic to lsp so it might not need to be included in the ocaml.nvim documentation.


### Installing `ocaml.nvim`

You can install this plugin easily using [lazy.nvim](https://github.com/folke/lazy.nvim) by adding the following to your `ocaml.nvim` setup.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is everyone expected to use lazy.nvim ? If not we should also provide standalone installation instructions.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The majority of existing Neovim plugins provide only installation instructions with lazy.nvim.
What do you think @maiste?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree most of the NeoVIM plugins I know tend to provide the lazy.nvim installation. I don't recall any plugin providing the standalone installation. The NeoVIM ecosystem is still maturing as NeoVIM is not yet stable. They are starting to provide a built-in package manager but it is not yet mature (maybe at some built it will be the default).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's also the new built-in plugin manager (inspired by mini) that's going to be the standard going forward. Generally, I think it's better to at least mention it as well.

Comment thread data/tutorials/getting-started/2_00_editor_setup.md Outdated
Comment thread data/tutorials/getting-started/2_00_editor_setup.md Outdated
```lua
require("lazy").setup({
{"tarides/ocaml.nvim",
config = function()
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the simple instruction is:

require('lazy').setup({
  {"tarides/ocaml.nvim"},
  opts = {
    -- add your options here, or leave empty
    -- to use the default one
 },
})

@sabine
Copy link
Copy Markdown
Collaborator

sabine commented Feb 3, 2026

@Lucccyo @voodoos are you happy with this and can we merge?

@bbatsov
Copy link
Copy Markdown
Contributor

bbatsov commented Feb 13, 2026

My two cents are that https://github.com/tarides/ocaml.nvim already has great docs, so probably we should just point people to it and not repeat so much of the instructions. This reduces the likelihood that they would drift apart over time.

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.

6 participants