Archives
/
zk-nvim
mirror of https://github.com/mickael-menu/zk-nvim
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
main
user-commands
feature/initial
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'e2b6d62b18'
${ noResults }
zk-nvim/doc/zk.txt

493 lines
21 KiB
Plaintext
Raw Blame History

zk.txt
================================================================================
CONTENTS *zk-contents*
1. zk-nvim............................................................|zk-zk-nvim|
1.1. Requirements............................................|zk-requirements|
1.2. Installation............................................|zk-installation|
1.3. Setup..........................................................|zk-setup|
1.3.1. Notebook Directory Discovery......|zk-notebook_directory_discovery|
1.4. Getting Started......................................|zk-getting_started|
1.5. Built-in Commands..................................|zk-built-in_commands|
1.6. Custom Commands......................................|zk-custom_commands|
1.7. High-level API........................................|zk-high-level_api|
1.8. API..............................................................|zk-api|
1.9. Pickers......................................................|zk-pickers|
1.10. Example Mappings...................................|zk-example_mappings|
2. Miscellaneous................................................|zk-miscellaneous|
2.1. Syntax Highlighting Tips....................|zk-syntax_highlighting_tips|
2.2. nvim-lsp-installer................................|zk-nvim-lsp-installer|
2.3. Telescope Plugin....................................|zk-telescope_plugin|
================================================================================
ZK-NVIM *zk-zk-nvim*
Neovim extension for the `zk` (https://github.com/zk-org/zk) plain text note-taking assistant.
--------------------------------------------------------------------------------
REQUIREMENTS *zk-requirements*
* Neovim >= 0.6.0
* `zk` >= 0.9.0
--------------------------------------------------------------------------------
INSTALLATION *zk-installation*
Via packer.nvim (https://github.com/wbthomason/packer.nvim)
>
use("zk-org/zk-nvim")
<
Via vim-plug (https://github.com/junegunn/vim-plug)
>
Plug "zk-org/zk-nvim"
<
To get the best experience, it's recommended to also install either Telescope (https://github.com/nvim-telescope/telescope.nvim), fzf (https://github.com/junegunn/fzf), or mini.pick (https://github.com/echasnovski/mini.nvim/blob/main/readmes/mini-pick.md).
--------------------------------------------------------------------------------
SETUP *zk-setup*
>
:warning: This plugin will setup and start the LSP server for you, do not call `require("lspconfig").zk.setup()`.
<
>
require("zk").setup()
<
The default configuration
>
require("zk").setup({
-- can be "telescope", "fzf", "fzf_lua", "minipick", or "select" (`vim.ui.select`)
-- it's recommended to use "telescope", "fzf", "fzf_lua", or "minipick"
picker = "select",
lsp = {
-- `config` is passed to `vim.lsp.start_client(config)`
config = {
cmd = { "zk", "lsp" },
name = "zk",
-- on_attach = ...
-- etc, see `:h vim.lsp.start_client()`
},
-- automatically attach buffers in a zk notebook that match the given filetypes
auto_attach = {
enabled = true,
filetypes = { "markdown" },
},
},
})
<
Note that the `setup` function will not add any key mappings for you.
If you want to add key mappings, see the example mappings (#example-mappings).
NOTEBOOK DIRECTORY DISCOVERY *zk-notebook_directory_discovery*
When you run a notebook command, this plugin will look for a notebook in the following places and order:
1. the current buffer path (i.e. the file you are currently editing),
2. the current working directory,
3. the `$ZK_NOTEBOOK_DIR` environment variable.
We recommend you to export the `$ZK_NOTEBOOK_DIR` environment variable, so that a notebook can always be found.
It is worth noting that for some notebook commands you can explicitly specify a notebook by providing a path to any file or directory within the notebook.
An explicitly provided path will always take precedence and override the automatic notebook discovery.
However, this is always optional, and usually not necessary.
--------------------------------------------------------------------------------
GETTING STARTED *zk-getting_started*
After you have installed the plugin and added the setup code to your config, you are good to go. If you are not familiar with `zk`, we recommend you to also read the `zk` docs (https://github.com/zk-org/zk/tree/main/docs).
When using the default config, the `zk` LSP client will automatically attach itself to buffers inside your notebook and provide capabilities like completion, hover and go-to-definition; see https://github.com/zk-org/zk/issues/22 for a full list of what is supported.
Try out different commands (#built-in-commands) such as `:ZkNotes` or `:ZkNew`, see what they can do, and learn as you go.
--------------------------------------------------------------------------------
BUILT-IN COMMANDS *zk-built-in_commands*
>
" Indexes the notebook
" params
" (optional) additional options, see https://github.com/zk-org/zk/blob/main/docs/editors-integration.md#zkindex
:ZkIndex [{options}]
<
>
" Creates and edits a new note
" params
" (optional) additional options, see https://github.com/zk-org/zk/blob/main/docs/editors-integration.md#zknew
:ZkNew [{options}]
<
>
" Creates a new note and uses the last visual selection as the title while replacing the selection with a link to the new note
" params
" (optional) additional options, see https://github.com/zk-org/zk/blob/main/docs/editors-integration.md#zknew
:'<,'>ZkNewFromTitleSelection [{options}]
<
>
" Creates a new note and uses the last visual selection as the content while replacing the selection with a link to the new note
" params
" (optional) additional options, see https://github.com/zk-org/zk/blob/main/docs/editors-integration.md#zknew
:'<,'>ZkNewFromContentSelection [{options}]
<
>
" cd into the notebook root
" params
" (optional) additional options
:ZkCd [{options}]
<
>
" Opens a notes picker
" params
" (optional) additional options, see https://github.com/zk-org/zk/blob/main/docs/editors-integration.md#zklist
:ZkNotes [{options}]
<
>
" Opens a notes picker for the backlinks of the current buffer
" params
" (optional) additional options, see https://github.com/zk-org/zk/blob/main/docs/editors-integration.md#zklist
:ZkBacklinks [{options}]
<
>
" Opens a notes picker for the outbound links of the current buffer
" params
" (optional) additional options, see https://github.com/zk-org/zk/blob/main/docs/editors-integration.md#zklist
:ZkLinks [{options}]
<
>
" Opens a notes picker, filters for notes that match the text in the last visual selection
" params
" (optional) additional options, see https://github.com/zk-org/zk/blob/main/docs/editors-integration.md#zklist
:'<,'>ZkMatch [{options}]
<
>
" Opens a notes picker, filters for notes with the selected tags
" params
" (optional) additional options, see https://github.com/zk-org/zk/blob/main/docs/editors-integration.md#zktaglist
:ZkTags [{options}]
<
The `options` parameter can be any valid Lua expression that evaluates to a table.
For a list of available options, refer to the `zk` docs (https://github.com/zk-org/zk/blob/main/docs/editors-integration.md#custom-commands).
In addition, `options.notebook_path` can be used to explicitly specify a notebook by providing a path to any file or directory within the notebook; see Notebook Directory Discovery (#notebook-directory-discovery).
Examples:
>
:ZkNew { dir = "daily", date = "yesterday" }
:ZkNotes { createdAfter = "3 days ago", tags = { "work" } }
:'<,'>ZkNewFromTitleSelection " this will use your last visual mode selection. Note that you *must* call this command with the '<,'> range.
:ZkCd
<
--------------------------------------------------------------------------------
Via Lua
You can access the underlying Lua function of a command, with `require("zk.commands").get`.
Examples:
>
require("zk.commands").get("ZkNew")({ dir = "daily" })
require("zk.commands").get("ZkNotes")({ createdAfter = "3 days ago", tags = { "work" } })
require("zk.commands").get("ZkNewFromTitleSelection")()
<
--------------------------------------------------------------------------------
CUSTOM COMMANDS *zk-custom_commands*
>
---A thin wrapper around `vim.api.nvim_add_user_command` which parses the `params.args` of the command as a Lua table and passes it on to `fn`.
---@param name string
---@param fn function
---@param opts? table {needs_selection} makes sure the command is called with a range
---@see vim.api.nvim_add_user_command
require("zk.commands").add(name, fn, opts)
<
Example 1:
Let us add a custom `:ZkOrphans` command that will list all notes that are orphans, i.e. not referenced by any other note.
>
local zk = require("zk")
local commands = require("zk.commands")
commands.add("ZkOrphans", function(options)
options = vim.tbl_extend("force", { orphan = true }, options or {})
zk.edit(options, { title = "Zk Orphans" })
end)
<
This adds the `:ZkOrphans [{options}]` vim user command, which accepts an `options` Lua table as an argument.
We can execute it like this `:ZkOrphans { tags = { "work" } }` for example.
>
Note: The `zk.edit` function is from the high-level API (#high-level-api), which also contains other functions that might be useful for your custom commands.
<
Example 2:
Chances are that this will not be our only custom command following this pattern.
So let's also add a `:ZkRecents` command and make the pattern a bit more reusable.
>
local zk = require("zk")
local commands = require("zk.commands")
local function make_edit_fn(defaults, picker_options)
return function(options)
options = vim.tbl_extend("force", defaults, options or {})
zk.edit(options, picker_options)
end
end
commands.add("ZkOrphans", make_edit_fn({ orphan = true }, { title = "Zk Orphans" }))
commands.add("ZkRecents", make_edit_fn({ createdAfter = "2 weeks ago" }, { title = "Zk Recents" }))
<
--------------------------------------------------------------------------------
HIGH-LEVEL API *zk-high-level_api*
The high-level API is inspired by the commands provided by the `zk` CLI tool; see `zk --help`.
It's mainly used for the implementation of built-in and custom commands.
>
---Cd into the notebook root
--
---@param options? table
require("zk").cd(options)
<
>
---Creates and edits a new note
--
---@param options? table additional options
---@see https://github.com/zk-org/zk/blob/main/docs/editors-integration.md#zknew
require("zk").new(options)
<
>
---Indexes the notebook
--
---@param options? table additional options
---@see https://github.com/zk-org/zk/blob/main/docs/editors-integration.md#zkindex
require("zk").index(options)
<
>
---Opens a notes picker, and calls the callback with the selection
--
---@param options? table additional options
---@param picker_options? table options for the picker
---@param cb function
---@see https://github.com/zk-org/zk/blob/main/docs/editors-integration.md#zklist
---@see zk.ui.pick_notes
require("zk").pick_notes(options, picker_options, cb)
<
>
---Opens a tags picker, and calls the callback with the selection
--
---@param options? table additional options
---@param picker_options? table options for the picker
---@param cb function
---@see https://github.com/zk-org/zk/blob/main/docs/editors-integration.md#zktaglist
---@see zk.ui.pick_tags
require("zk").pick_tags(options, picker_options, cb)
<
>
---Opens a notes picker, and edits the selected notes
--
---@param options? table additional options
---@param picker_options? table options for the picker
---@see https://github.com/zk-org/zk/blob/main/docs/editors-integration.md#zklist
---@see zk.ui.pick_notes
require("zk").edit(options, picker_options)
<
--------------------------------------------------------------------------------
API *zk-api*
The functions in the API module give you maximum flexibility and provide only a thin Lua friendly layer around `zk`'s LSP API.
You can use it to write your own specialized functions for interacting with `zk`.
>
---@param path? string path to explicitly specify the notebook
---@param options? table additional options
---@param cb function callback function
---@see https://github.com/zk-org/zk/blob/main/docs/editors-integration.md#zkindex
require("zk.api").index(path, options, function(err, stats)
-- do something with the stats
end)
<
>
---@param path? string path to explicitly specify the notebook
---@param options? table additional options
---@param cb function callback function
---@see https://github.com/zk-org/zk/blob/main/docs/editors-integration.md#zknew
require("zk.api").new(path, options, function(err, res)
file_path = res.path
-- do something with the new file path
end)
<
>
---@param path? string path to explicitly specify the notebook
---@param options table additional options
---@param cb function callback function
---@see https://github.com/zk-org/zk/blob/main/docs/editors-integration.md#zklist
require("zk.api").list(path, options, function(err, notes)
-- do something with the notes
end)
<
>
---@param path? string path to explicitly specify the notebook
---@param options? table additional options
---@param cb function callback function
---@see https://github.com/zk-org/zk/blob/main/docs/editors-integration.md#zktaglist
require("zk.api").tag.list(path, options, function(err, tags)
-- do something with the tags
end)
<
--------------------------------------------------------------------------------
PICKERS *zk-pickers*
Used by the high-level API (#high-level-api) to display the results of the API (#api).
>
---Opens a notes picker
--
---@param notes list
---@param options? table containing {picker}, {title}, {multi_select} keys
---@param cb function
require("zk.ui").pick_notes(notes, options, cb)
<
>
---Opens a tags picker
--
---@param tags list
---@param options? table containing {picker}, {title}, {multi_select} keys
---@param cb function
require("zk.ui").pick_tags(tags, options, cb)
<
>
---To be used in zk.api.list as the `selection` in the additional options table
--
---@param options table the same options that are use for pick_notes
---@return table api selection
require("zk.ui").get_pick_notes_list_api_selection(options)
<
--------------------------------------------------------------------------------
EXAMPLE MAPPINGS *zk-example_mappings*
Add these global mappings in your main Neovim config:
>
local opts = { noremap=true, silent=false }
-- Create a new note after asking for its title.
vim.api.nvim_set_keymap("n", "<leader>zn", "<Cmd>ZkNew { title = vim.fn.input('Title: ') }<CR>", opts)
-- Open notes.
vim.api.nvim_set_keymap("n", "<leader>zo", "<Cmd>ZkNotes { sort = { 'modified' } }<CR>", opts)
-- Open notes associated with the selected tags.
vim.api.nvim_set_keymap("n", "<leader>zt", "<Cmd>ZkTags<CR>", opts)
-- Search for the notes matching a given query.
vim.api.nvim_set_keymap("n", "<leader>zf", "<Cmd>ZkNotes { sort = { 'modified' }, match = { vim.fn.input('Search: ') } }<CR>", opts)
-- Search for the notes matching the current visual selection.
vim.api.nvim_set_keymap("v", "<leader>zf", ":'<,'>ZkMatch<CR>", opts)
<
You can add additional key mappings for Markdown buffers located in a `zk` notebook, using `ftplugin`. First, make sure it is enabled in your Neovim config:
>
filetype plugin on
<
Then, create a new file under `~/.config/nvim/ftplugin/markdown.lua` to setup the mappings:
>
-- Add the key mappings only for Markdown files in a zk notebook.
if require("zk.util").notebook_root(vim.fn.expand('%:p')) ~= nil then
local function map(...) vim.api.nvim_buf_set_keymap(0, ...) end
local opts = { noremap=true, silent=false }
-- Open the link under the caret.
map("n", "<CR>", "<Cmd>lua vim.lsp.buf.definition()<CR>", opts)
-- Create a new note after asking for its title.
-- This overrides the global `<leader>zn` mapping to create the note in the same directory as the current buffer.
map("n", "<leader>zn", "<Cmd>ZkNew { dir = vim.fn.expand('%:p:h'), title = vim.fn.input('Title: ') }<CR>", opts)
-- Create a new note in the same directory as the current buffer, using the current selection for title.
map("v", "<leader>znt", ":'<,'>ZkNewFromTitleSelection { dir = vim.fn.expand('%:p:h') }<CR>", opts)
-- Create a new note in the same directory as the current buffer, using the current selection for note content and asking for its title.
map("v", "<leader>znc", ":'<,'>ZkNewFromContentSelection { dir = vim.fn.expand('%:p:h'), title = vim.fn.input('Title: ') }<CR>", opts)
-- Open notes linking to the current buffer.
map("n", "<leader>zb", "<Cmd>ZkBacklinks<CR>", opts)
-- Alternative for backlinks using pure LSP and showing the source context.
--map('n', '<leader>zb', '<Cmd>lua vim.lsp.buf.references()<CR>', opts)
-- Open notes linked by the current buffer.
map("n", "<leader>zl", "<Cmd>ZkLinks<CR>", opts)
-- Preview a linked note.
map("n", "K", "<Cmd>lua vim.lsp.buf.hover()<CR>", opts)
-- Open the code actions for a visual selection.
map("v", "<leader>za", ":'<,'>lua vim.lsp.buf.range_code_action()<CR>", opts)
end
<
================================================================================
MISCELLANEOUS *zk-miscellaneous*
--------------------------------------------------------------------------------
SYNTAX HIGHLIGHTING TIPS *zk-syntax_highlighting_tips*
You can extend Neovim's built-in Markdown syntax with proper highlighting and conceal support for `[[Wikilinks]]`, and conceal support for standard `[Markdown Links]()`.
Create a new file under `~/.config/nvim/after/syntax/markdown.vim` for this purpose:
>
" markdownWikiLink is a new region
syn region markdownWikiLink matchgroup=markdownLinkDelimiter start="\[\[" end="\]\]" contains=markdownUrl keepend oneline concealends
" markdownLinkText is copied from runtime files with 'concealends' appended
syn region markdownLinkText matchgroup=markdownLinkTextDelimiter start="!\=\[\%(\%(\_[^][]\|\[\_[^][]*\]\)*]\%( \=[[(]\)\)\@=" end="\]\%( \=[[(]\)\@=" nextgroup=markdownLink,markdownId skipwhite contains=@markdownInline,markdownLineStart concealends
" markdownLink is copied from runtime files with 'conceal' appended
syn region markdownLink matchgroup=markdownLinkDelimiter start="(" end=")" contains=markdownUrl keepend contained conceal
<
You can then enable conceal with `:setlocal conceallevel=2`, see `:h 'conceallevel'`.
Note that if you are using `nvim-treesitter` for Markdown, don't forget to enable `additional_vim_regex_highlighting`:
>
require("nvim-treesitter.configs").setup({
-- ...
highlight = {
-- ...
additional_vim_regex_highlighting = { "markdown" }
},
})
<
--------------------------------------------------------------------------------
NVIM-LSP-INSTALLER *zk-nvim-lsp-installer*
>
Not recommended, instead install the `zk` (https://github.com/zk-org/zk) CLI tool and make it available in your `$PATH`.
<
If you insist to use nvim-lsp-installer for `zk`, the following code snippet should guide you on how to setup the `zk` server when installed via nvim-lsp-installer.
>
require("nvim-lsp-installer").on_server_ready(function(server)
local opts = {
-- customize your options as usual
--
-- on_attach = ...
-- etc, see `:h vim.lsp.start_client()`
}
if server.name == "zk" then
require("zk").setup({
lsp = {
config = vim.tbl_extend("force", server:get_default_options(), opts),
},
})
else
server:setup(opts)
end
end)
<
--------------------------------------------------------------------------------
TELESCOPE PLUGIN *zk-telescope_plugin*
>
Not recommended, instead just use the :ZkNotes or :ZkTags commands (#built-in-commands).
<
It's possible (but unnecessary) to also load the notes and tags pickers as a telescope plugin.
>
require("telescope").load_extension("zk")
<
>
:Telescope zk notes
:Telescope zk notes createdAfter=3\ days\ ago
:Telescope zk tags
:Telescope zk tags created=today
<
Reference in New Issue View Git Blame Copy Permalink