Some popular KDE programs (e.g., Dolphin, Kate) have built-in terminal. It appears at the separate panel. When user navigates folders the application while having terminal opened, terminal emulates graphical navigation by executing commands like " cd". This command come with leading space and generally that means "don't save this command in history". That works for distros that has environmental value set as HISTCONTROL="ignoreboth". Fedora, for some historical reasons, has a different value - HISTCONTROL="ignoredups"
HISTCONTROL="ignoreboth"
HISTCONTROL="ignoredups"
Example of the usability issue: User needs to execute the same command (e.g., "ls", "grep", "ffmpeg", "gm" etc.) in different directories. So users goes to some folder, input and executes command, then goes to another folder and instead of pasting/"reverse-i-search"/re-typing command, just presses "Up" key and then "Enter". With ignoredup "Up" key will show the last navigation command instead which is inconvenient and hurts productivity.
ignoredup
Solution: Set HISTCONTROL=ignoreboth in ~/.bashrc
HISTCONTROL=ignoreboth
In my opinion, ignoreboth by default is beneficial for all Fedora users as well as those who migrate from other distros. If it's not possible to change distro-wide, I'd like to have it on KDE-related spins.
ignoreboth
Very old related bug-reports: - https://bugzilla.redhat.com/show_bug.cgi?id=500819 - https://bugzilla.redhat.com/show_bug.cgi?id=520632
I don't personally believe this belongs to KDE
@aleasto
Compared to other KDE distributions, I believe it's a usability regression. For me it's kinda similar to fonts subpixel rendering tweak (/etc/fonts/conf.d/10-sub-pixel-rgb-for-kde.conf). Fedora downstream decides to disable ше in fontconfig package, but Fedora KDE SIG enables it for KDE Plasma users. If this issue is not on the Fedora KDE SIG side and both Fedora bugs are closed, I wonder how this issue should be resolved.
That is different. The fontconfig snippet was always separate, it just moved from the global fontconfig package to ours. It also always existed in some form.
This is doing something to the shell, which affects everything. And as the old bug reports in 2023 and 2009 both indicate, people didn't like it. We could consider making a System Wide Change proposal for this if other members of the SIG feel like we should make this change, though.
Login to comment on this ticket.