Offray Vladimir Luna Cárdenas <[email protected]> 于2018年10月12日周五 上午12:21写道： .... > Most of my documentation happens today in my own interactive outliner > and not in Leo, but I remember having simple Leo outlines I wanted to > share about my workflow with Markdown that where relatively > self-contained via @buttons. Maybe today they're supersede by Leo > developments regarding Markdown external files and they could contain a > lot of newbie code, but at that moment I felt pretty proud of them. We > could have a place where Leo users could share the knowledge they have > by sharing .leo files that exemplify how Leo helps in making their > concerns and workflows possible. >
can not agree more for this: Leo is great , and Leo's user community is great too, so just need open the door for Leonista show all kinds of Leo usage skills ;-) > For example, once Leo is installed, I would like to have a set of > notebooks that show me how to use Leo to bootstrap itself and the Python > ecosystem (specifically the data related one). A Leo notebook that > installs Conda/Git and contains recipes/nodes to load interesting > notebooks, converting from Org/Jupyter to Leo and so on. > > Hope this helps, > > Offray > > On 10/11/18 2:56 AM, Zoom.Quiet wrote: > > <[email protected]> 于2018年10月11日周四 下午2:06写道： > >>> Yes, i meet same problems, > >>> but the reason is simple: > >>> - Leo release so many years, but the core developer always only EKR > >>> - so means more and more knowledge for EKR as natural truth, not need > >>> explain > >>> - and servicing big document.leo project is not funny and tired... v > >> Now that I think about it, I think you hit the nail on the head. Edward > >> knows the software and code too well, and so it's hard for him to see it > >> from a new user's perspective. If anyone is up for it, it may be best that > >> a revamped documentation is done by others, with Edward looking over to > >> make sure it's not inaccurate. > >> > >> My smaller dream was that I become well versed enough in Leo programming > >> that I would then write my own documentation as a series on my site - > >> starting from the basics of scripting to more advanced usage. I wanted to > >> take features I liked in Emacs and port them to Leo and show how it's done > >> - mostly because I really think many, many programmers out there would use > >> Leo if they only knew how to. People learn a fairly foreign language > >> (Emacs Lisp) to customize their editor. Many more would rather just do it > >> in Python. I don't know if I'll ever become knowledgeable enough to get to > >> that point, though. > >> > > as ur another mail suggest: > > I'm suggesting that there be an Examples directory in the > > distribution, where any file in it or a sub directory of it is treated > > as such a template. It would contain live documents for plugins, > > workflows, debugging demos, design notes, generic add a language demo, > > unit test demo, todo plugin demo, etc. > > > > ... > > > > in fact in any tech community, there is one hide rule: > > propose by who, make it by who ;-) > > > > just like EKR, not understand literature programming, > > so build Leo to make literature programming environment for everyone. > > > > base the document problems, u r so right: > > - want EKR writing friendly document for fresh people, is not the good solve > > - but start with anlifer uself, is very good: > > -- fork Leo repo. > > -- append Examples directory > > -- start write down all kinds of u feel need demo/doc./test/... > > > > so EKR and other people can work with your fork, > > when the Examples sub path, grow enough, Pull-Request back distribution > > repo. > > Bazinga ;-) > > you create new age for Leo document. > > > > > > > > > > > >> -- > >> 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. -- life is pathetic, go Pythonic! 人生苦短, Python当歌! 俺: http://zoomquiet.io 授: http://creativecommons.org/licenses/by-sa/2.5/cn/ 怒: 冗余不做,日子甭过!备份不做,十恶不赦! KM keep growing environment culture which promoting organization learning! -- 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.
