>
> I am being mindful about what causes additional pain.
>

Out of curiosity, what do you believe is responsible for causing your pain? 
I have a great interest in RSI related issues when it comes to interacting 
with computers. 

I use a homerow keyboard setup using autohotkey so that I very rarely have 
to move my hands from the homerow position. Due to *extremely* reduced 
finger travel time effort is reduced, comfort level improves and overall 
computing speed improves. 

It may be possible to prevent a situation like this in the future with a 
homerow solution of your own.

Unfortunately autohotkey is a windows only application.

On Friday, November 18, 2016 at 5:24:37 AM UTC-5, Edward K. Ream wrote:
>
> ​​On Thu, Nov 17, 2016 at 8:43 PM, 'Terry Brown' via leo-editor <
> leo-e...@googlegroups.com <javascript:>> wrote:
>
>>
>> I tried changing all the @file headline text to @auto in LeoPy.leo to
>> see if it could import the Leo codebase, but the experiment's not that
>> straight forward.  Maybe you'd have a better idea of what would be
>> needed to make that test work.
>>
>
> ​I've thought of doing that.  The script would write all of Leo's core 
> files, without sentinels, to a temporary directory, and then use the @auto 
> import logic on each temporary file.​
>  
>
> ​Importer.trial_write writes the imported outline without sentinels​, so 
> that's what I would adapt for the script, or maybe even use as is.
>
> This test that should be run, at least once. Feel free to give it a try.  
> I'll be glad to help if there problems.
>
> Some files that already were @auto seemed good though.
>>
>> > Giving my hands a rest is now urgent, so I'll take a break from
>> > programming for several days.
>>
>> That's not what `git log` says :-}
>>
>
> ​Heh.  It's unbearable not to finish what I've worked so long on, 
> regardless of discomfort.  Besides ice, I am being mindful about what 
> causes additional pain.
>
> First I'll be unifying the code, by moving as much as possible into the 
> base Importer class.  This the proper, and best, way.
>
> Next, I'll explain, with examples, how to create an importer for a new 
> language. Of course, converting all existing importers to the new code base 
> will be the best kind of example. I'll do that asap.
>
> Edward
>

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Reply via email to