441–450 of 454 posts
Earlier quoted context omitted.
I would also add window "mark"s, I have a-z marks set up, like vi marks, so I can tag windows and then jump to them by mark.
Do you have keybindings set up for them?
Earlier quoted context omitted.
Qutebrowser has an "all tabs are windows" mode, along with the ability to hide all the "chrome", so the window manager can handle the tabs.
Hard agree. If you're the kind of person using a tiling WM, you will definitely find the deep customization that Qutebrowser exposes to be liberating. I like the experience so much that I'll start selling it for the rest of this comment: Do you use vim-like extensions, but hate how surface-level they become due to hard WebExtension limitations? Pining to recapture the days of Pentadactyl? Qutebrowser is built for vim…
As for adblocking, I wouldn't recommend jblock (it's rather buggy from what I've seen so far) - but a built-in adblocker based on Brave's Rust library is almost ready now: https://github.com/qutebrowser/qutebrowser/pull/5317
Earlier quoted context omitted.
Same configuration across different machines (apart from hardware.nix). I have a configuration.nix, networking.nix and packages.nix that pretty much covers everything. Then there's my .emacs, bashrc and my i3/config files. There's probably a way to get those last three into my NixOS config, but I haven't really investigated that. I only use i3. Haven't found a reason to install another WM yet. I tend to use xrandr, p…
I see. I keep my Emacs configuration non-nixified but otherwise I use home-manager + stow for shell config and config dir stuff.
Changing my emacs configurations means restarting my emacs sessions in NixOS, and I don't want to have to do that if emacs is going to be my WM....
Earlier quoted context omitted.
Hard agree. If you're the kind of person using a tiling WM, you will definitely find the deep customization that Qutebrowser exposes to be liberating. I like the experience so much that I'll start selling it for the rest of this comment: Do you use vim-like extensions, but hate how surface-level they become due to hard WebExtension limitations? Pining to recapture the days of Pentadactyl? Qutebrowser is built for vim…
I love this comment :) As for adblocking, I wouldn't recommend jblock (it's rather buggy from what I've seen so far) - but a built-in adblocker based on Brave's Rust library is almost ready now: https://github.com/qutebrowser/qutebrowser/pull/5317
Of course, as always, thanks for the excellent software!
One of my favorite things about i3 is that it doesn't force itself on you when it's not needed. You can keep it "in the background" in tabbed mode, effectively using it like a non-tiling WM, as long as you want. Just let your windows pile up and switch between them with fuzzy search (rofi/Switcheroo). Then, once usage patterns emerge, you can tile to take advantage of spatial memory. Example: - Start i3 in tabbed mod…
This is why I can never switch off i3 (well, Sway). I just use tabs too much. I even hacked Firefox to hide the tab bar and open every "tab" in a new window so I could use Sway tabs for browsing. BSPWM/DWM/etc all look cool, but no built-in tabs.
Earlier quoted context omitted.
Have you tried static tiling window managers? For some reason those are much less popular even though I find them more pratical. Where dynamic WMs constantly rearrange all the windows with every change according to some fixed layout, the static ones work basically like Vim's windows and buffers. Meaning windows are stacked above each other by default with only the first one showing, but with some shortcuts you can sp…
Could you recommend any static WM?
Earlier quoted context omitted.
Have you tried static tiling window managers? For some reason those are much less popular even though I find them more pratical. Where dynamic WMs constantly rearrange all the windows with every change according to some fixed layout, the static ones work basically like Vim's windows and buffers. Meaning windows are stacked above each other by default with only the first one showing, but with some shortcuts you can sp…
That's why you have 10 workspaces.
Also, when I want to quickly open a terminal on dynamic WMs I have to setup a shortcut for a floating terminal if I don't want it to rearrange everything, while on a static WM I just open a terminal and it'll have no effect on the layout by default.
Ironically I find static window managers to be more comfortable to use the more dynamic my workflow and window arrangements are. i3wm isn't as bad because it doesn't enforce a fixed layout, but it's still more cumbersome once I want to quickly resize or swap around some windows on the screen.
Earlier quoted context omitted.
Do you have keybindings set up for them?
I do, I think I just took them from the i3 docs. Looks like there's a new way to do it: https://i3wm.org/docs/userguide.html#vim_like_marks
Earlier quoted context omitted.
I boot straight into the console and then have a setup where I either run startx or start_sway. I love i3 and it was my first experience with tiling WM years ago. It is absolutely a radical break for me from all other WM's since tiling allows me to work in deep focus many desktops, 1 desktop per activity/task and my focus always on one thing not many. Also wanting not to miss out on the future I moved to sway in para…
>The only difference is if I have to use video / webRTC screensharing or similar (usually in the browser), in which case sway will not work. Screensharing under sway works fine with firefox and chromium through xdpw.
Earlier quoted context omitted.
I boot straight into the console and then have a setup where I either run startx or start_sway. I love i3 and it was my first experience with tiling WM years ago. It is absolutely a radical break for me from all other WM's since tiling allows me to work in deep focus many desktops, 1 desktop per activity/task and my focus always on one thing not many. Also wanting not to miss out on the future I moved to sway in para…
> I boot straight into the console and then have a setup where I either run startx or start_sway Interesting, I do the same thing but just use startx. I find it hard to find convincing reasons to move from X apart from it 'being dead,' which isn't very convincing to me. What benefits to you get from sway in your setup? Is it compatible with things like ssh X forwarding?
I don't hink X is dead for a while. There is a lot of reasons for application devs not to support sway unless a strong enough user-base from that camp justifies the effort. Consider also that some of the heavy lifting previously done by X is being offloaded to Sway.
My motivation to switch to it was because Sway claims that you can just drop in your .config/i3/config and sway will be compatible to it. (it's pretty close).
What I wanted was transparency (not via a clunky workaround like compton). Also a system that takes less of my resources while in use to also roll it out on 10 or 15 year old machines I own. Sway delivers here and also has less issues with screen tearing than X with my card.
Literally everything I needed previously worked in Sway (often with different commands, e.g. wofi instead of rofi, or grim for screenshots, Waybar instead of Polybar, etc)
anything else like tmux, ssh-forwarding and all things in the terminal work perfectly.