Re: Message compose temp file disappearing
Brendan Barnwell <[email protected]>
| Newsgroups | gmane.mail.mahogany.user |
|---|---|
| Message-ID | <[email protected]> |
On Tue, 27 Jul 2004 10:45:39 +0200 (Romance Daylight Time) Xavier Nodet <[email protected]> wrote: > > Hmmm, yes, it just happened and I saw that message -- but the > > editor was still running. I'll see if I can see any more pattern > > to what's causing it to think the editor has closed. > > Would it be the case that your editor reuses an already existing > instance of itself? I suppose this could explain the behavior you > see: as the copy of the editor ends, M supposes that the editing > task is over, while it is actually going on in the other running > copy of your editor. You're right, that's exactly it. This is irritating behavior, however -- I use this editor specifically because it allows me to open multiple documents in a single instance. Would it be possible for Mahogany to update the compose window by monitoring the temp file itself rather than the editor process? I frequently have an editor window open with several files, then I go to check my email. It seems that the current situation requires me to close everything I'm doing and let Mahogany have its own editor. Of course, Mahogany presumably uses the process information in order to do that thing it does where it blocks typing the compose window while the editor is open. Personally, though, I don't care much for this feature. I'd much prefer it to simply update the compose window when the temp file changes, and not attempt to "enforce" the external editor usage by making sure I close it before doing anything else. -- --Brendan Barnwell "Do not follow where the path may lead. Go, instead, where there is no path, and leave a trail." --author unknown ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click