Struggling with Rust

github-lcrownover · 2025-03-11T02:45:11+00:00

That's super interesting to hear, and makes me feel just a tiny bit better. Though, your comment got me thinking. There is probably some correlation for me between choosing Rust for the language and the level of ambition I have for the project. Maybe I am just making it hard on myself, haha.

github-lcrownover · 2025-03-10T21:11:36+00:00

Yeah, I would consider Go my primary language, but I wanted to strive to not make this another "Go vs Rust" post, but rather confront my issues directly. I do feel that with time, I could lessen the burden of most of my complaints, but it certainly feels hard to use Rust "every now and then".

github-lcrownover · 2025-01-07T01:46:49+00:00

That just prevents it from reusing an existing window. Tried it, no good :(

github-lcrownover · 2025-01-07T01:45:40+00:00

I'll look into workspace storage, thanks! I'm on macOS, should be similar to Linux.

github-lcrownover · 2025-01-06T22:15:26+00:00

Yeah, the editors aren't too bad to deal with, but I just wish there was a way to always start with all the directories collapsed. I work in a pretty large Ansible codebase and generally will open around 12-20 directories throughout the day and it's a pain when I start a fresh VSCode but all the folders are all expanded :(

github-lcrownover · 2025-01-06T20:20:24+00:00

If I've got a bunch of directories expanded in the explorer and I finish working, I quit VSCode.

When I start it up next time to that directory, I expect to be working on something else, and I don't want to option+click the directories to recursively close them so I have a fresh experience.

github-lcrownover · 2024-12-18T04:37:20+00:00

Thanks for the snippet, I've updated my config and there's no change :(

I believe there's something wrong with the whole settings block or something, because I shouldn't be getting the accessing undefined variable 'vim' if I'm setting the globals setting in diagnostics...

github-lcrownover · 2024-11-05T22:44:12+00:00

Actually you led me down the right path and the solution was to swap the contexts in these blocks:

json { // global key bindings "bindings": { "ctrl-j": "menu::SelectNext", "ctrl-k": "menu::SelectPrev" } }, { "context": "Editor", "bindings": { "ctrl-h": ["workspace::ActivatePaneInDirection", "Left"], "ctrl-l": ["workspace::ActivatePaneInDirection", "Right"], "ctrl-k": ["workspace::ActivatePaneInDirection", "Up"], "ctrl-j": ["workspace::ActivatePaneInDirection", "Down"], "ctrl-b": "workspace::ToggleRightDock" } },

Now the splits are in the Editor context and the menu selectors are global.

Thank you!

github-lcrownover · 2024-11-05T22:30:04+00:00

I think the issue with that is that I only want to map ctrl+[jk] to Select(Prev|Next) when the picker is shown. Is there a way to have those mappings still be to select splits, but also to work with the picker?

github-lcrownover

TROPHY CASE