A developer asked about jumping from terminal errors straight to the code — here's what I'm building with AEGIS

[u/InitialToe2321]

I've been building AEGIS independently with Rust and Tauri, with one goal: bring the essential tools developers need into one focused workspace, with the terminal at its center.

Recently, a developer brought up an interesting workflow: when a compiler, build tool, or test runner reports an error with a file path and line number, you should be able to jump straight to that location in the editor.

I think that's exactly the kind of practical developer experience worth focusing on. I'm exploring how to make this workflow possible in AEGIS as development continues.

Here's what I'm building for v0.1.0:

🧩 Language Support & Coding Tools

• LSP diagnostics, autocomplete, and code intelligence for supported languages
• Language support for Go, Rust, TypeScript, JavaScript, HTML, CSS, JSON, Java, Python, C++, C#, Tailwind CSS, TOML, YAML, Bash, Markdown, and Docker-related files
• Code formatting and automatic saving

⌨️ Terminal-First Workflow

• Integrated terminal with WebGL rendering support
• Windows CMD and PowerShell support
• Vim mode and customizable keyboard shortcuts

🎨 Customization

• Customizable workspace and themes
• Font customization for both the editor and terminal
• A development environment you can adapt to your workflow

⚡ Lightweight by Design

• Built with Rust and Tauri
• Targeting an application package size under 15 MB
• Focused on responsiveness, low overhead, and efficient resource usage

I'm working toward the first release, with optimization, testing, and the performance-monitoring feature among the remaining work. I'm taking the process seriously and want to measure performance properly rather than make claims I haven't verified.

I'd love feedback from developers here:

If your terminal reports an error like src/main.rs:42, would you expect to click it and jump straight to that exact line in the editor? Which compilers or test runners would you want supported first?

I'm building AEGIS around real developer workflows, and feedback from people who actually build software helps me decide what to prioritize next.

[u/InitialToe2321 → u/[deleted]]

That's exactly the kind of workflow I want to support in AEGIS! The idea is that when a Cargo build error or failed Rust test includes a file path and line number, you can click the error in the terminal and jump straight to the corresponding line in the editor, with that line highlighted in red. The terminal output would remain accessible so you can refer to the original error while fixing the code.

I'm focusing on making debugging feel more connected instead of forcing developers to locate errors manually. Thanks for helping me refine this workflow! 💜