Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Rust, RR, Neovim: A perfect debug combination

github.com

Post reply on HN
Print view View original

51–60 of 102 posts

Re: Rust, RR, Neovim: A perfect debug combination

#51

Post by ReleaseCandidat »

planede wrote: post #48
jackmott42 wrote: post #38

Earlier quoted context omitted.

Just ignoring that it is fundamentally gross and pointless, which some people don't understand somehow, consider the practical implications. I can't casually make a youtube video or blog article teaching about Rust without worrying about trademarks if I use the word. Hundreds of rust libraries have Rust in the name and would be in violation of this policy the second it changed, etc.

IANAL but it's important to understand what is and isn't enforceable regarding a trademark. I can write about Debian, Firefox and Rust without an explicit disclaimer that I'm not endorsed by their corresponding foundations if it's obvious in context. I can also write about Coca-Cola, Nintendo and Oracle in a similar manner. It doesn't matter what any of the trademark policies say. I wouldn't worry about writing on ru…

> I don't get why people like to put the name "rust" in crate names, unless they write tools that work with the language (linters, auto-formatters), it just feels redundant.

In crate names it is redundant. As a project or domain name it isn't.

Re: Rust, RR, Neovim: A perfect debug combination

#52

Post by serial_dev »

planede wrote: post #48
jackmott42 wrote: post #38

Earlier quoted context omitted.

Just ignoring that it is fundamentally gross and pointless, which some people don't understand somehow, consider the practical implications. I can't casually make a youtube video or blog article teaching about Rust without worrying about trademarks if I use the word. Hundreds of rust libraries have Rust in the name and would be in violation of this policy the second it changed, etc.

IANAL but it's important to understand what is and isn't enforceable regarding a trademark. I can write about Debian, Firefox and Rust without an explicit disclaimer that I'm not endorsed by their corresponding foundations if it's obvious in context. I can also write about Coca-Cola, Nintendo and Oracle in a similar manner. It doesn't matter what any of the trademark policies say. I wouldn't worry about writing on ru…

It feels redundant when you search for it on crates.io/lib.rs, it's not redundant when you search for it or talk about it anywhere else (Google, Twitter, GitHub, real life, events, conferences).

Re: Rust, RR, Neovim: A perfect debug combination

#55

Post by ReleaseCandidat »

DixieDev wrote: post #11

Anyone got other useful tools for debugging within (neo)vim? Just seamlessly putting down breakpoints, stepping through code execution, and getting a fully fledged debugging UI experience (a la Visual Studio or Remedy BG)? This is possibly the only thing I miss from developing on Windows, and it's a shame! EDIT: I specified 'within vim' but actually I'd be down for standalone Linux app recommendations too.

> I specified 'within vim' but actually I'd be down for standalone Linux app recommendations too.

Totalview https://totalview.io/ or Ex-Allinea (now Nvidia) - don't know if it's still usable as a 'general' debugger though. https://developer.nvidia.com/allinea-ddt

Both don't work with Rust.

Re: Rust, RR, Neovim: A perfect debug combination

#57

Post by II2II »

qbasic_forever wrote: post #23
DixieDev wrote: post #11

Anyone got other useful tools for debugging within (neo)vim? Just seamlessly putting down breakpoints, stepping through code execution, and getting a fully fledged debugging UI experience (a la Visual Studio or Remedy BG)? This is possibly the only thing I miss from developing on Windows, and it's a shame! EDIT: I specified 'within vim' but actually I'd be down for standalone Linux app recommendations too.

VS code plus its vim key binding plugin. The neovim plugin world is just way too unstable in my experience.

Came here to say pretty much the same thing, except I use the Neovim extension for VS Code. It uses Neovim as the backend and, from my experience, behaves a lot more like (Neo)Vim. It is much easier to setup, since debugging is handled by VS Code. The main drawback is VS Code does not work in a terminal, which is okay IMHO since you still have access to Neovim from the shell.
Post reply on HN