371–380 of 454 posts
I would say the best technique depends on the situation. Sometimes column-oriented setup is more convenient for a given task/screen, and other times a tree is better.
I used to be all in on Apple. On macOS I had a little program called Magnet to snap windows to sides and corners, and on my iPad (with external keyboard) I SSH’d into a VPS to write and run code there. I used Alfred and had all kinds of workflows in there. I thought it was great. But then during my AI studies I wanted some beefier hardware, which was just not affordable for me within Apple’s ecosystem, plus they only…
Earlier quoted context omitted.
>Mouse is used because it has very low learning curve and you can just click on stuff that interests you without thinking how to reach it. I have this idea for a tiling manager called rubik's cube. Basically to switch windows all you gotta use your brain and solve a rubik's cube. You also have to memorize a bunch of short cut keys for rotating the cube. Specifically avoided allowing you to use arrow keys or the mouse…
Of course this is satire. For your information, there is a tiling WM which is more radical than my preference. It's called 'ratpoison' and it literally doesn't have mouse support, by design. I don't use it because I think having mouse support is useful as a fallback, when the application can't be effectively worked with otherwise. It is for real, it's written in C was developed 2000-2017. Got any arrows left in your…
Earlier quoted context omitted.
I dont like Microsoft operating systems and wanted to try something different. I installed Linux. The installation process was very painful. Getting it to cooperate with the hardware was worse, and of course there is no real support. I finally got it halfway working. At that point, I found it was hard to learn, harder to get used to, and hardest to do anything useful since none of the programs were familiar. Two days…
Linux CD , author being current "high-school senior" (from the profile), and "my lawyer said"...
Earlier quoted context omitted.
Aren't tiling window managers the traditional ones? The ability for one window to float over another was a later innovation and is of course more difficult to implement. The earliest versions of Windows were also tiling only, which is thus the traditional way.
Sounds plausible. Note there's a big trend of making fullscreen applications. Skype acts like you bought a computer just to run it. Slack wants it all. Gmail is crammed with icons and features and can't deal with half width screen. Media players have notions, they call your computer a library. Instead, many applications subdivide themselves into smaller windows - for example IDEs. It's as if people gave up arranging…
I use and love DWM on my home Arch system. However, at work I am stuck with Win10. Are there any recommendations for a tilting window manager for Win10? Thanks!
https://github.com/GGLucas/PyleWM
The author has recently added some nice features - a fuzzy search launcher and a fuzzy search for open windows.
My only complaint is it only supports two workspaces per monitor (I think). There's some sort of temporary workspace, but I haven't really found a use for those and they aren't really documented. However, with the new fuzzy window finder, you can just minimize windows and than search to bring them up quickly and with minimal key strokes.
Another thing: the readme hasn't been updated since the last big changes, so you'll find that you're gonna have to install more dependencies then it says.
Earlier quoted context omitted.
> You are forgetting that you actually can sandbox and contain apps. Under X11, doing that and then giving the app access to the display is dangerous. Under Wayland it is not. This matters for Flatpak, Snap, firejail, etc. I addressed this in my very post and forgot no such thing. Firejail can and does sandbox X11 . > I have seen multiple such arguments that you can “sandbox” X11 access, with no proof or really bad c…
What Firejail supports is nested X servers, which are complicated and often buggy. Last I checked Firejail itself only recommended using X11 sandboxing when dealing with hostile situations. I consider having to use a nested X server, even one capable of forwarding, a huge compromise based on my experience with it. Anyway, that did not exist before Wayland was even conceived. First of all, hardware acceleration in Xpr…
As in, a form of sandboxing.
> which are complicated
They are no more complicated than every other proxied daemon, as my original post very much explained.
> and often buggy.
Then I'm sure you can provide me with such a bug.
> Last I checked Firejail itself only recommended using X11 sandboxing when dealing with hostile situations.
Then I'm sure you can cite this recommendation.
> I consider having to use a nested X server, even one capable of forwarding, a huge compromise based on my experience with it.
I'm sure that you can come with an actual concrete example of a problem, because when I used it it simply appears as if the application normally ran in it's Window, and I would not be able to tell the difference had I not known.
> Anyway, that did not exist before Wayland was even conceived. First of all, hardware acceleration in Xpra has been a relatively rocky story for a long time. Second of all, Firejail didn’t support using it until 2016.
The first Firejail beta releases itself was in 2014, long after Wayland was first conceived.
The first Xpra release was in 2008, however.
> If you want to keep buying borderline Linux-incompatible video cards and running an unmaintained display server, by all means try to jam a security model onto an inherently insecure client-server system to help justify it. As cold as it may be, the world will happily leave you behind. And if you don’t believe me, just keep waiting. Lots of people thought Macromedia Flash would stick around forever, too.
I'm sure you'll tell the next man that proved you wrong that you “never saw proof” as well, and he will provide proof too, which you will just as dismiss with vague arguments of “It's buggy and a huge compromise, but I won't provide any specifics on which bugs, and which compromises.”
People that actually think that Wayland is the “future” that will replace X11 with this constant “features that many users need are insecure and they really don't need them.” are a laughter. As of this moment most user interfaces haven't even tried an attempt to make a Wayland port and aren't interested; the only noteable ports are KDE, GNOME, Sway, and Enlightenment, two of which had to add back many of the cut features to make their system work, but had to do so in incompatible, nonstandardized ways.
It must have been around 2013 when I first heard talk about how Wayland was ready and would leave X11 behind, and adoption hasn't increased much since then.
Earlier quoted context omitted.
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.
How did you hack Firefox that way? Been trying to figure that out for a while, no luck.
I used i3 for a while when unity had a really annoying multi-touch bug I could not work around. The thing is? I never used much more than a simple L/R split that was available in any OS / WM forever. If I wanted to split more, it was usually in the terminal, and done via tmux or the term app. Add to this, a full desktop environment will handle all sorts of things for you like brightness, volume controls, proper locki…
Try https://github.com/gTile/gTile or https://regolith-linux.org/ regolith works only under ubuntu though but both should work under gnome.
I used to be all in on Apple. On macOS I had a little program called Magnet to snap windows to sides and corners, and on my iPad (with external keyboard) I SSH’d into a VPS to write and run code there. I used Alfred and had all kinds of workflows in there. I thought it was great. But then during my AI studies I wanted some beefier hardware, which was just not affordable for me within Apple’s ecosystem, plus they only…
Take away a lot of the chrome and it’s incredible how much can be achieved via simple text files and unfussy Linux tools.
As an example, my GTD workflow (before I switched to a physical bullet journal) went from a variety of apps to a single i3 workspace that auto opened with 5 terms with each containing a single markdown file opened in vim.
The leftmost column contained the processing file from top to bottom. The middle column had Doing and Follow up files.
The rightmost column had Done and Projects files.
My done would be archived each week with a script and a new done file opened for the upcoming week.
If there were any other major files I wanted (for example I would maintain a ling term projects file) that would be opened in a different buffer in the VIM app containing the projects file.
Moving items from one folder to another was as simple as quickly navigating to that folder, using a shortcut to yank or cut the line to the global clipboard, ans then pasting it to the file I wanted to move it to.
I suspect it would have been trivial to write a script that would have automatically moved the entire line over with a single shortcut.
There is absolutely no additional overhead and it works extremely fast and well.