• 2 Posts
  • 110 Comments
Joined 1 year ago
cake
Cake day: October 9th, 2023

help-circle

  • fl42v@lemmy.mltoLinux@lemmy.mlMy move to Linux
    link
    fedilink
    arrow-up
    4
    ·
    2 days ago

    Given those options, you may want to try vim :) It’s a bit different in how you interact with it (pressing stuff on the keyboard instead of clicking stuff in menus, plus it’s more of an imperative vs declarative approach, i.e. you tell vim how to do stuff instead of what you need to be done; the good part is being independent of what sb thought you may need to do, the bad – having to learn editing primitives and stuff), but it can certainly do stuff you’ve mentioned, sometimes with some help from external programs:

    • dupcicate current line - yyp [(yy)ank_curren and (p)aste];
    • join lines depends on how you want to join them, in the simplest case it’s J or gJ to join current line with the one below with or without space as a separator respectively. You can also combine it with :g or :v and norm or macros to make this edit on lines matching (g) or not (v) a specific regex (e.g. :g/join me/norm J will join all lines containing “join me” with that below). Splitting also depends;
    • reverse, randomize and sorting can be done via calling external stuff: v10j:.!tac will reverse 11 lines, including the one with the cursor, via calling (!) tac on the selection (v) of the current line and 10 below (10j) and pasting its output in the file you’re editing (.) (it’ll replace stuff you’ve selected). Replace tac with shuf or sort for the other options mentioned. Removing duplicates without sorting - https://stackoverflow.com/questions/11532157/remove-duplicate-lines-without-sorting#11532197

    Bonus: neovim integrates with vscode quite well, and on itself it handles reasonably huge files without an issue.









  • fl42v@lemmy.mltoLinux@lemmy.mlThinkpad recs?
    link
    fedilink
    arrow-up
    2
    ·
    4 months ago

    CPUs are also somewhat choked. I had to use throttled to make mine run above 2.4 GHz under load. (You need HWP_MODE and possibly Disable_BDPROCHOT, if anyone’s interested).

    But other than that, waaaay better compared to …70 laptops, and some models seem to beat maxed out t440p-s. Also quicksync massively speeds up video decoding/encoding, so I’m overall happy with mine so far.




  • fl42v@lemmy.mltoLinux@lemmy.mlI hate flathub
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    5 months ago

    I mean, they said they don’t like flatpak explicitly, and appimage is kinda the same thing but bulkier, standalone nix is similar as well except the lack of sandboxing stuff, and spinning another distro in a container seems overkill-ish. Idk, honestly, mb they prefer the windows way of downloading random installers from the web or that clusterslackery of placing stuff in /opt by hand





  • Kinda follows from the description on their website:

    You should use KDE neon if you are an adventurous KDE enthusiast who wants the latest and greatest from the KDE community as soon as it’s available, with no delays, opinionated patches, or UX changes.

    Although, yap, I may’ve put it a bit too harshly, and the same may be applicable to using KDE on many rolling release distros.

    To be fair, the only problem I had while using it (except for the usual need to add a ppa to install literally anything) was exactly the same I encountered on arch: sddm just died after some updates and refused to start. What made it worse, however, was that they decided it was a great idea to configure the same keyboard layouts both for the graphical session and tty, so I couldn’tc even login to fix it :/


  • Well, you might’ve entered the password incorrectly a few times, and then faiilock faillocked the account. Can be fixed by going to another tty (e.g. Ctrl+alt+f3), logging in as root and faillock --reset --user your_username_here. If that doesn’t help, that’s probably neon’s issue (mb they messed up pam stuff or something).

    On a side note, KDE neon is not exactly stable for daily driving, I’d suggest switching to another distro that’s not meant for testing recent KDE stuff