TomorrowPlusX

In short: I defined a couple debug tasks in my project's .zed/debug.json and they work correctly.

However, whenever I hit F4 to pick a debug task (not sure if Task is the right word here) I see a list of options, and most of them are ostensibly auto-generated and not useful, as I have some specific env-vars and args in my specified debug tasks.

Screenshot for reference: https://imgur.com/a/WFS30ZH

The ones I want aren't always at the top, so I have to carefully look each time, just in case, as selecting an autogenerated one doesn't necessarily work.

How do I get Zed to only show the ones I specified?

For reference:

• Zed 1.7.2
• Fedora Linux 44
• cargo 1.96.00

I have an MX Master 3S, connected by wireless USB dongle. It works, and I use Solaar to bind the thumb pad trigger to Gnome overview. Pretty great.

But for the life of me I can't get high resolution scrolling to work. When enabled in Solaar I get problematically fast scrolling. I've tried a few things over the years (honestly, can't remember all of them) and nothing has worked.

I have heard it can work over bluetooth, but that's not an option for me as I have multiple machines connected to a single thunderbolt dock over a TB3 KVM-like switch.

Any pointers?

I upgraded to 41, it went smoothly - I'm grateful for that! This is definitely a minor, silly thing, but I was under the impression that the new Ptyxis terminal would be part of Fedora 41 / Gnome 47. But My machine is still running the old Gnome Terminal, and Ptyxis is not installed, nor is it launched with the ctrl-alt-t command shortcut.

I know I can manually install Ptyxis - and I likely will as I'm a somehwat heavy commandline user - but the fact it wasn't automatically installed has me concerned. Any suggestions?

I'm using VSCode to build and debug Rust code using Rust Analyzer and Code LLDB on Fedora Linux. Everything works great; specifically, hitting f5 starts a performs a debug build, and loads runs my project under the debugger.

But I'd like to have ctrl-f5 run a release build. At present it simply runs a debug build, just not in the debugger. One of my projects has some CPU heavy code which runs very fast in release, and very slow in debug, and it would be nice to be able to launch my code via ctrl-f5 instead of on the command line via cargo run --release

Hi,

I'm back on linux after an 18-year hiatus running macOS. I'm running Ubuntu on a Dell XPS13, and it's basically fine but it's had weird warts since upgrading to 20.04 did weird shit to my apt repositories. I've been considering popOS since it seems just a little more polished and it ran nicely when I ran it off a liveboot usb recently.

I have two duplicity backups of my user folder (one to network, one to a local drive), but they're kind of opaque, as a bunch of tgz files. And since I'd be switching OSes, I can't imagine that Ubuntu settings data from ~/.config and ~/.local would be safely applied (given popOS is an ununtu-derivative, it's not really ubuntu).

I'm inclined towards

I'm using the GLM library for vector/matrix/etc math in C++. GLM represents vec3 (and friends) as a union to allow to allow for referring fields as (x, y, z), (r, g, b) etc. This is fine, however the gdb and CodeLLDB debuggers show the unions in an awkward manner, which makes debugging a pain. See the screenshot for an example of a vec3 being displayed as three separate unions which all have to be opened to see the value.

In Xcode, I can set up some debugger pretty printing commands to simply show a formatted string instead. Is there a way to do this with VS Code's GDB or CodeLLDB debuggers? I am on linux, but have this issue on macOS as well.

https://preview.redd.it/icntmye3be051.png?widt

I have a 4k monitor, and a mid-range thunderbolt/USBC power delivery hub with display port output. My work-issued macbook pro can use the hub for power delivery, and drive the 4k monitor at 60hz over the hub's display port, which is awesome - one plug does it all.

However, my personal XPS 13 (running ubuntu 20.04) can only drive that monitor at 30hz when using the hub's display port. Fortunately, I can plug a separate usbc/thunderbolt-to-displayport cable into the XPS13's other usbc/thunderbolt plug and drive the monitor at 60hz.

This tells me a couple things. First, the hub clearly can drive the monitor at 60hz because it works with the macbook pro. Secondly, the XPS13 can drive the mon