TrailBlazer enables you to seemlessly move through important project marks as quickly and efficiently as possible to make your workflow blazingly fast ™.
TrailBlazer is the plugin we didn't deserve but most definitely need. It has fundamentally transformed the way I use my text editor on a daily basis. Truely a beautifully simple plugin of the people, by the people, for Neovim users.
— Abraham Lincoln, November 19th 1863
Do not blindly believe any quote on the internet, even though the one above is most certainly accurate.
NOTE: TrailBlazer is still in its early stages of development and there are still many features to come. If you have any suggestions or find any bugs, please open an issue.
- TrailBlazer
Navigating back and forth between multiple very specific points of interest in one or more files spread over several windows can be a rather difficult task. Most of the time those spots are either located too far apart within one file to do a quick relative jump or to use leap.nvim or are spread out between multiple documents but also not located at the same spot when using harpoon jumps. Remembering default Neovim mark names on a per buffer basis is annoying and takes up valuable RAM in your brain. Thus moving between those locations within large projects can slow you down tremendously. TrailBlazer aims to solve this problem by enabling you to leave trail marks as you navigate multiple files over different windows and buffers. Quickly move along the trail you mark as you journey through your project and start working wherever you left off right away whenever you need to. You can even use several immediate actions on your trail marks that allow you to be even more efficient. You can also toggle a reactive list view of all your trail marks and quickly jump to any of them.
You could just use TrailBlazer trail marks as you would normal Neovim marks, but with a few optimalizations to make your workflow more efficient. The real power of this plugin however, lies within its ability to quickly create and consume trail marks from the stack as you edit your code. This enables you to quickly "bookmark" where you are right now, naviagte to wherever you need to and come back by simply popping the last mark off the stack using the "track back" feature. This is especially useful when you need to quickly jump to a specific location in a different file or window and return afterwards without the need for a permanent mark. The length of these short lived trails is completely up to you and you can even go back to an ealier mark, do whatever you need to do and track back to your "bookmarked" location from there. The "track back" feature always brings you back to the last mark you left and consumes it from the stack. As a common use case for a feature like this is to quickly copy and paste something from one spot to another, TrailBlazer gives you several builtin stack actions like "paste at the newest trail mark" to quickly paste whatever contents you yanked into any Neovim register at the last trail mark and consume it. You can also do the same thing for all trail marks by using the "paste at all trail marks" action. As TrailBlazer continues to be developed, more actions will be added to enable you to be even more efficient.
- Neovim (stable or nightly) >= 0.8.0
TrailBlazer will usually support the current stable and nightly versions of Neovim. Older versions will most likely still work, but are no longer tested.
You can install TrailBlazer through your favorite plugin manager:
-- Using packer
use({
"LeonHeidelbach/trailblazer.nvim",
config = function()
require("trailblazer").setup({
-- your custom config goes here
})
end,
})You can configure TrailBlazer by passing a table to the setup function. The following options are
available and set by default:
-- Adjust these values to your liking
{
lang = "en",
auto_save_trailblazer_state_on_exit = false,
auto_load_trailblazer_state_on_enter = false,
custom_session_storage_dir = "", -- i.e. "~/trail_blazer_sessions/"
trail_options = {
-- The trail mark priority sets the global render priority of trail marks in the sign/number
-- column as well as the highlights within the text (e.g. Treesitter sets a value of 100).
-- Make sure this value is higher than any other plugin you use to ensure that trail marks
-- are always visible and don't get overshadowed.
trail_mark_priority = 10001,
-- Available modes to cycle through. Remove any you don't need.
available_trail_mark_modes = {
"global_chron",
"global_buf_line_sorted",
"global_fpath_line_sorted",
"global_chron_buf_line_sorted",
"global_chron_fpath_line_sorted",
"global_chron_buf_switch_group_chron",
"global_chron_buf_switch_group_line_sorted",
"buffer_local_chron",
"buffer_local_line_sorted"
},
-- The current / initially selected trail mark selection mode. Choose from one of the
-- available modes: global_chron, global_buf_line_sorted, global_chron_buf_line_sorted,
-- global_chron_buf_switch_group_chron, global_chron_buf_switch_group_line_sorted,
-- buffer_local_chron, buffer_local_line_sorted
current_trail_mark_mode = "global_chron",
current_trail_mark_list_type = "quickfix", -- currently only quickfix lists are supported
trail_mark_list_rows = 10, -- number of rows to show in the trail mark list
verbose_trail_mark_select = true, -- print current mode notification on mode change
mark_symbol = "•", -- will only be used if trail_mark_symbol_line_indicators_enabled = true
newest_mark_symbol = "⬤", -- disable this mark symbol by setting its value to ""
cursor_mark_symbol = "⬤", -- disable this mark symbol by setting its value to ""
next_mark_symbol = "⬤", -- disable this mark symbol by setting its value to ""
previous_mark_symbol = "⬤", -- disable this mark symbol by setting its value to ""
multiple_mark_symbol_counters_enabled = true,
number_line_color_enabled = true,
trail_mark_in_text_highlights_enabled = true,
trail_mark_symbol_line_indicators_enabled = false, -- show indicators for all trail marks in symbol column
symbol_line_enabled = true,
default_trail_mark_stacks = {
-- this is the list of trail mark stacks that will be created by default. Add as many
-- as you like to this list. You can always create new ones in Neovim by using either
-- `:TrailBlazerSwitchTrailMarkStack <name>` or `:TrailBlazerAddTrailMarkStack <name>`
"default" -- , "stack_2", ...
},
available_trail_mark_stack_sort_modes = {
"alpha_asc", -- alphabetical ascending
"alpha_dsc", -- alphabetical descending
"chron_asc", -- chronological ascending
"chron_dsc", -- chronological descending
},
-- The current / initially selected trail mark stack sort mode. Choose from one of the
-- available modes: alpha_asc, alpha_dsc, chron_asc, chron_dsc
current_trail_mark_stack_sort_mode = "alpha_asc",
-- Set this to true if you always want to move to the nearest trail mark first before
-- continuing to peek move in the current selection mode order. This effectively disables
-- the "current trail mark cursor" to which you would otherwise move first before continuing
-- to move through your trail mark stack.
move_to_nearest_before_peek = false,
move_to_nearest_before_peek_motion_directive_up = "fpath_up", -- "up", "fpath_up" -> For more information see section "TrailBlazerMoveToNearest Motion Directives"
move_to_nearest_before_peek_motion_directive_down = "fpath_down", -- "down", "fpath_down" -> For more information see section "TrailBlazerMoveToNearest Motion Directives"
move_to_nearest_before_peek_dist_type = "lin_char_dist", -- "man_dist", "lin_char_dist" -> Manhattan Distance or Linear Character Distance
},
event_list = {
-- Add the events you would like to add custom callbacks for here. For more information see section "Custom Events"
-- "TrailBlazerTrailMarkStackSaved",
-- "TrailBlazerTrailMarkStackDeleted",
-- "TrailBlazerCurrentTrailMarkStackChanged",
-- "TrailBlazerTrailMarkStackSortModeChanged"
},
mappings = { -- rename this to "force_mappings" to completely override default mappings and not merge with them
nv = { -- Mode union: normal & visual mode. Can be extended by adding i, x, ...
motions = {
new_trail_mark = '<A-l>',
track_back = '<A-b>',
peek_move_next_down = '<A-J>',
peek_move_previous_up = '<A-K>',
move_to_nearest = '<A-n>',
toggle_trail_mark_list = '<A-m>',
},
actions = {
delete_all_trail_marks = '<A-L>',
paste_at_last_trail_mark = '<A-p>',
paste_at_all_trail_marks = '<A-P>',
set_trail_mark_select_mode = '<A-t>',
switch_to_next_trail_mark_stack = '<A-.>',
switch_to_previous_trail_mark_stack = '<A-,>',
set_trail_mark_stack_sort_mode = '<A-s>',
},
},
-- You can also add/move any motion or action to mode specific mappings i.e.:
-- i = {
-- motions = {
-- new_trail_mark = '<C-l>',
-- ...
-- },
-- ...
-- },
},
quickfix_mappings = { -- rename this to "force_quickfix_mappings" to completely override default mappings and not merge with them
nv = {
motions = {
qf_motion_move_trail_mark_stack_cursor = "<CR>",
},
actions = {
qf_action_delete_trail_mark_selection = "d",
qf_action_save_visual_selection_start_line = "v",
},
alt_actions = {
qf_action_save_visual_selection_start_line = "V",
}
},
v = {
actions = {
qf_action_move_selected_trail_marks_down = "<C-j>",
qf_action_move_selected_trail_marks_up = "<C-k>",
}
}
},
-- Your custom highlight group overrides go here
-- hl_groups = {}
}You can customize the default highlight groups directly from within your configuration table. Since
there are quite a few of them, you will find a complete list in the collapsed section below. You can
use any valid highlight group attribute as a table key to customize them. Once you are done, simply
add the highlight groups you would like to change to your configuration table using the hl_groups
key as shown above.
Available highlight groups
hl_groups = {
TrailBlazerTrailMark = {
-- You can add any valid highlight group attribute to this table
guifg = "White",
guibg = "none",
gui = "bold",
},
TrailBlazerTrailMarkNext = {
guifg = "Green",
guibg = "none",
gui = "bold",
},
TrailBlazerTrailMarkPrevious = {
guifg = "Red",
guibg = "none",
gui = "bold",
},
TrailBlazerTrailMarkCursor = {
guifg = "Black",
guibg = "Orange",
gui = "bold",
},
TrailBlazerTrailMarkNewest = {
guifg = "Black",
guibg = "LightBlue",
gui = "bold",
},
TrailBlazerTrailMarkCustomOrd = {
guifg = "Black",
guibg = "LightSlateBlue",
gui = "bold",
},
TrailBlazerTrailMarkGlobalChron = {
guifg = "Black",
guibg = "Red",
gui = "bold",
},
TrailBlazerTrailMarkGlobalBufLineSorted = {
guifg = "Black",
guibg = "LightRed",
gui = "bold",
},
TrailBlazerTrailMarkGlobalFpathLineSorted = {
guifg = "Black",
guibg = "LightRed",
gui = "bold",
},
TrailBlazerTrailMarkGlobalChronBufLineSorted = {
guifg = "Black",
guibg = "Olive",
gui = "bold",
},
TrailBlazerTrailMarkGlobalChronFpathLineSorted = {
guifg = "Black",
guibg = "Olive",
gui = "bold",
},
TrailBlazerTrailMarkGlobalChronBufSwitchGroupChron = {
guifg = "Black",
guibg = "VioletRed",
gui = "bold",
},
TrailBlazerTrailMarkGlobalChronBufSwitchGroupLineSorted = {
guifg = "Black",
guibg = "MediumSpringGreen",
gui = "bold",
},
TrailBlazerTrailMarkBufferLocalChron = {
guifg = "Black",
guibg = "Green",
gui = "bold",
},
TrailBlazerTrailMarkBufferLocalLineSorted = {
guifg = "Black",
guibg = "LightGreen",
gui = "bold",
},
}Trail mark stacks are a collection of trail marks which you can traverse in many different ways by setting a specific trail mark selection mode. You can find out how those modes work further down below.
You can create as many trail mark stacks as you like, which allows you to group trail marks in any
way you want, depending on your project needs. You can give your trail mark stacks names and use
different sorting modes when switching between them. By default there is only one trail mark stack,
called default, and if that is enough for you, you don't ever have to create any new stacks. New
trail marks will always be added to the currently selected trail mark stack.
| Mode | Description |
|---|---|
alpha_asc |
This is the default mode. Trail mark stacks are cycled through in alphabetically ascending order depending on their given name. |
alpha_dsc |
Trail mark stacks are cycled through in alphabetically descending order depending on their given name. |
chron_asc |
Trail mark stacks are cycled through in chronological ascending order depending on their creation time. |
chron_dsc |
Trail mark stacks are cycled through in chronological descending order depending on their creation time. |
Trail mark sessions allow you to save and restore your trail mark stacks and current mode
configuration. You can either save a session in TrailBlazer's default session directory which is
located within Neovim's data directory or with a given name in any directory you like and restore
it from there. You can find out where Neovim's data directory is located on your machine by
calling :echo stdpath('data') from the commandline. TrailBlazer session save files are portable,
meaning you can even commit them to your git project and restore your session on a different
computer as long as all files in your session are located relative to your project root or their
absolute file path is valid.
If you run :TrailBlazerSaveSession without any arguments, the current session will be saved in the
default session directory and running :TrailBlazerLoadSession without any arguments will load this
session from the default session directory. All sessions in the default session directory are
automatically associated with the current working directory. This means that if you change your
working directory and run :TrailBlazerLoadSession without any arguments again, the corresponding
session for the new working directory will be loaded. If you pass either a directory or file name to
:TrailBlazerSaveSession or :TrailBlazerLoadSession, the session will be saved into or loaded
from the given directory or file. Note that you have to append any file extension (e.g. ".tbsv") to
the file name argument when saving a session. Otherwise TrailBlazer will create a directory with the
given name and save the session file named as the hashed path of the current working directory.
Passing a directory name to :TrailBlazerLoadSession will cause TrailBlazer to search for a session
file which matches the name of the hashed path of the current working directory. The same applies to
the :TrailBlazerDeleteSession command. For safety reasons, you can only delete valid session files
using this command which will be verified before deletion.
With trail mark sessions you can enable the following options in your configuration:
auto_save_trailblazer_state_on_exit = falseauto_load_trailblazer_state_on_enter = false
If you set auto_save_trailblazer_state_on_exit to true, TrailBlazer will automatically save the
current session when you exit Neovim, but only if you have previously loaded or saved a session. If
you set auto_load_trailblazer_state_on_enter to true, TrailBlazer will automatically load the
session which matches the current working directory when you enter Neovim, but only if you have a
session saved for this directory.
Trail mark selection modes allow you to switch between different modes of traversing and executing actions on your trail marks. Add the ones you would like to use to your configuration table. By default all modes are enabled. Thus far you can choose between the following modes:
| Mode | Description |
|---|---|
custom_ord |
This is a dynamic mode which will only be available and switched to once the trail mark order in any other selection mode has been manually changed from inside the trail mark list. |
global_chron |
This is the default mode. Marks are traversed globally in chronological order. |
global_buf_line_sorted |
Marks are sorted by their buffer id and globally traversed from BOF to EOF. |
global_fpath_line_sorted |
Marks are sorted by their file path and globally traversed from BOF to EOF. |
global_chron_buf_line_sorted |
Marks are sorted chronologically, then by their buffer id and globally traversed from lowest to highest line number. |
global_chron_fpath_line_sorted |
Marks are sorted chronologically, then by their file path and globally traversed from lowest to highest line number. |
global_chron_buf_switch_group_chron |
Marks are sorted chronologically, then by their buffer id and grouped by buffer switch events. Each group switch event is then traversed in chronological order. |
global_chron_buf_switch_group_line_sorted |
Marks are sorted chronologically, then by their buffer id and grouped by buffer switch events. Each group switch event is then sorted from BOF to EOF within the respective buffer. |
buffer_local_chron |
Only current buffer marks are traversed chronologically. |
buffer_local_line_sorted |
Only current buffer marks are traversed from BOF to EOF. |
There are a total of four different mark symbols in TrailBlazer that can be customized to your liking:
- The „Newest Mark“ symbol
- The „Current Cursor“ symbol
- The „Next Mark“ symbol
- The „Previous Mark“ symbol
Mark symbols allow you to see at a glance which of your marks is the newest, where the current mark
cursor is located and which mark is the next or previous to be traversed from the current cursor
position within the trail mark stack. As soon as multiple mark symbols would be displayed in the
same line of the sign column, only the last one in the stack, depending on the current sorting of
the stack, will be shown. You can set all mark symbols to any one or two characters you
like. There can only be a maximum of two characters displayed in the sign column at all times,
which is a limitation of the Neovim API. If you set any mark symbol to an empty string (i.e. ""),
it will be disabled. All mark symbols can be styled through their respective highlight groups.
This section is dedicated to the configuration table setting multiple_mark_symbol_counters_enabled
which might be a bit confusing at the beginning. As explained in the section above, there are four
types of mark symbols. As soon as there would be multiple mark symbols shown in the same sign column
of a line, with this setting enabled only the last one in the stack will be shown, but now the
number of mark symbols that are currently located within that line will be shown as the leading
character in the sign column. This will give you a better notion of where the different mark symbols
are roughly located even if they are not currently visible in the sign column. With four possible
symbols that can be displayed in the sign column, the highest possible number that will be shown
next to your mark symbol is 4, if all of the above mark symbols are located on the same line.
As soon as you create a new trail mark it will by default have two of the above symbols, the „Newest
Mark“ symbol and the „Current Cursor“ symbol set to the same line, so you will have the number 2
visible next to your mark symbol. If you now place a new mark right next to the first one, we
already have three of the possible symbols in the same line as the "Previous Mark" symbol would now
be added to the line changing the displayed number to 3. If you now add a third mark to the same
line and peek move back to the trail mark before, we have the maximum number of four symbols in the
same line as now the "Next Mark" symbol would also be added to the sign column changing the
displayed number to 4.
With TrailBlazer you can view, delete and quickly jump to any of your trail marks from within a QuickFix-List. In the title bar of the QuickFix-List you can see the name of the current trail mark stack as well as the selection mode. If you are using any "buffer local" selection mode you will also see the name of the file in the current buffer.
You can also rearrange the order of your trail marks which will then dynamically create a new trail
mark selection mode named custom_ord in your trail mark selection mode list. On entering the
visual line mode in the trail mark list, either one or multiple marks can be moved to any position
using the assigned key maps. The custom order mode can be invoked from any selection mode on the
first trail mark move action from within the trail mark list. The order of the current selection
mode will then be used as the base for the new custom order including the first move action. You can
then change the order in this selection mode or overwrite it by selecting a different base selection
mode and invoking the move action from within that mode. Cycling through the other available
selection modes will not reset the custom order. Once created, the custom_ord selection mode can
either be invoked directly or selected by cycling through the available selection modes.
This QuickFix-List does also have a few special features that make editing your trail mark stack very convenient. The following key maps are currently available within the Trail Mark QuickFix-List:
| Key Maps | Key-Code | Description |
|---|---|---|
| Enter | <CR> |
Jump to the trail mark under your cursor and set the current trail mark cursor. |
| v or V | v or V |
Enter visual line mode and select multiple trail marks. |
| d | d |
Delete the trail mark under your cursor or all trail marks within your selection. |
| Ctrl + j | <C-j> |
Move trail marks within your selection down the stack. |
| Ctrl + k | <C-k> |
Move trail marks within your selection up the stack. |
Arguments annotated with ? can be omitted when running any user command or calling an API
function. If omitted, sensable default values will be used such as: the current window, buffer,
cursor position, trail mark stack or similar. All user commands use functions defined within the
main TrailBlazer API module lua/trailblazer/init.lua which can also be used directly
like this:
require("trailblazer").<function_name>(<args>)| Command | Arguments | Description |
|---|---|---|
:TrailBlazerNewTrailMark |
<window? number><buffer? string | number><cursor_pos_row? number><cursor_pos_col? number> |
Create a new / toggle existing trail mark at the current cursor position or at the specified window / buffer / position. |
:TrailBlazerTrackBack |
<buffer? string | number> |
Move to the last global trail mark or the last one within the specified buffer and remove it from the trail mark stack. |
:TrailBlazerPeekMovePreviousUp |
<buffer? string | number |
Move to the previous global trail mark or the previous one within the specified buffer leading up to the oldest one without removing it from the trail mark stack. In chronologically sorted trail mark modes this will move the trail mark cursor up. |
:TrailBlazerPeekMoveNextDown |
<buffer? string | number> |
Move to the next global trail mark or the next one within the specified buffer leading up to the newest one without removing it from the trail mark stack. In chronologically sorted trail mark modes this will move the trail mark cursor down. |
:TrailBlazerMoveToNearest |
<buffer? string | number><directive? string><dist_type? string> |
Move to the nearest trail mark in the current or the nearest trail mark within the specified buffer. This calculates either the minimum Manhattan Distance or the minimum linear character distance between the current cursor position and the qualifying trail marks depending on dist_type => ("man_dist", "lin_char_dist"). Passing one of the available motion directives to this command will change the behavior of this motion. |
:TrailBlazerMoveToTrailMarkCursor |
Move to the trail mark cursor in the current stack. | |
:TrailBlazerDeleteAllTrailMarks |
<buffer? string | number> |
Delete all trail marks globally or within the specified buffer. |
:TrailBlazerPasteAtLastTrailMark |
<buffer? string | number> |
Paste the contents of any selected register at the last global trail mark or the last one within the specified buffer and remove it from the trail mark stack. |
:TrailBlazerPasteAtAllTrailMarks |
<buffer? string | number> |
Paste the contents of any selected register at all global trail marks or at all trail marks within the specified buffer. |
:TrailBlazerTrailMarkSelectMode |
<mode? string> |
Cycle through or set the current trail mark selection mode. |
:TrailBlazerToggleTrailMarkList |
<type? string><buffer? string | number> |
Toggle a global list of all trail marks or a subset within the given buffer. If no arguments are specified the current trail mark selection mode will be used to populate the list with either a subset or all trail marks in the mode specific order. |
:TrailBlazerOpenTrailMarkList |
<type? string><buffer? string | number> |
Open a global list of all trail marks or a subset within the given buffer. If no arguments are specified the current trail mark selection mode will be used to populate the list with either a subset or all trail marks in the mode specific order. |
:TrailBlazerCloseTrailMarkList |
<type? string> |
Close the specified trail mark list. If no arguments are specified all lists will be closed. |
:TrailBlazerSwitchTrailMarkStack |
<stack_name? string> |
Switch to the specified trail mark stack. If no stack under the specified name exists, it will be created. If no arguments are specified the default stack will be selected. |
:TrailBlazerAddTrailMarkStack |
<stack_name? string> |
Add a new trail mark stack. If no arguments are specified the default stack will be added to the list of trail mark stacks. |
:TrailBlazerDeleteTrailMarkStacks |
<stack_name? string>... |
Delete the specified trail mark stacks. If no arguments are specified the current trail mark stack will be deleted. |
:TrailBlazerDeleteAllTrailMarkStacks |
Delete all trail mark stacks. | |
:TrailBlazerSwitchNextTrailMarkStack |
<sort_mode? string> |
Switch to the next trail mark stack using the specified sorting mode. If no arguments are specified the current default sort mode will be used. |
:TrailBlazerSwitchPreviousTrailMarkStack |
<sort_mode? string> |
Switch to the previous trail mark stack using the specified sorting mode. If no arguments are specified the current default sort mode will be used. |
:TrailBlazerSetTrailMarkStackSortMode |
<sort_mode? string> |
Cycle through or set the current trail mark stack sort mode. |
:TrailBlazerSaveSession |
<session_path? string> |
Save all trail mark stacks and and the current configuration to a session file. If no arguments are specified the session will be saved in the default session directory. You will find more information here. |
:TrailBlazerLoadSession |
<session_path? string> |
Load a previous session from a session file. If no arguments are specified the session will be loaded from the default session directory. You will find more information here. |
:TrailBlazerDeleteSession |
<session_path? string> |
Delete any valid session file. If no arguments are specified the session will be deleted from the default session directory. You will find more information here. |
This list of directives can be used to change the behavior of the :TrailBlazerMoveToNearest
command and the corresponding API function. Simply choose the directive that best fits your
workflow.
| Directive | Description |
|---|---|
up |
Move to the nearest trail mark above the current line within the current buffer. If there is no trail mark above the cursor in the current buffer, nothing happens. |
down |
Move to the nearest trail mark below the current line within the current buffer. If there is no trail mark above the cursor in the current buffer, nothing happens. |
fpath_up |
Move to the nearest trail mark above the current line. If there is no trail mark above the cursor in the current buffer, move up to the next file in alphabetical order depending on the current buffer's file path. |
fpath_down |
Move to the nearest trail mark below the current line. If there is no trail mark below the cursor in the current buffer, move down to the next file in alphabetical order depending on the current buffer's file path. |
With TrailBlazer you can register custom event callbacks for different actions. TrailBlazer also provides you with useful information about the internal plugin state when dispatching events which you can process in any way you like. You could for example, use any of the provided events to update a custom status line component.
-- Register a custom event callback
vim.api.nvim_create_autocmd("User", {
pattern = "TrailBlazerTrailMarkStackSaved", -- use any of the below events
callback = function(event)
-- your code to process the callback data goes here
print(vim.inspect(event.data))
end,
})In the table below you will find a list of the currently available event callbacks that you can use.
Note that TrailBlazer will only dispatch events that have been added to the configuration table
using the event_list key. You will find an example on how to do this in the configuration
section. If you do not add the events you would like to use to the list,
they will not be dispatched even if you properly register a custom event callback as shown above.
If you need any additional events, feel free to open an issue.
| Event Name | Callback data |
|---|---|
TrailBlazerTrailMarkStackSaved |
{ added_stack = <string>, current_stack = <string>, available_stacks = <table<string>> } |
TrailBlazerTrailMarkStackDeleted |
{ deleted_stacks = <table>, current_stack = <string>, available_stacks = <table<string>> } |
TrailBlazerCurrentTrailMarkStackChanged |
{ current_stack = <string>, available_stacks = <table<string>> } |
TrailBlazerTrailMarkStackSortModeChanged |
{ current_sort_mode = <string>, available_stacks = <table<string>> } |
You can find the technical documentation for TrailBlazer under doc/trailblazer.nvim.txt. If
you are within Neovim you can also open the documentation by running :help trailblazer.
I would like to keep TrailBlazer's code base as clean and easy to read as possible. If you would like to contribute, please make sure to follow the following contribution guidelines and make sure to add method documentations to your code:
TrailBlazer uses LuaCheck to lint the code base. You will have to install Lua as well as LuaRocks to run and install LuaCheck. To get started, simply follow these steps:
Install LuaCheck through LuaRocks:
$ luarocks install luacheckAfter adding the LuaRocks binary directory to your $PATH you can use this command to
lint the code:
$ luacheck lua/ test/spec/TrailBlazer uses busted, luassert (through plenary.nvim) and
matcher_combinators to define tests in the ./test/spec directory. If you
are planning to contribute, make sure all tests pass prior to creating a pull request.
Make sure your shell is in the ./test directory or, if it is in the root directory,
replace make by make -C ./test in the commands below.
To initialize all test dependencies and execute the test suite simply run:
$ make prepare
$ make testFeedback is always welcome! If you would like to leave some, please use the GitHub Discussions. Issues are reserved for bug reports and feature requests.