[konsole] [Bug 383976] newer vim outputs $q q on konsole (broken xterm-256color compatibility)

2017-09-05 Thread Kurt Hindenburg 
https://bugs.kde.org/show_bug.cgi?id=383976

Kurt Hindenburg  changed:

   What|Removed |Added

 CC||michal.zajac+kde.org@gmail.
   ||com

--- Comment #8 from Kurt Hindenburg  ---
*** Bug 382501 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 383976] newer vim outputs $q q on konsole (broken xterm-256color compatibility)

2017-09-05 Thread Kurt Hindenburg 
https://bugs.kde.org/show_bug.cgi?id=383976

Kurt Hindenburg  changed:

   What|Removed |Added

  Latest Commit|https://commits.kde.org/kon |https://commits.kde.org/kon
   |sole/6dc09a36c106879f3b86d0 |sole/f3ddd3ef301d3c1e4f5140
   |24e6b95ac0f5f028c8  |5bf9a6afdc897edd8a

--- Comment #7 from Kurt Hindenburg  ---
Git commit f3ddd3ef301d3c1e4f51405bf9a6afdc897edd8a by Kurt Hindenburg, on
behalf of Albert Astals Cid.
Committed on 05/09/2017 at 13:46.
Pushed by hindenburg into branch 'Applications/17.08'.

Ignore xterm-DCS messages

Summary:
Would be ideal to process them too, but they seem kind of corner
case and ignoring them fixes vim having $q q written on the first
line on startup

Test Plan:
Ran vim, looks good

Should this go to 17.08 or master?

Reviewers: hindenburg

Reviewed By: hindenburg

Subscribers: #konsole

Tags: #konsole

Differential Revision: https://phabricator.kde.org/D7644

(cherry picked from commit 6dc09a36c106879f3b86d024e6b95ac0f5f028c8)

M  +2-0src/Vt102Emulation.cpp

https://commits.kde.org/konsole/f3ddd3ef301d3c1e4f51405bf9a6afdc897edd8a

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 383976] newer vim outputs $q q on konsole (broken xterm-256color compatibility)

2017-09-02 Thread Albert Astals Cid 
https://bugs.kde.org/show_bug.cgi?id=383976

Albert Astals Cid  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/kon
   ||sole/6dc09a36c106879f3b86d0
   ||24e6b95ac0f5f028c8
 Resolution|--- |FIXED

--- Comment #6 from Albert Astals Cid  ---
Git commit 6dc09a36c106879f3b86d024e6b95ac0f5f028c8 by Albert Astals Cid.
Committed on 02/09/2017 at 08:54.
Pushed by aacid into branch 'master'.

Ignore xterm-DCS messages

Summary:
Would be ideal to process them too, but they seem kind of corner
case and ignoring them fixes vim having $q q written on the first
line on startup

Test Plan:
Ran vim, looks good

Should this go to 17.08 or master?

Reviewers: hindenburg

Reviewed By: hindenburg

Subscribers: #konsole

Tags: #konsole

Differential Revision: https://phabricator.kde.org/D7644

M  +2-0src/Vt102Emulation.cpp

https://commits.kde.org/konsole/6dc09a36c106879f3b86d024e6b95ac0f5f028c8

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 383976] newer vim outputs $q q on konsole (broken xterm-256color compatibility)

2017-09-01 Thread Albert Astals Cid 
https://bugs.kde.org/show_bug.cgi?id=383976

--- Comment #5 from Albert Astals Cid  ---
I've a very basic "fix" at https://phabricator.kde.org/D7644

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 383976] newer vim outputs $q q on konsole (broken xterm-256color compatibility)

2017-08-30 Thread Scott Baker 
https://bugs.kde.org/show_bug.cgi?id=383976

Scott Baker  changed:

   What|Removed |Added

 CC||sc...@perturb.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 383976] newer vim outputs $q q on konsole (broken xterm-256color compatibility)

2017-08-26 Thread MikeC 
https://bugs.kde.org/show_bug.cgi?id=383976

MikeC  changed:

   What|Removed |Added

 CC||mike.cloa...@gmail.com

--- Comment #4 from MikeC  ---
(In reply to Rex Dieter from comment #2)
> confirming here (on fedora 26).
> 
> (in case it matters):
> $ echo $TERM
> xterm-256color

For my arch installation I have the same as you. 

After editing the file ~/.local/share/konsole/Shell.profile to add a line to
the end of the [general] section containing "Environment=TERM=konsole-256color"
then on starting konsole the $TERM now has:

 $ echo $TERM
konsole-256color

and the problem with vim no longer occurs.

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 383976] newer vim outputs $q q on konsole (broken xterm-256color compatibility)

2017-08-25 Thread David Rankin 
https://bugs.kde.org/show_bug.cgi?id=383976

David Rankin  changed:

   What|Removed |Added

 CC||drankinatty@suddenlinkmail.
   ||com

--- Comment #3 from David Rankin  ---
Just for the sake of completeness, this effects all versions of konsole back to
3.5.10.

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 383976] newer vim outputs $q q on konsole (broken xterm-256color compatibility)

2017-08-25 Thread Rex Dieter 
https://bugs.kde.org/show_bug.cgi?id=383976

Rex Dieter  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
 CC||rdie...@gmail.com

--- Comment #2 from Rex Dieter  ---
confirming here (on fedora 26).

(in case it matters):
$ echo $TERM
xterm-256color

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 383976] newer vim outputs $q q on konsole (broken xterm-256color compatibility)

2017-08-25 Thread Elvis Angelaccio 
https://bugs.kde.org/show_bug.cgi?id=383976

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||elvis.angelac...@kde.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 383976] newer vim outputs $q q on konsole (broken xterm-256color compatibility)

2017-08-25 Thread Egmont Koblinger 
https://bugs.kde.org/show_bug.cgi?id=383976

Egmont Koblinger  changed:

   What|Removed |Added

 CC||egm...@gmail.com

--- Comment #1 from Egmont Koblinger  ---
This comment summarizes properly what is it that's not supported by konsole:
https://github.com/vim/vim/issues/2008#issuecomment-324829794

Just FYI: VTE (gnome-terminal et al) doesn't support this either (ESC P aka
"device control string" is totally unsupported there), but at least silently
ignores it. Probably good enough, at least people don't complain about
gnome-terminal there :)

-- 
You are receiving this mail because:
You are watching all bug changes.