That may fix it.

diff --git a/src/document/katedocument.cpp b/src/document/katedocument.cpp
index e365c380..7c24f67f 100644
--- a/src/document/katedocument.cpp
+++ b/src/document/katedocument.cpp
@@ -3350,7 +3350,9 @@ void KTextEditor::DocumentPrivate::backspace(KTextEditor::ViewPrivate *view, con

What would be the concrete content of the combobox then?

What? Which box? These box can became these 4th "Smart" option but the code should then only work on spaces....to be "correct/right".

Given we already have now some enum for the show spaces stuff (None/Trailing/All) I would just vote to have some "Smart" 4th variant inside

I thought it should try to quit the app not only close one window.

And why is the delete not useful?

Hi, any more feedback on this?

the path is appended behind the document name. What about this solution?

PS: The tab switcher also has something similar to make a distiction between files with the same name D16054

Well, I'm also not full convinced about the current way, but how else?

I could add a "Recent" section to the beginning of the menu, it would be useful.

Nice! Just to be clear. That should to be work over session borders, not only the current one.

• Make feature configurable

• Move code to cd function
• Add Ctrl-E as suggested

• Add config page with some options, more may follow
• "Autohide" works now slightly smart
• Chose new icon which for my taste more fit
• Add an ascii progess bar to the info message to solve size issues...and to be a little fancy :-)

I could add a "Recent" section to the beginning of the menu, it would be useful.

In D20974#459863, @cullmann wrote:

Does that obsolete the other patch

When the menu is opened, clear any text in the search field left over from a prior search

Wow, look very nice :-)
The only thing I would like to have is an auto generated "most often used" list. That was also suggested somewhere. This way you could quickly change between preferred styles instead to search for them.

• Last missed settings
• Some cleanup

7 more and we are done :-/

• Use the power of new the interface in DocumentPrivate::setViewVariable
• ShowFoldingPreview
• ShowLineModification
• ShowFoldingBar

• Use the power of new the interface in ViewPrivate::setConfigValue
• Add missed finalizeConfigEntries() call
• Add check to finalizeConfigEntries() for key to be unique
• ShowIconBar
• ShowScrollbars

• Rebase on master

• ShowScrollBarPreview
• ShowScrollBarMarks
• ShowLineNumbers
• Add some validator functions, please look at them

Ah, last hint: The diff is not against master. Should you really like to try it, I can fix that earlier, otherwise will do it when I'm done

• Remove special angle bracket check, will be back in a smarter may later (hopefully)
• Move getter config functions into header

• Make feature optional by new config interface
• Make feature independent from auto bracket option
• Remove redundant const QChar typedChar
• Use dummy config value from dialog

> Have the feeling kateview_test testDragAndDrop fails more and more often. Have already spend a lot of time in look at that but without success

• Fix missing cleanup in case of unvalid mouse position
• Give members more fitting names
• Remove unneeded m_nextHighlightBlock
• Remove repaint()
• Remove commented event filter hint

• Fix jump of big unfold II :-/

• Ensure cursor don't move when isssue toggleFoldingsInRange

I think about a patch to issue the foldingPreview in case of unfold when done by click on the icon bar. Unfortunately would that need some bigger changes at the toggleFolding functions to return what was done.

In D20606#451744, @mwolff wrote:

In D20606#451459, @dhaumann wrote:

I would prefer a context menu that has this as action. This is much better discoverable and also extensible with more folding actions.

I agree. Right-click should show a context menu. Middle-click could toggle, if you need it.

try to fix annotation issue

I'm sorry, I couldn't reproduce the crash to verify your patch. But at least cause it on the first sight no new crash here :-)

hm, can't say much helpful to your patch. Send you my BT.
But from my point of view is this assert here redundant. When you dislike my check, you can drop the assert anyway.

In D20697#453841, @dhaumann wrote:

Did you test that the annotation border still works? You can do so in KDevelop by invoking git blame.

Out of the blue run I into this issue.
The only slightly unusual before was, that I had a confirmation box regarding an unsaved file while quit the session. Then, when I want to restart the same session, it crached always.
If you like I can submit the BT, but think it's not needed to approve this patch.

@dhaumann Beside these annotation stuff I think I'm done with this now. Should you, or someone else, not stop me in the next few days I may treat this as OK and push it.
There are still some issues in the mouse move handling but will try to fix that in some other patch

• Fix bookmark pixmap painting

Left before, right with fix

• Add margin to the edit area, but I'm not sure if it should be done here. I guess renderer should do it
• Simplify "additional folding highlighting", there is now the slightly gradient gone, bad?
• Rename backGroundColor->iconBarColor to fit orig name, but that name sounds to me as it's only for the icon area of the border

@dhaumann asked elsewhere

• Fix missing printed background in proper theme color
• Fix scroll past end of document
• Fix less pushy paint unfolded icon in not dark themes and don't try to use currentLineNumberColor, the folded icon gets also not highligted
• Some more cosmetic

Patch is part of D20606

• Add menu action
• Replace old two actions "Fold/Unfold Current Node" by "Toggle Current Node"
• Move logic to ViewPrivate
• KateBuffer: Add checks where they should be