ThePrimeagen/harpoon

[Feature request] ability to disable cycling

Closed

#341 opened on Nov 29, 2023

View on GitHub
 (12 comments) (0 reactions) (0 assignees)Lua (484 forks)batch import
enhancementgood first issueharpoon2

Repository metrics

Stars
 (9,070 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

hey, I think it would be useful to be able to disable cycling when using nav_next() and nav_prev().

For example: if I have 4 harpoons and I am currently at the 4th one, I would like nav_next() to do nothing. Same thing for nav_prev() on nav(1)

I know it would make sense for some of my workflows where I tend to go deeper and deeper into a codebase, setting checkpoints along the way

thanks for the hard work!

Contributor guide

Research direction
Examine the current implementation of nav next() and nav prev() in harpoon's source code to understand how cycling works. Then, add a configuration option (e.g., enable cycling) that when set to false stops navigation at the first and last items. Test manually and ensure backward compatibility.
Tech stack
lua
Domain
developer experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
LuaNeovim plugin development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60