Menu

#163 Tag text objects not working?

Moderate
closed-fixed
Editing (61)
6
2013-03-05
2012-03-05
work.flow
No

I read in a feature request that tag text object commands like "cit" should already be implemented. However, they seem to do nothing for me on jVi 1.4.5/NB 7.1.1. Anyone else experiencing that?

Thank you for this awesomest of all plugins! *bow*
I 'd like to contribute in the future, as soon as I can put some time aside without pain. Meanwhile, is it possible to support your efforts with a small donation?

Discussion

<< < 1 2 (Page 2 of 2)
  • Ernie Rael

    Ernie Rael - 2013-02-27

    Daniele,
    The original poster tried jVi in standalone mode (read through bug comments for how to do that) and was able to reproduce the bug. The standalone version is simpler to debug (don't have to debug all of netbeans). See in bug report starting at
    https://sourceforge.net/p/jvi/bugs/163/?limit=10&page=2#1abd
    for notes on the jVi code that does the tag block thing. Follow this code with a debugger to find the failure...

    I notice that both you and work.flow are on 64 bit machines. I wonder...

     
  • Daniele Bettella

    Thank you, i verified that the current_tagblock method is reached. I'll try to see what breaks next

     
  • Daniele Bettella

    Could the problem be that I get to line 100 of Eval.java and n==0 (causing the break to be executed?)... I can't understand what it means though

     
    • Ernie Rael

      Ernie Rael - 2013-02-27

      BTW,

      line 100 of Eval.java and n==0 (causing the break to be executed?)
      ... I can't understand what it means though

      It means that the backwards search for a start tag, something like
      <i>
      failed.

       
  • Ernie Rael

    Ernie Rael - 2013-02-27

    Thanks very much. I think I know what's going on. As a workaround, try doing
    :set rem=
    and then do something like
    vit
    within an xml tagblock. I think it will work.

    "rem" is the reMetaEscape option found at Tools>Options>jVi>Search.

    This option allows regular expression character escaping that follows the standard rather than the way vim does it. The patterns used in current_tagblock use some of the characters that are escaped differently depending on the 'rem' option.

    If you verify that this is the problem, then I'll look for a fix.

     
    • Daniele Bettella

      Yup, :set rem= does it.
      Thanks, you are doing a great job with this project.

       
  • Ernie Rael

    Ernie Rael - 2013-03-05
    • status: open --> closed-fixed
     
  • Ernie Rael

    Ernie Rael - 2013-03-05

    In nbvi-1.4.8

     
<< < 1 2 (Page 2 of 2)

Log in to post a comment.