> I'll be writing more about the new importers in an "info" github issue.
> This issue probably should remain open indefinitely.​
If any of the concerns re GitHub being a private company that could start 
charging or whatever whenever eventuate, it's useful to think about git vs. 
GitHub add ons.
A permanently open issue on GitHub would be ok, but a better fit might be a 
wiki page on GitHub - each project has its own wiki space.  However, I'd argue 
for a third option, a hierarchy of .md files in the Leo repo. in an appropriate 
subdir. Two reasons - it's part of the repo. then, zero issues should Leo ever 
leave GitHub, and also, perhaps more importantly, last time I checked, searches 
on GitHub don't search the wiki pages, while they do search repo. files.
Remember that GitHub will render .md files in the repo., and you can edit them 
through GitHub there, so editing / viewing experience is similar.
You can download both wiki (as a separate git repo.) and issues (in some JSON 
API format I think) from GitHub, should you be leaving GitHub, but the format 
of the issues in particular has work involved in making it into searchable 
docs. again.
Cheers -Terry

 
      From: Edward K. Ream <[email protected]>
 To: leo-editor <[email protected]> 
 Sent: Wednesday, November 9, 2016 11:31 AM
 Subject: Re: The coffeescript importer was broken recently
   
​​On Wed, Nov 9, 2016 at 9:00 AM, Edward K. Ream <[email protected]> wrote:

Actually, it might have been broken for a long time.

I've just noticed that the coffeescript importer had disabled the perfect 
import checks, so running its unit tests was essentially useless.  I've hooked 
up the tests now and they are failing.  I'll fix them today.


​Done at 8fd9109.

The work on the new importers is going spectacularly well. The code has 
completely collapsed. There is no longer any confusion about method names or 
location.  It's all amazingly simple.  But it hasn't been easy to create this 
simplicity.  I could not have done it without Leo.

For the first time I see that importers are all about leading whitespace. 
Splitting the input lines into separate nodes is secondary.

I'll be writing more about the new importers in an "info" github issue.  This 
issue probably should remain open indefinitely.​

EKR-- 
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.


   
 

-- 
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 [email protected].
To post to this group, send email to [email protected].
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