On Thu, Mar 12, 2009 at 4:32 PM, Ville M. Vainio <[email protected]> wrote:
> > On Thu, Mar 12, 2009 at 11:14 PM, Edward K. Ream <[email protected]> > wrote: > > >> Let's say you have 2 spaces in a leo node (no matter how deeply > >> indented it is inside @others). Just make that result in 2 spaces in > >> the derived file. > > > > This won't work without a major revision to the write code. It's way > past > > heroic. > > This doesn't seem any harder than using special annotation like \=4 > (or whatever it was). Just interpret 2 spaces as \=2 (though I'm not > sure what you meant by \=N exactly. Yes, I think you are right about the complexity. It's not *that* hard to do. But it does imply non-trivial changes to the sax-read code, and I would rather not go there. I'll keep this idea in reserve. It certainly is clever. However, I won't do this any time soon, for several reasons: 1. Eliminating the write_strips_blank_lines options, thereby permanently *enabling* it, should work well in the Leo community. It's the simplest thing that could possibly work. This morning I realized I've been worrying too much about the Zope sprint. Leo doesn't have to be "perfect", nor does it have to please every programmer on the planet. 2. The trick you propose promises one thing and delivers another. In that sense, it is quite confusing. True, most people won't notice, but I simply am not comfortable with it. In conclusion, I would like to see whether simply stripping whitespace from blank lines will work. If it does, we are done. If it creates real problems, we can revisit this idea, or others. Edward --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
