I looked up *ctags* so I have some idea about them now. @gar, how do you picture their use? There are a couple of existing Leo plugins that use ctags files. Personally, the functionality like that I use the most is Leo's ability to jump to method defs. I don't know how that's accomplished but it's a great feature of Leo. I have thought of trying to get that capability into this Freewin plugin. The way I see it working is that you CNTL-click on a method invocation and a new Freewin window opens up for the node where the definition is.
This would be way beyond the scope I had in mind originally, but it does seem like it could be delightfully useful. I'm not sure how tricky it would be to implement. If that is what you were thinking of, I could look into it. The thing is that I didn't devise these editing windows with programming in mind. I mostly wanted to view so-called "zettelkasten" notecards - that is, small focused chunks of textual data. So the windows don't do any syntax colorizing, and the way they are constructed I don't think that adding colorizing to the editing view would be very easy at all. Another thing I could look into ... On Sunday, June 6, 2021 at 8:42:57 AM UTC-4 tbp1...@gmail.com wrote: > Thanks for your interest! I am not sure what you are asking for. In > fact, I'm not sure what the "ctags" are. The intent of the plugin is to > focus on a single node. The plugin maintains a reference to the commander > of its underlying node, so almost anything would be possible in principle. > It would be easy enough to provide another view in addition to the editor > and RsT views it has now. > > As usual, the challenge would be to make the new view simple to use and > clean in its appearance. It would be better if it did not try to change > the outline, at least not beyond the underlying node. That's because you > might be viewing at one place but end up making changes somewhere else that > is not in sight. Also, you don't want to get into a cycle of changes to > the outline triggering a "changed" event in the Freewin window, which then > triggers a new changed event back in the outline ... > > I would also prefer to keep the plugin's code simple. Right now it is > about as simple as it could possibly be. > > But probably most anything can be done if we can get clear on what it > would be. > > On Sunday, June 6, 2021 at 2:40:00 AM UTC-4 gar wrote: > >> Hey! Thanks for your work, it's very much appreciated. I was missing such >> a function in Leo for a long time. >> And a question related to this is: can then your plugin be used to >> integrate say tree from parsed output of ctags for current file? >> This is another thing I miss very much (sure after vim editing). >> > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/518b1eae-a3af-4c53-a657-35dacb0d8b86n%40googlegroups.com.
