On Sun, Nov 26, 2017 at 1:01 PM, Matt Wilkie <[email protected]> wrote:
> How should this be documented so that people will be sure to see it? >> >> For sure there should be some instructions somewhere in the download page >> <http://leoeditor.com/download.html> and also somewhere in this doc tree >> <http://leoeditor.com/getting-started.html>. >> > > My very next question and task ;-) I'm unfamiliar with the process flow > of where things get written to where they are read. Do I simply edit > *'leo\doc\LeoDocs.leo', > *use [make-sphinx] button, and then git commit? > Yes. Edit LeoDocs.leo and do a git commit. If you like, uou can do make-sphinx as a syntax check on the rST code and the look of the result .html files. But it's not strictly necessary. I am the only one who knows the password needed to upload the files to my brother's server, so I'll have to make the files myself before uploading them. I am good tester in this regard because I haven't been following your work >> closely and have little idea how people would use pip install. >> > > Oh good! Perhaps hold off until I get the first draft 'how and when to > install with pip' thingy written. > Let me know when you update LeoDocs.leo. 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 [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.
