On Wed, Dec 14, 2011 at 3:29 PM, Terry Brown <[email protected]> wrote:
> This just got me again - in complex environments like web app. servers > it doesn't occur to you that the file isn't being saved, instead you > start looking to see if the javascript files are being grabbed from the > wrong place by the http server or something... > > I think Leo needs to get seriously in your face every time you try to > save an outline with @ignore in and @<file>. Maybe we need an > @ignore-quietly for cases where it's intended. You and Hans agree, and I am beginning to appreciate the problem more fully. I don't like @ignore-quietly, but changing @<file> to @@<file> will do the same thing, and moreover is visible just by looking at the headline. And if you want to make it more visible, just use @@@@<file> ;-) In short, I am now willing, on an experimental basis, to have Leo put up a dialog when inserting an @ignore, and also when writing an @<file> node containing @ignore. In the past, I have always found read/write dialogs to be a) intrusive and b) panic-inducing, but this may be a tolerable exception. We shall see. 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.
