Skip to content

Commit a3be570

Browse files
committed
Add Show Linting Errors In Zed as a Workflow TIL
1 parent 464a2af commit a3be570

File tree

2 files changed

+24
-1
lines changed

2 files changed

+24
-1
lines changed

README.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ pairing with smart people at Hashrocket.
1010

1111
For a steady stream of TILs, [sign up for my newsletter](https://crafty-builder-6996.ck.page/e169c61186).
1212

13-
_1544 TILs and counting..._
13+
_1545 TILs and counting..._
1414

1515
---
1616

@@ -1797,6 +1797,7 @@ _1544 TILs and counting..._
17971797
- [See Overlaps For A Set Of Time Zones](workflow/see-overlaps-for-a-set-of-time-zones.md)
17981798
- [Send A Message To A Discord Channel](workflow/send-a-message-to-a-discord-channel.md)
17991799
- [Set Recurring Reminders In Slack](workflow/set-recurring-reminders-in-slack.md)
1800+
- [Show Linting Errors In Zed](workflow/show-linting-errors-in-zed.md)
18001801
- [Toggle Between Stories In Storybook](workflow/toggle-between-stories-in-storybook.md)
18011802
- [Update asdf Plugins With Latest Package Versions](workflow/update-asdf-plugins-with-latest-package-versions.md)
18021803
- [View The PR For The Current GitHub Branch](workflow/view-the-pr-for-the-current-github-branch.md)
Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
# Show Linting Errors In Zed
2+
3+
When working in a language like TypeScript or Go, the language server tooling
4+
in [Zed](https://zed.dev/) can draw my attention to errors in my code. This
5+
could be an unrecognized function or variable, a type error, or a syntax error.
6+
When these linting errors are detected, the editor underlines them with a red
7+
squiggly. I can hover over offending token or statement and see what the error
8+
is.
9+
10+
There are also a few mouse-free ways to do this.
11+
12+
First, I can hit `F8` to jump to the next one of these errors in the current
13+
file. That will move my cursor to that location and display a small overlay
14+
with the error details.
15+
16+
Second, assuming Vim mode, I can navigate my cursor over a specific highlighted
17+
token and then hit `Shift+k`. That will pop open the same small overlay to
18+
display the error details.
19+
20+
Third, I can hit `Cmd+Shift+M` to open the _Project Diagnostics_ tab which
21+
displays a series of file buffer results with the offending lines and the error
22+
description.

0 commit comments

Comments
 (0)