- 18 Jul, 2020 1 commit
-
-
Gustavo Carneiro authored
-
- 17 Jul, 2020 4 commits
-
-
Gustavo Carneiro authored
-
Gustavo Carneiro authored
-
Gustavo Carneiro authored
-
Gustavo Carneiro authored
-
- 16 Jul, 2020 2 commits
-
-
Gustavo Carneiro authored
-
Gustavo Carneiro authored
-
- 15 Jul, 2020 1 commit
-
-
Gustavo Carneiro authored
-
- 04 Dec, 2019 1 commit
-
-
- 24 Oct, 2019 1 commit
-
-
File name was just passed around and has been always initialized to default value in outside code.
-
- 07 Apr, 2019 1 commit
-
-
Kurt Hindenburg authored
-
- 08 Nov, 2018 1 commit
-
-
Kurt Hindenburg authored
-
- 16 May, 2018 1 commit
-
-
Summary: Currently Unicode uses 0x10FFFF code points. It is possible to represent all of them with up to two 16 bit values (UTF-16), but this makes it harder to e.g. check for their width. Some test cases were changed. Originally they were added with an assumption that the code point will be truncated to 16 bit value and as a result changed to another code point. Test Plan: * All code points <= 0xFFFF should work as before * Start the same tmux session in two Konsoles * Change background to fully transparent in one of them and put it in front of the other one, so that all text will overlap * Generate characters with (you can pipe it to `fold -s | less -r`): ``` perl -XCSDL -e 'print map{chr($_), " "} 1..0xffff' ``` * Compare output visually. * Code points > 0xFFFF should not be truncated to 16 bits * "𝐀" and "퐀" should be different characters * Some code points > 0xFFFF should have single width * Vertical lines below should align: ``` |𝐀 | |𠀋| ``` Reviewers: #konsole, hindenburg Reviewed By: #konsole, hindenburg Subscribers: konsole-devel, hindenburg, #konsole Tags: #konsole Differential Revision: https://phabricator.kde.org/D12236
-
- 11 Mar, 2018 1 commit
-
-
Kurt Hindenburg authored
s/0/nullptr/
-
- 06 Jan, 2018 1 commit
-
-
Kurt Hindenburg authored
-
- 30 Dec, 2017 1 commit
-
-
Kurt Hindenburg authored
-
- 18 Jun, 2017 1 commit
-
-
Kurt Hindenburg authored
Revamp the file-based "unlimited" scrollback code to remove limits caused by 32bit file offsets. Use Qt's I/O functions which are buffered and use 64bit offsets. Use Qt's map instead of direct mmap to ensure consistency. Prevent wrap-around of readWriteBalance. Patch from FreeBSD committed by rezny https://github.com/freebsd/freebsd-ports-kde/blob/master/x11/konsole/files/patch-src_History.cpp https://github.com/freebsd/freebsd-ports-kde/blob/plasma5/x11/konsole/files/patch-fix_infinite_scrollback CCBUG: 374259
-
- 29 May, 2017 1 commit
-
-
Kurt Hindenburg authored
-
- 27 Apr, 2017 1 commit
-
-
Kurt Hindenburg authored
-
- 11 Apr, 2017 1 commit
-
-
Kurt Hindenburg authored
-
- 26 Mar, 2017 1 commit
-
-
Kurt Hindenburg authored
-
- 18 Feb, 2017 1 commit
-
-
Kurt Hindenburg authored
-
- 16 Jul, 2016 2 commits
-
-
Kurt Hindenburg authored
Adds faint intensity, strikeout, conceal and overline support. echo -e 'D\e[2mD\e[9mD\e[53mD\e[8mD' Thanks to Antonio Russo antonio e russo gmail com for patch REVIEW: 128405 BUG: 362171 (cherry picked from commit 84b43dfb)
-
Kurt Hindenburg authored
Adds faint intensity, strikeout, conceal and overline support. echo -e 'D\e[2mD\e[9mD\e[53mD\e[8mD' Thanks to Antonio Russo antonio e russo gmail com for patch REVIEW: 128405 BUG: 362171
-
- 08 Aug, 2015 1 commit
-
-
Kurt Hindenburg authored
REVIEW: 123881
-
- 17 Oct, 2014 1 commit
-
-
Laurent Montel authored
-
- 07 Sep, 2013 3 commits
-
-
Kurt Hindenburg authored
(cherry picked from commit ed4c55c0)
-
Kurt Hindenburg authored
(cherry picked from commit ec03567f)
-
Kurt Hindenburg authored
(cherry picked from commit 0b947727)
-
- 02 Sep, 2013 3 commits
-
-
Kurt Hindenburg authored
-
Kurt Hindenburg authored
-
Kurt Hindenburg authored
-
- 20 Dec, 2012 1 commit
-
-
Kurt Hindenburg authored
-
- 02 Dec, 2012 1 commit
-
-
Jekyll Wu authored
-
- 26 Jun, 2012 1 commit
-
-
Kurt Hindenburg authored
-
- 18 May, 2012 1 commit
-
-
Jekyll Wu authored
-
- 17 May, 2012 2 commits
-
-
Jekyll Wu authored
-
Jekyll Wu authored
Apparently I didn't take a close look at the implementation detail of memory-based history when I added the 'isRealCharacter' flag. That missing information causes some wrong behaviors randomly when using memory-based history. This is a follow up of commit dc2b64d33(for BUG 188528) BUG: 294330 BUG: 299252 FIXED-IN: 4.8.4
-
- 13 May, 2012 1 commit
-
-
Kurt Hindenburg authored
-
- 18 Mar, 2012 1 commit
-
-
Kurt Hindenburg authored
-