abdullah/til
1
0
Fork 0
mirror of https://github.com/jbranchaud/til synced 2026-01-03 15:18:01 +00:00
Code Issues Projects Releases Wiki Activity

Add Show Linting Errors In Zed as a Workflow TIL

Browse Source
This commit is contained in:
jbranchaud
2024-12-21 19:14:48 -06:00
parent 464a2af6db
commit a3be570a32
2 changed files with 24 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
README.md
View File

@@ -10,7 +10,7 @@ pairing with smart people at Hashrocket.
For a steady stream of TILs, [sign up for my newsletter](https://crafty-builder-6996.ck.page/e169c61186).
_1544 TILs and counting..._
_1545 TILs and counting..._
---
@@ -1797,6 +1797,7 @@ _1544 TILs and counting..._
- [See Overlaps For A Set Of Time Zones](workflow/see-overlaps-for-a-set-of-time-zones.md)
- [Send A Message To A Discord Channel](workflow/send-a-message-to-a-discord-channel.md)
- [Set Recurring Reminders In Slack](workflow/set-recurring-reminders-in-slack.md)
- [Show Linting Errors In Zed](workflow/show-linting-errors-in-zed.md)
- [Toggle Between Stories In Storybook](workflow/toggle-between-stories-in-storybook.md)
- [Update asdf Plugins With Latest Package Versions](workflow/update-asdf-plugins-with-latest-package-versions.md)
- [View The PR For The Current GitHub Branch](workflow/view-the-pr-for-the-current-github-branch.md)

22
workflow/show-linting-errors-in-zed.md Normal file
View File

@@ -0,0 +1,22 @@
# Show Linting Errors In Zed
When working in a language like TypeScript or Go, the language server tooling
in [Zed](https://zed.dev/) can draw my attention to errors in my code. This
could be an unrecognized function or variable, a type error, or a syntax error.
When these linting errors are detected, the editor underlines them with a red
squiggly. I can hover over offending token or statement and see what the error
is.
There are also a few mouse-free ways to do this.
First, I can hit `F8` to jump to the next one of these errors in the current
file. That will move my cursor to that location and display a small overlay
with the error details.
Second, assuming Vim mode, I can navigate my cursor over a specific highlighted
token and then hit `Shift+k`. That will pop open the same small overlay to
display the error details.
Third, I can hit `Cmd+Shift+M` to open the _Project Diagnostics_ tab which
displays a series of file buffer results with the offending lines and the error
description.