conduct.nvim

A project management plugin for Neovim with session support

Table of Contents

• Features
• Requirements
• Installation
• Configuration
• Usage
  • Projects
  • Sessions
• Project Config Structure
  • Keybinds
  • Variables
• Presets
• Functions
• Telescope

Features

• Intuitive and easy to manage projects
• Run commands or Lua functions on keybindings
• Presets for multiple projects that share some similarities
• Store multiple sessions for a single project
• Provides hooks to customize your experience
• Easy to use API
• Telescope integration

Requirements

• Neovim >= 0.8.0 (might work with earlier version)
• plenary.nvim

Installation

lazy.nvim:

{
    "aaditeynair/conduct.nvim",
    dependencies = "nvim-lua/plenary.nvim",
    cmd = {
        "ConductNewProject",
        "ConductLoadProject",
        "ConductLoadLastProject",
        "ConductLoadProjectConfig",
        "ConductReloadProjectConfig",
        "ConductDeleteProject",
        "ConductRenameProject",
        "ConductProjectNewSession",
        "ConductProjectLoadSession",
        "ConductProjectDeleteSession",
        "ConductProjectRenameSession",
    },
}

Configuration

require("conduct").setup({
    -- define function that you bind to a key in a project config
    functions = {},

    -- define presets for projects
    presets = {},

    hooks = {
        before_session_save = function() end,
        before_session_load = function() end,
        after_session_load = function() end,
        before_project_load = function() end,
        after_project_load = function() end,
    }
})

Usage

Projects

Sessions

One of the main differences between conduct.nvim and other project management plugins, is its ability to store multiple session for a single project. This allows you to switch between different contexts in the code.

These commands only work when a project is active

Project Config Structure

{
  "name": "project name",
  "cwd": "/home/user/project/foo",
  "variables": [],
  "preset": "",
  "keybinds": []
}

Keybinds

The keybinds property should be a list that contains data in the following manner:

{
  "keybinds": [["keybinding", "command", "type"]]
}

• keybinding: the key combination of the binding ("hi", "so")
• command: can be a vim command or the name of a function
• type: can be either command or function. If not provided, it is assumed as command

Variables

Variables can only be used in the command type keybindings. They can be mentioned using the ${variable_name} syntax.

{
  "variables": {
    "flags": "-la"
  },
  "keybinds": [["<leader>so", "TermOpen control ls ${flags}"]]
}

Presets

Presets can be used to setup keybinds for multiple projects that might share similarities

require("conduct").setup({
    presets = {
        node = {
            keybinds = {
                {"<leader>sd", "TermOpen dev-server npm run dev", "command"}
                {"<leader>sb", "TermOpen build npm run build", "command"}
            }
        }
    }
})

{
  "name": "personal-blog-react",
  "cwd": "/home/user/project/blog",
  "variables": [],
  "preset": "node",
  "keybinds": []
}

Functions

Define functions when setting up conduct.nvim and bind keys to them in the project config

require("conduct").setup({
    functions = {
        run_npm_server = function()
            local tm = require("termnames")
            if not tm.terminal_exists("server") then
                tm.create_terminal("server")
            end

            tm.run_terminal_cmd({"server", "npm run dev"})
        end,
    },
})

{
  "name": "personal-blog-react",
  "cwd": "/home/user/project/blog",
  "variables": [],
  "preset": "",
  "keybinds": [["<leader>so", "run_npm_server", "function"]]
}

Telescope

Conduct.nvim provides telescope integration for switching between projects and sessions.

telescope.load_extension("conduct")

Run :Telescope conduct projects to search and load a project and run :Telescope conduct sessions to switch between project sessions.