Hello Edward, On 3 Feb., 21:15, "Edward K. Ream" <[email protected]> wrote: > On Feb 3, 2:05 pm, "Edward K. Ream" <[email protected]> wrote: > > > Thanks for the confirmation. There will be more testing needed after I > > switch over to KeyStroke objects instead of strings. > > Rev 4971 contains the *disabled* new code. It should work exactly as > before, but one never knows. Please report any problems immediately. > Tomorrow I'll push the enabled new code. Until then I'll be eating my > own dog food. > > Here is the checkin log: > > QQQQQ > Added scaffolding for the transition to KeyStroke objects instead of > canonicalized strings: > > - Added g.new_strokes, g.isStroke and g.isStrokeOrNone. > - All new code is enabled by g.new_strokes, which is False at present. > > After this commit I'll get g.new_strokes = True and see what > happens ;-) > > All expected unit test pass at present with Python 2.x/3.x. > QQQQQ >
with this revision '@tabwidth -4' is no longer honoured. If I use '-> (TAB)' leo advances 5 characters. - If I then hit ENTER it starts in the new line after 4 characters. With kind regards, Viktor -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
