argiopetech
Joined 6 years ago
Joined 6 years ago
Now, if the random crashing were fixed, that would make a real difference for me...
Most of my like-new rules came from antique malls, though I've also purchased one from Etsy. Estate sales are occasionally fruitful. As long as they were stored properly (e.g., in a desk drawer, like it seems they mostly were after the electronic calculator took over), they don't degrade. Occasionally you see minor yellowing that is cured by some time in the sun. Carrying cases (often leather) are typically more affected by time. I soak new (to me) leather cases in neatsfoot oil and give them at least a week before putting the rule back.
You could make your own with prints from the Slide Rule Museum [0]. 3D printing would make quick work of it, but I'm sure wood or metal units could be accomplished. The cursor benefits from spring loading,
They also have some pretty nice simulators [1], if that's your thing.
[0] https://sliderulemuseum.com/SR_Scales.shtml [1] https://www.sliderulemuseum.com/VirtualSR.shtml
If the widths don't add to 1, there are two possible behaviors (configurable). Either the newly focused pane adheres to the size of the screen (e.g., scroll right from the full screen editor and the half-screen browser is on the right border with half the editor visible), or the newly focused pane centers on the screen. I prefer the first behavior, but I make significant use of the "center pane" keybinding.
The Video Demo section in the README gives a pretty good demonstration of this behavior in the first 10-15 seconds.
Edit: To add to this thought and address some comments elsewhere about losing windows, I use "struts", which show P pixels of the panes to the left and right (when they exist) of the current view as a visual aid/reminder of where I am in the ribbon. These reduce the size of the tiled section of the screen and the calculation of pane size accordingly.
Quote:
We're using xwayland-satellite rather than Xwayland directly because X11 is very cursed. xwayland-satellite takes on the bulk of the work dealing with the X11 peculiarities from us, giving niri normal Wayland windows to manage.
xwayland-satellite works well with most applications: Steam, games, Discord, even more exotic things like Ardour with wine Windows VST plugins. However, X11 apps that want to position windows or bars at specific screen coordinates won't behave correctly and will need a nested compositor to run. See sections below for how to do that.
Noting the release notes, it does have many animations already enabled (but I have some or all of them disabled through config).
I'm not recommending anyone run this in favor of newer versions, but it's working for me.
If you have (having had "Editor" focused, and just opened "TermT"):
Editor | (TermT) | Term | Browser
(FM) | Term | Browser | etc.
(where pipe delimits a pane and parens are the active pane), if you go "next desktop" from "TermT" (the terminal at /tmp), that moves you down the stack of desktops. Moving up the stack of desktops returns with focus on "TermT". You'd then go "left pane" from "TermT" to get back to the editor.The answer (for me) is to think of desktops as topics. The terminal on /tmp is with the things that prompted its creation. If I needed to check some log output, for example, it's with the project that made that log output.
Edit: Note that there's nothing keeping you from stacking those terms if you like, i.e., the appropriate keybinding goes from the previous to
Editor | (TermT), Term | Browser
(FM) | Term | Browser | etc.
where the terms stack vertically in the ribbon of the desktop.Vastly preferable to having to look at the edge of the screen.
Things on other desktops are invisible in every WM.
The only difference with niri is the possibility for things to be left or right of the current window. Overview helps with that, but I know what I expect to be on a specific desktop (it's related to the topic) and seldom need it.
This was on my Bonobo WS (PopOS) w/ 2x NVidia GTX 1080s, multiple screens (2 1080p, 1 4k at 2x scaling), etc. No issues other than app support.
Highly recommend trying it. Very low barrier to entry.