[kate] [Bug 520734] Assertion triggered when setting an uppercase VI-mode mark

"Christoph Cullmann" <[email protected]>
Newsgroups gmane.comp.kde.devel.bugs
Message-ID <[email protected]/>
https://bugs.kde.org/show_bug.cgi?id=520734

Christoph Cullmann <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|                            |6.30
  Fixed/Implemented|                            |
                 In|                            |
      Latest Commit|                            |https://invent.kde.org/fram
                   |                            |eworks/ktexteditor/-/commit
                   |                            |/d8f41b7b4fc9d227a8c23d9df6
                   |                            |05251a1178fe3e
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #3 from Christoph Cullmann <[email protected]> ---
Git commit d8f41b7b4fc9d227a8c23d9df605251a1178fe3e by Christoph Cullmann, on
behalf of Ismael Asensio.
Committed on 15/08/2026 at 15:32.
Pushed by cullmann into branch 'master'.

vi-mode: Fix checks for setting user marks

When setting a user mark ("m"), there was no check for a valid character
(a-z), so it would trigger the assertion in the setter. When using the
command bar (":mark") there was a check, but it still allowed several
non-valid mark characters ("_", "+", "*").

Add a small public checker method and simplify the logic to fix this
FIXED-IN: 6.30

M  +1    -1    src/vimode/cmds.cpp
M  +6    -11   src/vimode/marks.cpp
M  +2    -1    src/vimode/marks.h
M  +5    -3    src/vimode/modes/normalvimode.cpp

https://invent.kde.org/frameworks/ktexteditor/-/commit/d8f41b7b4fc9d227a8c23d9df605251a1178fe3e

-- 
You are receiving this mail because:
You are watching all bug changes.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.