[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [kate] [Bug 310073] Tab and backspace don't indent to expected position
From:       LaChenal <bIllachenal () gmail ! com>
Date:       2013-01-06 3:14:51
Message-ID: bug-310073-17878-TeDWXUCymu () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=310073

LaChenal <bIllachenal@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bIllachenal@gmail.com

--- Comment #1 from LaChenal <bIllachenal@gmail.com> ---
I agree, though perhaps it could be said it's just the way Kate does things by
default.
For me, this is not quite as annoying and useless as the behaviour of carriage
return at end of text.

However all this is already achievable by tinkering with available Settings 
Configure Kate - Editor component - Editing options- Indentation tab
    / I have set  indentation 4,  keeping tabwidth 8 (?):
adjust indent of pasted code yes, 
backspace in leading blank unindents yes, 
tab key action -always increase indentation level yes, 
and increase tab level in leading blank space yes.

At the head of that panel is also a selector "Default Indentation Mode"  to
adopt standard behaviour of other editors. This is normally  set to the Kate
default, which is bizarrely termed "Normal".

So, it is all possible, just that the current defaults are not that clever, and
it is a bit of  a pain to navigate to alter them.
I would, however, be concerned that some admins may depend of current behaviour
to 
achieve automated edits.


May I illustrate what I understand.
Assuming tab is set to six spaces, the current defaulty behaviour of Kate is
like this:

+at start line
      +indented once, return
+return comes here
                  +indented thrice
            +indented thrice,place cursor before "+" & backspace once 
      +indented thrice, backspace twice
+indented thrice, backspace thrice

Which is miserable, except:

      +whereas in the case of a very long line that goes on to triggers word
wrap at the archaic limit
      of 80 characters, say (for those of us who remember IBM punch cards) then
it comes back to
      here (as one might expect), forming a nicedly-behaved block of text.

A more useful default, achieved once settings have been adjusted, might be
this:

+at start line
    +indented once, return
    +return comes here, forming a block of text#
    +until action is taken to shift left again
+start again
            +indented thrice
        +indented thrice, place cursor at start-line (before "+") & backspace
once, goes back a tab
    +indented thrice, place cursor at start-line & backspace twice, goes back
two tabs
+indented thrice, backspace thrice.

~~~~~~~~~~

Tab key action "increase indentation level if in leading blank space" 
(in the CofigureKate  - Editing  - Indentation panel) seems not to work for me.

I happen to be using Mint 13 KDE just now, 
 Kate is "Version 3.8.3 Using KDE Development Platform 4.8.3 (4.8.3)" 

~~~~~~~~~~~

More annoying & useless is the insert-point behaviour at end of text. I don't
see an option to change this.

The default splits the last line immediately above where the cursor is
positioned (cursor somewhere below current last line of text, that is). 
This is next to useless, very irritating, because one has to locate the end of
the last line to get return to work sensibly.

Current default when cursor is somewhere non-specific below the last line:

"This is what Kate currently has in it's arsenal as default"

                                                                    ^          
          {cursor somewhere below last line}

gives insert position approximately:
"This is what Kate currently has in it's ar|senal as default"

So, adding    return[something from the pasteboard]    currently gives:
"This is what Kate currently has in it's ar
[something from the pasteboard]senal as default"

Which is about as much use a blotting paper umbrella in a hurricane.

To get it to act at all usefully, to append, one has to actually locate the
very end of the last line & add there.
Which can be awkward if line-wrap is not on.

Better default behaviour would be 
"This is what Kate currently has in it's arsenal as default"|
                                                                               
                   ↖  {actual insert position }
                                                                 ^           
{when cursor is anywhere after EOT} 

Then adding    return[something from the pasteboard]    would give:
"This is what Kate currently has in it's arsenal as default"
[something from the pasteboard]|

Much more sensible. 
Does anyone disagree?

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]