Skip to content

Conversation

@rymdbar
Copy link
Contributor

@rymdbar rymdbar commented Aug 14, 2025

Why settle with one perl language server when ale can have two‽

Fixes #4842.

In my mind this one was ready for merge. First when I was about to finalize the PR creation I realized I'm still running my patched PerlNavigator. Upstreaming should hopefully be fixed with bscan/PerlNavigator#171 so publishing this as a draft.

@rymdbar rymdbar force-pushed the topic/perlnavigator branch 2 times, most recently from a6d0ac0 to 51d2958 Compare August 14, 2025 21:27
@rymdbar
Copy link
Contributor Author

rymdbar commented Aug 15, 2025

PerlNavigator v0.8.20 can be used unpatched with ALE + this PR. Marking it as ready for review.

@rymdbar rymdbar marked this pull request as ready for review August 15, 2025 07:31
@rymdbar rymdbar force-pushed the topic/perlnavigator branch from 51d2958 to 32a2c94 Compare August 15, 2025 12:30
@rymdbar rymdbar marked this pull request as draft August 31, 2025 10:21
@rymdbar
Copy link
Contributor Author

rymdbar commented Aug 31, 2025

The newly pushed #5038 conflicts with this one. Thus marking as draft until the other one is merged, since msgh doesn't handle stacked pull-requests.

@rymdbar rymdbar force-pushed the topic/perlnavigator branch from 32a2c94 to 1c97daa Compare October 28, 2025 15:08
@rymdbar rymdbar marked this pull request as ready for review October 28, 2025 15:08
@rymdbar rymdbar requested a review from w0rp October 28, 2025 16:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

About adding support for PerlNavigator

2 participants