https://bugs.kde.org/show_bug.cgi?id=470099
donquixote changed:
What|Removed |Added
Ever confirmed|0 |1
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=470099
--- Comment #2 from donquixote ---
Thanks for the feedback!
I would like to KDE Plasma 5.27, but I would like to keep my Ubuntu LTS.
Unfortunately this is not possible,
https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/backports
> This PPA will
https://bugs.kde.org/show_bug.cgi?id=470099
Bug ID: 470099
Summary: Non-wysiwyg config for panels for multiple monitors
Classification: Plasma
Product: Active Window Control
Version: unspecified
Platform: Ubuntu
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=455518
--- Comment #2 from donquixote ---
> 1. I'm not sure if it has changed recently or not but there is a horizontal
> line between sinks and sources (at least for my chosen Plasma theme) but
> perhaps the UI team could take hint that the
https://bugs.kde.org/show_bug.cgi?id=454668
--- Comment #10 from donquixote ---
> I can reassign to Alt+^ which on my keyboard layout is right above Tab.
I should add:
If I add both Alt+^ and Alt+Shift-Tab, then even Alt+^ has the same problem as
Alt+Shift+Tab.
If I only assign Alt+^, it wo
https://bugs.kde.org/show_bug.cgi?id=454668
--- Comment #9 from donquixote ---
> This happens to me since I switched from X11 to wayland.
I should add, I can switch back to X11 and have the problem disappear.
But I would like to use wayland :)
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=454668
donquixote changed:
What|Removed |Added
CC||py7sm...@anonaddy.me
--- Comment #8 from
https://bugs.kde.org/show_bug.cgi?id=464384
--- Comment #8 from donquixote ---
This person is asking for something similar,
https://stackoverflow.com/questions/58626170/print-a-blank-line-in-bash-only-after-output
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=464384
--- Comment #7 from donquixote ---
> Add '\[\e]133;L\a\]' at the start of PS1. This is a conditional newline, so
> it does nothing if the previous output ended in newline, and a newline if the
> last output did not end in newline.
https://bugs.kde.org/show_bug.cgi?id=464384
--- Comment #5 from donquixote ---
@ninjalj
Thanks for the response in both places.
I am not happy with this behavior of bash, but I don't really know where to
take it from here.
I don't know where I would file feature requests for bash.
Perh
https://bugs.kde.org/show_bug.cgi?id=464384
donquixote changed:
What|Removed |Added
Status|RESOLVED|REPORTED
Resolution|NOT A BUG
https://bugs.kde.org/show_bug.cgi?id=464384
donquixote changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=464384
--- Comment #1 from donquixote ---
Could also be a problem with bash or xterm.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=464384
Bug ID: 464384
Summary: Up / down history damaged if last command output did
not end in newline
Classification: Applications
Product: konsole
Version: 21.12.3
Platform: Ubuntu
https://bugs.kde.org/show_bug.cgi?id=455518
Bug ID: 455518
Summary: Usability issues in audio volume control / device
switcher
Product: plasma-pa
Version: unspecified
Platform: Ubuntu Packages
OS: Linux
15 matches
Mail list logo