All Projects → henriquehbr → nvim-startup.lua

henriquehbr / nvim-startup.lua

Licence: MIT license
Displays neovim startup time

Programming Languages

lua
6591 projects
Makefile
30231 projects
shell
77523 projects
javascript
184084 projects - #8 most used programming language

Projects that are alternatives of or similar to nvim-startup.lua

nvim-todoist.lua
Todoist plugin for Neovim in pure Lua, inspired by https://github.com/romgrk/todoist.nvim, which you should use instead
Stars: ✭ 22 (-58.49%)
Mutual labels:  nvim, neovim-plugin
cargo-limit
Cargo with less noise: warnings are skipped until errors are fixed, Neovim integration, etc.
Stars: ✭ 105 (+98.11%)
Mutual labels:  nvim, neovim-plugin
code runner.nvim
Neovim plugin.The best code runner you could have, it is like the one in vscode but with super powers, it manages projects like in intellij but without being slow
Stars: ✭ 234 (+341.51%)
Mutual labels:  nvim, neovim-plugin
aerial.nvim
Neovim plugin for a code outline window
Stars: ✭ 485 (+815.09%)
Mutual labels:  nvim, neovim-plugin
cutlass.nvim
Plugin that adds a 'cut' operation separate from 'delete'
Stars: ✭ 78 (+47.17%)
Mutual labels:  nvim, neovim-plugin
nvim-config
My neovim config
Stars: ✭ 63 (+18.87%)
Mutual labels:  nvim, neovim-plugin
awesome-neovim
Awesome Configurations for C/C++,Zig,Web and Lua development in NeoVim
Stars: ✭ 54 (+1.89%)
Mutual labels:  nvim, neovim-plugin
Lsp Status.nvim
Utility functions for getting diagnostic status and progress messages from LSP servers, for use in the Neovim statusline
Stars: ✭ 201 (+279.25%)
Mutual labels:  nvim, neovim-plugin
stabilize.nvim
Neovim plugin to stabilize window open/close events.
Stars: ✭ 295 (+456.6%)
Mutual labels:  nvim, neovim-plugin
firvish.nvim
WIP
Stars: ✭ 31 (-41.51%)
Mutual labels:  nvim, neovim-plugin
bolt.nvim
⚡ Ultrafast multi-pane file manager for Neovim with fuzzy matching
Stars: ✭ 100 (+88.68%)
Mutual labels:  nvim, neovim-plugin
feline.nvim
A minimal, stylish and customizable statusline for Neovim written in Lua
Stars: ✭ 867 (+1535.85%)
Mutual labels:  nvim, neovim-plugin
qf helper.nvim
A collection of improvements for the quickfix buffer
Stars: ✭ 70 (+32.08%)
Mutual labels:  nvim, neovim-plugin
modes.nvim
Prismatic line decorations for the adventurous vim user
Stars: ✭ 299 (+464.15%)
Mutual labels:  nvim, neovim-plugin
Coc.nvim
Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
Stars: ✭ 18,268 (+34367.92%)
Mutual labels:  nvim, neovim-plugin
neovim-lua-plugin-boilerplate
Starter template for creating Neovim Lua plugins
Stars: ✭ 28 (-47.17%)
Mutual labels:  nvim, neovim-plugin
Acid.nvim
Asynchronous Clojure Interactive Development
Stars: ✭ 147 (+177.36%)
Mutual labels:  nvim, neovim-plugin
Lualine.nvim
A blazing fast and easy to configure neovim statusline written in pure lua.
Stars: ✭ 198 (+273.58%)
Mutual labels:  nvim, neovim-plugin
tabby.nvim
A declarative, highly configurable, and neovim style tabline plugin. Use your nvim tabs as a workspace multiplexer!
Stars: ✭ 232 (+337.74%)
Mutual labels:  nvim, neovim-plugin
nvim-highlite
A colorscheme template that is "lite" on logic for the developer.
Stars: ✭ 163 (+207.55%)
Mutual labels:  nvim, neovim-plugin

Important notice

This project is currently hosted on GitHub. This is not ideal; GitHub is a proprietary, trade-secret system that is not Free and Open Souce Software (FOSS). I'm deeply concerned about using a proprietary system like GitHub to develop our FOSS project. I urge you to read about the Give up GitHub campaign from the Software Freedom Conservancy to understand some of the reasons why GitHub is not a good place to host FOSS projects.

With that in mind, i'll be migrating this repository to sourcehut on August 1st, after that, with the intent of keeping users and contributors informed, this repository will be archived, and all of it's files and commit history will be removed (with the exception of this notice), keep in mind that development will happen exclusively at sourcehut

Any use of this project's code by GitHub Copilot, past or present, is done without my permission. I do not consent to GitHub's use of this project's code in Copilot.

Logo of the GiveUpGitHub campaign

nvim-startup.lua

Displays neovim startup time

Summary

Installation

If you're using one of these plugin managers:

The installation method is pretty much the same for all of them, simply initialize the plugin manager and include henriquehbr/nvim-startup.lua on the list

Otherwise, if you're using pathogen, simply clone it on your ~/.vim/bundle directory:

$ git clone --depth 1 https://github.com/henriquehbr/nvim-startup.lua

nvim-startup is intended to be immediately executed on (n)vim startup, so if your plugin manager has some sort of opt funcionality that marks it as a optional plugin, avoid it!

Usage

To get it up and running, first, require it on your config:

require 'nvim-startup'.setup()

Then, the last step required for the plugin to work effectively, is to create a alias on your .bashrc or .zshrc like the one below:

alias nvim='nvim --startuptime /tmp/nvim-startuptime'

By default, nvim-startup uses /tmp/nvim-startuptime as it's startup log file, but if you need to change that, you can specify a different path on the g:nvim_startup_file global variable

After that, you're done, just reload your nvim and hopefully you will see a message just like that:

nvim-startup: running on the next (n)vim instance

Don't worry, that means the plugin still couldn't find the startup time log file on the first run, it's completely normal and expected to happen, it will work fine on subsequent runs of vim, with the message below:

nvim-startup: launched in <x> ms

Configuration

The example below represents all the possible settings with their respective types and default values

require 'nvim-startup'.setup {
    startup_file = '/tmp/nvim-startuptime' -- sets startup log path (string)
    message = 'Whoa! those {} are pretty fast' -- sets a custom message (string | function)
    message = function(time) -- function-based custom message
        time < 100 and 'Just {}? really good!' or 'Those {} can get faster'
    end
}

Contribution guidelines

Requirements

The following tools are needed in order to properly setup the development workflow:

Steps

If you're willing to contribute to nvim-startup, it's highly recommended to follow the steps below (for organization purposes)

  1. Fork the repo
  2. Open a new branch following one of the following naming patterns
    • feat/<branch_name> for features
    • fix/<branch_name> for bugfixes
    • chore/<branch_name> for small changes that doesn't fit the ones above
  3. Run make init to setup the development environment
  4. All commits must follow a similar naming pattern as the branches (which will be enforced by commitlint), examples below:
    • feat: <commit_message> for features
    • fix: <commit_message> for bugfixes
    • chore: <commit_message> for small changes that doesn't fit the ones above
  5. Submit your PR! (preferably a small one and concise one, for a faster code review)

Pull requests that stricly follow the recommendations above will have higher priority in contrast of those who don't

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].