Y u no Mamaleek

  • 69 Posts
  • 558 Comments
Joined 3 months ago
cake
Cake day: November 3rd, 2025

help-circle
  • I hope that you use the motion commands at least, because that’s the whole point of the separate modes. If not, you should look them up and add some of them to your workflow little by little.

    The most basic ones are wand b to go a word forward or back; 0 and $ to go to the start or end of the line, or g0 and g$ for the visual line. f to jump to a particular letter forward. { and } to go to the start/end of the paragraph.

    V is useful for selecting whole lines. ctrl-v for block selection (or ctrl-q, depending on your setup).

    % can jump or select to the matching parenthesis or brace. With matchit installed, it also jumps to matching keywords like end or HTML tags.

    gc comments out the selection (or uncomments it). Works with motions too, like gcc.

    For pasting, you should use p in the normal mode. Also P pastes before the cursor. This is useful for moving text around by deleting it with something like daw, jumping elsewhere, and doing p.

    And of course, the regex replacement with :s// is very useful if you have more than a few lines that need approximately the same change.





















  • don’t you have to get all your files in an external drive and delete a full computer before you can reinstall a different disto?

    Note that you can have a separate partition for the /home directory, under which your user directory is located. Then you could wipe just the system partition and install a new distro there, keeping /home as it is. But this requires some basic knowledge of partitions and a little attention during setup. In any case, having a backup is always recommended, especially when dealing with operations that can delete all your data.



  • slower/less sensitive for a sliding bar in a specific gui menu

    I’ve never heard of such a requirement for any reason, and I’ve been around for a while and tend to read more than a little. As I wrote in another comment, I’ve only heard of the originally mentioned scrolling speed being a nuisance when the app doesn’t follow the system-wide settings. So the tradeoff of the demand to cost of implementation and support isn’t in your favor.

    Configuring this would be quite cumbersome — the user would need to specify the whole hierarchy of UI elements for the specific window, including intermediate invisible elements. Whereupon the app would just offload that to the GUI framework, which presumably would handle the functionality and add that to the myriad of aspects that it must handle already.

    However, this is probably already possible to implement in MacOS without any need for ridiculous configs on the part of the app: via a separate app using accessibility APIs. Iirc those APIs can report the UI elements that the user is engaged with — and if it reports the cursor hovering too, then the app could change the cursor speed dynamically. It’s possible even that Hammerspoon, programmable in Lua, can do something like that. Of course, apps not made with the native Cocoa framework break this and other accessibility functionality.

    As for the colors of the windows, there comes a time in the life of a man when they realize they’d like to get shit done instead of fiddling with customization, and for the UI to fade away and do its thing quietly. I’ve seen it happen.





  • It’s a very well known problem in interface design. If you include every option that someone could possibly want, you’ll have three thousand options in the settings, and it will be impossible to find anything without getting severe fatigue from looking at all the toggles.

    Consider Windows: with many advanced options, one has to click through a couple dozen dialogs in search of where that option is, getting RSI in the process. You can also take LibreOffice’s or old KDE’s settings as examples.

    MacOS solves that pretty simply: settings that most people use are in the control panel under comparatively few categories and typically readily available in there. Settings that are unlikely to be changed by anyone outside power users are still modifiable through the command-line utility for that — which is actually responsible for all the settings, making MacOS very fit for automatic setup with Ansible or somesuch.

    However, that’s just the design issue. There’s also the programming issue: every option increases pathways that the code may take, and thus the possibility of bugs and regressions, and the complexity of the code and tests.

    A well-known approach that many companies take is to include only the functionality and settings that conform to the main vision, and focus on that working well instead of trying to serve everyone. This gets them a dedicated customer base to whom the product is tailored, instead of corporate sales made on the breadth of features, wherein the end users need only a tenth of the functions but have to wade through the whole interface. 37signals is one such example of a narrowly-focused company. Github’s issues system is likely used by way more people than Jira, Bugzilla and such, despite being quite poor in functionality in comparison — but it also doesn’t need a two-hundred-pages manual to use.


  • Interesting, but doesn’t quite inspire confidence in Plasma’s resource usage either. People here complain about Electron regularly, after all. Presumably KHTML must’ve grown in complexity together with other engines.

    Meanwhile I’ve got hit with a reminiscence of Windows 98/ME having telltale underlining on folder and file names in Explorer and opening of them with one click.