On Sun, Feb 22, 2009 at 6:56 PM, Edward K. Ream <[email protected]> wrote: > On Sat, Feb 14, 2009 at 2:36 PM, Kent Tenney <[email protected]> wrote: >> >> I say 'read' because in vim the command ':r(ead) <filename>' will >> place the content of <filename> into the current buffer at the cursor >> position. >> >> and ':e(dit) <filename>' creates a new buffer associated with <filename> >> >> maybe ctrl-o should list .leo files, ctrl-e select from all, create @auto >> nodes, >> ctrl-r place file contents into current node. >> >> Too vimcentric? What are the emacs equivalents? > > Geeze, it's been a week, and this was supposed to be a 3-day bug :-) > > Good questions. Imo, the actual names don't matter as much as the > operations they name. The question is, what use case (or cases) do we want > to support cleanly? > > In other words, we need something akin to opening a file in Emacs or vim and > optionally modifying and saving the file. > > @auto is the obvious candidate to use. We "slurp" all the text into the > node. > > But, alas, that only works the first time. That is, @auto will, by default, > *parse* the file, and there may be whitespace errors when that happens. > > My second thought was @nosent, but that fails because it doesn't do a > import/read. > > Looking at the plugins, it looks like the at_folder and at_view plugins do > roughly what is wanted. I'll investigate further, but in any case, it > appears we need an entirely new kind of @<file> directive to handle this use > case. > > I'm not sure what to call it. Maybe @view (as in the plugin) . Maybe > @open?? I don't think @slurp will fly :-) Any suggestions? > > Edward > > P.S. Whatever name is chosen, it should be relatively easy to implement. > Even if it weren't easy, it would be worth doing to help newbies and > others. This is a major hole that must be plugged immediately.
To review, we are discussing: - capability to register a node with an external file, allowing editing the file from Leo, adding no sentinels to the external file. - offer the option of parsing the external file into nodes which reflect the structure of the content - offer the option of not parsing the external file, it's entire content is in the body of the @auto <filename> node What if a button named 'Parse' would toggle the file between 'all in one node' and 'reflect the structure of the file' > > EKR > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
