• 0 Posts
  • 41 Comments
Joined 2 years ago
cake
Cake day: July 7th, 2023

help-circle





  • Things I already have:

    • rebind ctrl-r and up (configurable) to a full screen history search UI
    • old history file is not replaced

    Things I could find useful once in a while:

    • switch filter modes via ctrl-r; search history just from the current session, directory, or globally

    Things I don’t care about and probably wouldn’t use:

    • back up and sync encrypted shell history
    • log exit code, cwd, hostname, session, command duration, etc
    • calculate statistics such as “most used command”
    • quick-jump to previous items with Alt-<num>
    • enter to execute a command, tab to edit

    I really don’t want:

    • the same history across terminals, across sessions, and across machines

    Not really a feature:

    • store shell history in a sqlite database












  • I wasn’t. Like a WhatsApp integration, I think using SMS defeats the purpose of Signal. My phone can handle SMS just fine, I don’t need that feature. But when you take a feature away, you only hear about people who used and liked it to there’s a clear bias to think there was a huge backlash.

    I haven’t seen numbers to support the alleged “mass exodus” that happened when they removed it.


  • Eager Eagle@lemmy.worldtoTechnology@lemmy.worldWhatsApp interoperability with Signal
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    2 months ago

    People that do use signal value privacy or just want to get away from predatory companies

    Once interoperability breaks this, what’s going to be the reason for people to use it?

    There’s a good chance Signal will have even less users than it does today if that happens, because the few users who care will leave.

    Everybody uses WhatsApp.

    and there needs to be a reason for people to switch; what’s that then?


  • hmm this gives me all colors (from ls and grep)

    /usr/bin/ls -l --color=always | /usr/bin/grep --color=always a
    

    (I’m using their full paths because I usually alias ls and grep to eza and rg respectively)

    There’s a export CLICOLOR_FORCE=1 you can try to avoid repeating --color=always, but that didn’t work for me with ls and grep specifically.

    Edit: there’s also a FORCE_COLOR=1 that is popular, but again, neither ls nor grep seem to care.