From: janis_papanagnou+ng@hotmail.com   
      
   On 28.12.2023 09:13, Eli the Bearded wrote:   
   > [snip]   
   >   
   > In any case, it is clear that # and * recognize alphabetic characters   
   > like Greek capital *letter* omega differently from non-alphabet symbol   
   > characters like ohm *sign*. If you move along the line with "w" to jump   
   > between "words" you see the differences. The # and * searches use word   
   > boundaries, so word definitions are very important there.   
      
   Right.   
      
   >   
   > You are still looking at an ohm sign and thinking of a letter which is   
   > the trap of Unicode "look alikes", not something vim is doing wrong.   
      
   Erm, no. (I already explained elsethread that it's not about characters   
   that are looking alike; the issue turned out to not be about Unicode,   
   although it got apparent there. That's why I changed the test sample to   
   a plain ASCII test case.)   
      
   Your quotes (from the Vim help) helps explaining the behavior with the   
   'help' sample I posted:    'help'  'help'    'help'   
      
   I still think the behavior of Vim's * command is counterintuitive and   
   inconsistent. See this example (a file with two lines):   
      
    §%" §%" *+*+ §%" §%"   
    §%" a §%" a *+*+ §%" a §%" a   
      
   Starting from the first character of the first word we see the command   
   '*' jump words as depicted by the ^ symbols:   
      
    §%" §%" *+*+ §%" §%"   
    ^   ^        ^   ^                 # search-jumps on first line   
    §%" a §%" a *+*+ §%" a §%" a   
    ^         ^          ^     ^       # continuing/changing on second line   
        ^     ^          ^     ^   
      
   It means that * is first identifying the §%" string, and it continues   
   the search on the next line. But after it located the first §%" on the   
   second line it ad hoc changes the search pattern. - I would call that   
   undesired and inconsistent behavior.   
      
   We can "explain" (sort of) what happens. As in, say,   
   "If no alpha character is on the line * tries to match the next string   
   that matches the current one, but as soon as this search reaches or is   
   on a line that contains an alpha character the search pattern changes   
   and * jumps to the next alpha character on that line."   
      
   Okay, is it as it is. But shouldn't that feature be straightened? It's   
   not the first time that I missed a more coherent behavior in contexts   
   of non-alpha character strings, and I think that it would be generally   
   useful. - Is there, on the other hand, some sensible use-case for that   
   current [inconsistent] behavior (of ad hoc changing the pattern)?   
      
   Janis   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)