> > I seem to remember that the sidebar directory tree would follow the
> > current directory. In other words, if I'm in my home directory, the
> > /home/<username> folder would be expanded in the sidebar directory
> > tree, and then if I use a directory buffer to navigate to a different
> > folder (or if I use the directory buffer list to select a new buffer),
> > the sidebar directory tree would refresh itself to the new location.
> > That behavior seems to be missing for the last few releases. Or am I
> > just imagining things?
I'm a bit confused by all of this myself.
If I hit Ctrl D right now, using 0.18.1.13+ to compose this message, I
get (as expected) a directory buffer on my home directory, but the tree
comes up looking at /, which seems wrong; I would have expected the
tree to be open to /home/peter.
The official 0.18.1 release seems to have the same problem.
0.15.3 (which I happen to have lying around for some reason) seems to
work correctly: if I open a directory buffer on /home/peter, the tree
opens to /home/peter too.
So I'm thinking something broke, and then I get your second message...
> OK, I have a little more detail. I just re-built my prefs file and most
> of the functionality appears to have returned.
I don't think the prefs file should have anything to do with this. What
did you change?
> Here's what's not working as I expected: I opened two files located in
> different directories, /home/briz/.j/prefs and /home/briz/web/test.html.
> Both files show up in my directory buffer list, along with a directory
> buffer item which is set to /home/briz/web. When I use the sidebar
> buffer list to click on "prefs" and then hit Control-D, the sidebar
> directory tree correctly hilites /home/briz/.j. However, when I select
> "test.html", the sidebar buffer list directory item correctly changes to
> /home/briz/web, but the sidebar directory tree doesn't select
> /home/briz/web; its tree is open only to /home/briz.
I don't really follow the scenario here, exactly, but I still think
> After trying to duplicate this several times (I can't duplicate it every
> single time), I'm beginning to wonder if it has something to do with
> caching. Does j cache the results in the sidebar directory tree?
Yes. You can force a complete refresh by doing Ctrl R in a directory
buffer. But this should only make a difference (as far as the sidebar
tree is concerned) if you create or remove a directory, which isn't
part of your scenario as I understand it.
(Note that just to muddy the waters a bit more, sidebar updates are
generally done asynchronously by the idle thread, which makes the
timing a bit unpredictable.)
In any case, I still think something broke between 0.15.3 and 0.18.1.
I'll see if I can track it down.
Thanks for reporting the problem!