Bug 343541 - Cursor strange behavior since 3.0.1 update
Summary: Cursor strange behavior since 3.0.1 update
Status: RESOLVED UNMAINTAINED
Alias: None
Product: konsole
Classification: Applications
Component: font (show other bugs)
Version: 3.0.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-29 21:51 UTC by Olivier Churlaud
Modified: 2017-02-12 23:40 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
behavior in zsh (34.51 KB, image/png)
2015-01-29 21:52 UTC, Olivier Churlaud 		Details
behavior in python (32.20 KB, image/png)
2015-01-29 21:55 UTC, Olivier Churlaud 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Olivier Churlaud 2015-01-29 21:51:20 UTC 
While moving the cursor with the arrows i can see that there is a <tab> or <space> before the cursor.

In my regular zsh it's not beautiful but manageable, but in python it's unpossible to work : the work before the cursor diseappears.

I'm going to link pictures.

Reproducible: Always

Steps to Reproduce:
1. Open Konsole 
2. write some text
3. move in the line with arrows



II tried to change my profile, the type of cursor. Nothing changes this behavior
Comment 1 Olivier Churlaud 2015-01-29 21:52:55 UTC 
Created attachment 90797 [details]
behavior in zsh

the written command was 

    sudo pacman -Ss konsole
Comment 2 Olivier Churlaud 2015-01-29 21:55:08 UTC 
Created attachment 90798 [details]
behavior in python

I wrote twice the same line but moved the cursor in the 2nd one
Comment 3 Olivier Churlaud 2015-01-29 21:55:52 UTC 
(In reply to olivier from comment #1)
> Created attachment 90797 [details]
> behavior in zsh
> 
> the written command was 
> 
>     sudo pacman -Ss konsole

Also notice the problem with the "@"
Comment 4 Olivier Churlaud 2015-01-29 21:59:06 UTC 
please note that I also use yakuake without any issue
Comment 5 Olivier Churlaud 2015-02-07 22:30:11 UTC 
The problem was the Monospace font. 

Changing to DejaVu Sans or Droid corrected the thing.
Comment 6 Olivier Churlaud 2015-05-20 11:37:05 UTC 
The preblem is just concerning the default font... I had the same issue zits a fresh install
Comment 7 Kurt Hindenburg 2017-02-12 23:40:10 UTC 
This is an old report - newer versions should work as expected w/ fonts