I comment the commands that I want and then use vim to remove ones without comments.

For example, I run:

longandannoyingcommand -f1 -f2 -f3 # keep, does something useful

Usually comment explains what the command does so I can find it by description using fzf history search. And then you can easily find all lines that contain (or do not contain “# keep”) in your history to remove or keep.

Arch users switching back to Arch after 10 minutes of using Ubuntu:

Yes. You choose the compose key in your DE settings (usually right alt key), then you can press it and type compose sequences to insert unusual symbols or strings.

Thank you very much!

Looks like the site is down or blocked in my country.

Could anyone please be so nice and copy paste those commands here?

Great release.

However I’m still waiting for snapping/alignment/distribution to be usable. Right now, some things override others (even when holding a modifier to constrain node to an axis, it will snap to things that are not aligned with the axis), and because of visual vs geometric bounding box when resizing things it will snap to align with other shapes but when you let go of LMB, the object won’t be aligned anyway (so what was the point of snapping in the first place).

Also sometimes things will snap to a guideline from a mile away, when things I’m trying to move are nowhere close to a guideline.

I’m coming drom other software (specifically, Corel Draw) and understand it’s not fair to compare different tools and demand from one to mimic the other, especially when Inkscape is FOSS and Corel Draw is a commercial product made by paid developers. And you could also say most of things I’m complaining about are muscle memory things because I’ve been using Corel for years and need to let go of old habits and get used to Inkscape if I want to switch to it rather than demand Inkscape to be more Corel like.

But I still believe Corel does some things just right. I pretty much never needed to turn off snapping in Corel and “it just worked”™, objects would never snap to a guide on the other side of the screen and constrained nodes (when holding Shift) would still both be constrained to axis and snap to objects, meaning it snaps on the intersection of the other object and the axis I’m moving along.

Also if I’m resizing a box and the edge snaps to a guide, when I let go, in Corel the edge of the box will 100% be aligned with the guide, unlike in Inkscape.

I’m pretty sure some of these issues are because of Geometric vs Visual bounding box differences, and it’s good we can at least choose between the two: Corel can’t even deal with visual bounding boxes IIRC. You work with geometric bounding box only.

I think adding the toggle somewhere in the toolbar would be a great thing so that we don’t have to go into the menu and find it every time, maybe even a hotkey to toggle between the two.

It’s worse when you have a bugged function, try to fix it, and no matter what you change it’s still bugged because an hour later you realize there is a function with the same name that redefines the function you were changing anyway somewhere else in the code.

Is there a link to this talk (or interview, or whatever this is) but in a video format, or at least a text without all those «SEE ALSO» self ads?