|
From: <du...@sp...> - 2010-06-30 05:24:45
|
Alan Ezust writes: > On Tue, Jun 29, 2010 at 3:41 PM, Dushan Mitrovich <du...@sp...> wrote: >> I'm using jEdit 4.3.2 under Mac OS X.6.4, and have a question and a >> suggestion: >> >> Question: >> For the last several versions jEdit, opening a text-file from a >> file manager (such as >> Path Finder or muCommander) will start jEdit (assuming it's not >> already started) with >> a blank window, but the text-file itself will not be loaded. If >> jEdit was already open >> the invoked text-file will load into jEdit. Is there a fix or >> work-around to this behavior? > > I've noticed this too. It seems like every other time I start jEdit up, > there are empty buffers. Reload doesnt work, and I have to close and > re-open to see it. > > I was not sure if this was a jEdit bug, or a bug in ProjectViewer > (which I think was responsible for trying to open the file). Your > observation makes me think it is jEdit and not PV. > > It is a bug, and if you can reproduce it, please file a bug report > with the exact steps. I haven't had a reliable way to reproduce it > yet. I can reproduce it easily - in fact, can't help but reproduce it. I'll file a bug report. Thanks for the suggestion. >> Suggestion: >> Often I need to edit text-files in the same directory (folder). >> But every time I ask >> jEdit to open a file (Cmd-O) the dialog window displays the >> Applications folder, in >> which, of course, jEdit.app resides. While jEdit remains open (but >> not necessarily >> the OpenFile window), it would make sense that the OpenFile window >> also stays >> pointed at the most-recently used folder, rather than reverting to >> the Applications >> folder. This would let the user open a neighboring (same >> directory) text-file without >> having to re-specify the same folder. Or is it already possible to >> configure jEdit to >> behave this way? > > Global Options - File System Browser - general - default path. Terrific - thanks. Guess I just didn't look hard enough. - Dushan |