• About

    Dominik is a PhD student at the Control Theory and Robotics Lab, TU Darmstadt, as part of the Research Training Group GKMM (GRK1362). My research focuses on state estimation in distributed systems. As hobby, I contribute to the KDE project and work on the Kate application and editor component.

    http://www.kate-editor.org

    9 Responses to Highlight Text Selection Plugin

    1. Emdek
      February 15, 2013 at 10:16

      And here is fix for another missing piece (auto bracket feature). :-)
      https://bugs.kde.org/show_bug.cgi?id=313455

      Reply
    2. Pascal
      February 15, 2013 at 13:16

      i’ve actually been wondering about what happened to that :-)
      Glad to hear it’s coming back.

      Reply
    3. goncheff
      February 16, 2013 at 10:11

      Hello guys,
      What about the Quick Switch plugin? I’m using Kubuntu 12.10, KDE 4.10.0 from ppa, got hlselection working with the workaround above but really miss quickswitch.

      Reply
      • Dominik
        February 16, 2013 at 14:03

        If you carefully read http://kate-editor.org/2013/01/06/kate-in-kde-4-10/ you will notice ctrl+alt+o.
        In other words, quick switch is now integrated into Kate

        Reply
        • goncheff
          February 16, 2013 at 14:27

          Thanks Dominik, you saved me!
          I guess the keyword here is “carefully” as looked at it a few times :)

          Reply
    4. Roberto Maurizzi
      February 17, 2013 at 10:49

      Speaking of bugs… Am I the only one seeing a problem in block selection? I can’t find a bug for it.
      Press Ctrl-Shift-B and try to select a block of text: if the last line is shorter than the ones preceding it, you won’t be able to select all the columns you need: the cursor won’t move past the end of the last (shorter) line.

      Reply
      • Dominik
        February 17, 2013 at 12:18

        Christoph removed the “non-wrapping” cursor due to bugs (iirc). But I’m pretty much hit by this as well, it simply sucks…
        Can you open a bug report? Imo this should be even fixed in the 4.10 lifetime.

        Reply