On Monday, November 4, 2013 9:28:33 PM UTC+1, Terry wrote: > > Also, can I insert a new footnote, for instance between A and B, and > expect > > the system to automatically update the names of all the following nodes? > > This might be possible, although using sequence numbers to refer to > things is inherently fragile. If it was me I'd do something like > naming the footnotes #provenance, #derivation, /piers-1967, > #ibid, /doubtful etc. etc. where the # and / separate the numeric and > letter flavors. Then you could have a script process things for output > with letter and number markers in the order they first occur in the > para. >
Naturally, I don't care much what the subnodes per se are called. However, setting their name as 1,2,3,A,B,C is convenient because the reference to such nodes, in the main text, would be the same string as the nodes' name. > > Yet another question (but there are many others): can I have two > different > > keybindings for creating automatically, from the main text, the two > > different types of child notes? Ideally, while editing the main text, I > > would simply use the relevant key shortcut which will: (a) create the > > footnote link in the main text (b) create the corresponding footnote > node > > and (c) shift the focus to that newly created footnote node, ready for > > input. > > That would be straight forward. > > > I hope I am not asking too much. Also, are the above features yet to be > > implemented (programmed), or are these available features already? > > No, Leo is a very flexible platform and would probably get you where > you want to go faster than anything I can think of, but these features > don't exist currently - how common is multi sequence footnote > editing? :) > > > You see, all these practical aspects are quite important, because I am > not > > a real programmer. I can tinker a bit, but upto a certain point. Ease of > > use is important for me. > > If you have some Python familiarity you might be able to tinker with a > skeletal set up which handles the basics of the above without too much > trouble. > To be honest, my familiarity with Python is mostly limited to tinkering with other people's scripts. I am still learning. By the way, could you suggest some simple Leo scripts that I could study, so that I could learn Leo and Python at the same time? A Leo/Python learner's 101 syllabus would be very useful. > If you think the /sequence-A #sequence-B approach might work, > implementation would be quite straight forward. A key-binding to jump > from text to footnote, creating if needed, a @button command to scan > for missing references / unused footnotes, and another to generate a > throwaway version of the tree with the #names replaced with [A], [7] > etc. > Hmm. It seems that quite a bit of manual reading is required here, because frankly I did not understand much of this last paragraph. Is there ANY footnote support (like a plugin) already available for Leo? With my limited skills, I guess it would probably be much easier for me to follow the footsteps of something already implemented, rather than trying to program something new. -- 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
