• 2 Posts
  • 142 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle


  • Hmmm. This is either tangentially-related or an extension of the same issue you experienced… but I started using the terminal within Kate this past week troubleshooting a .bash_aliases function error and noticed that it too was not updating its environment as expected, even after editing the file and running source ~/.bashrc.

    I spent 30 minutes only to realize that all of my edits/source reloading were not registering within the Kate terminal for some reason, but were working as expected in Konsole. Once I shutdown Kate and restarted it, the issue was fixed but that seems like a bug and it makes me wary about leaning to heavily on the terminal within Kate (or any other KDE apps outside of Konsole)


  • Great question. Had to think about it and I’d say for me personally, poor implementation of color pickers is the biggest frustration.

    As a technical user, I have no qualms w/ editing the default selection if it’s hard to read due to colors, but I get frustrated with poor color picker implementation. For example, color swaths that don’t have named descriptions when you hover over them. Even/especially the standard ROYGBIV colors on the first page of a color picker, but also to a lesser degree, descriptive hex codes on more nuanced online color pickers. I can’t tell the difference and don’t feel like hearing someone ask why I made the bold choice of making the sky pink.

    Another issue is something like KDE’s Konsole has a color picker that doesn’t have clear names/examples for which aspect of the terminal is being changed, so when I wanted to change the bash custom prompt color to improve readability, I had to edit 5-6 different options, and use trial and error to fix the color.









  • That my solution. I have a ‘Sync’ folder on every device’s Home folder, and then I use some aliases to determine whether to grab the bash_aliases file or replace it:

    • alias dba=‘diff -s ~/.bash_aliases ~/Sync/.bash_aliases’ # compare files
    • alias s2ba=‘cp ~/Sync/.bash_aliases ~/’ # Push from Sync folder to current bash aliases
    • alias ba2s=‘cp ~/.bash_aliases ~/Sync/’ # Push from current bash aliases to Sync folder

    By far, the diff alias is the most used. It allows for a quick check on what is different between files w/o having to open them up



  • My uneducated guess is that Endless OS pays manufacturers to have their OS installed as it has what appears to be privacy-conscious telemetry. It won’t be anywhere close to what Microsoft/Apple, but in the Linux telemetry world of the blind, the one-eyed man is king, and so it’ll still have valuable data.

    Some of the areas that are unlike most other distros I’ve come across:

    • Their website for Endless OS does a lot of tracking and has a policy that is more ‘business-orientated’ than many distros
    • Privacy policy for the OS is not available online, only when downloading program
    • They use dark patterns to have the default for telemetry as ‘opt-in’ which might be the opposite for FOSS IIRC
    • Complete list of things tracked here

    To me, it’s akin to the free third party apps that come packaged with many Android mobile devices. Less intrusive since it’s anonymized, but also feels more intrusive because it’s the entire OS being monitored. I believe I came across a headline that Fedora is attempting to use the same tracking software in the link above

    This review shares a more judgmental view of their practices

    This article has a more positive spin