and now segueing to folding

[Randy Kramer]

On Thursday 27 December 2007 04:25 am, Thorsten Haude wrote:
> * Randy Kramer wrote (2007-12-23 13:13):
> >On Saturday 22 December 2007 07:33 pm, Thorsten Haude wrote:
> >> Anyway, feel free to bring up any question about NEdit that comes up,
> >> on- or off-list. I'm far from the best coder around here, so I can
> >> learn a lot from discussions like these.

Trying to take advantage of that.

Can anybody either give me some hints, explain to me, or point me to an 
explanation of how cursor movement is handled in nedit?

As a more specific question/example, what happens when the user presses the up 
arrow to move the cursor to the next line up?

With the minimal code reading and some recent grepping I've done, I haven't 
found code so far like I might have expected--something that looks for the 
up-arrow keystroke and repositions the cursor.  I'm beginning to suspect that 
such movement of the cursor is handled outside the "pure" nedit code, maybe 
in Motif (et.al.) or in the X server itself.  

Randy Kramer

(The reason for the question has to do with folding--if we leave folded (i.e., 
hidden) text in the text buffer but somehow arrange for it to not display (I 
don't know how to do that yet, I'm just imagining there might be ways), the 
cursor movement routines have to ignore that folded (hidden) text.

If those cursor movements are handled outside the "pure" nedit code, in some 
respects ignoring that hidden text might be simpler than I thought (or not).  
I'm just thinking that the actual cursor movement on the screen, if handled 
by X or Motif, would work appropriately with the text that is on the screen 
(i.e., it would ignore that hidden text) with little or no effort on our 
part. 

Of course, when NEdit needs to know where the cursor is (which,iiuc, it asks 
about at times), NEdit has to convert whatever answer it receives to ignore 
hidden text.  (Maybe the problem is neither easier nor harder, maybe just 
different than what I expected.)