Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If already in Diagnostics View, triggering diagnostics: deploy again loses focus #25509

Open
marcospb19 opened this issue Feb 24, 2025 · 0 comments · May be fixed by #25517
Open

If already in Diagnostics View, triggering diagnostics: deploy again loses focus #25509

marcospb19 opened this issue Feb 24, 2025 · 0 comments · May be fixed by #25517
Labels
diagnostics Feedback for diagnostics, error messages, logs, etc

Comments

@marcospb19
Copy link
Contributor

marcospb19 commented Feb 24, 2025

Summary

Triggering diagnostics: deploy a second time removes your cursor (and focus from multibuffer).

Steps to trigger the problem:

  1. Have Rust diagnostics.
  2. Run diagnostics: deploy twice.

Actual Behavior:

Cursor disappears.

Expected Behavior:

Cursor stays where it was added when you first triggered.

Zed Version and System Specs

Zed: v0.176.0 (Zed Nightly 918cba4)
OS: Linux X11 arch unknown
Memory: 60.3 GiB
Architecture: x86_64
GPU: AMD Radeon RX 6750 XT (RADV NAVI22) || radv || Mesa 24.3.4-arch1.1

@marcospb19 marcospb19 added the diagnostics Feedback for diagnostics, error messages, logs, etc label Feb 24, 2025
@marcospb19 marcospb19 changed the title If already in Diagnostics View, triggering diagnostics: deploy again makes you lose focus If already in Diagnostics View, triggering diagnostics: deploy again loses focus Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
diagnostics Feedback for diagnostics, error messages, logs, etc
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant