From: Ben W. <be...@gm...> - 2008-04-30 13:41:36
|
Andrey Halyavin wrote: > Hi Nathaniel, > > Wednesday, April 30, 2008, 5:10:05 AM, you wrote: > > >> Hi folks, >> > > >> I'm finally making the switch to jEdit from NEdit after many many >> years and I have a question about how to accomplish a certain kind of >> workflow. In NEdit, a buffer "belongs" to a single window -- it can >> only be viewed there, only appears in the tabs of that window, etc. >> This is limiting at times, but it does allow one to segregate buffers >> into related groups by window. So I would usually have one window >> that held the small collection of files I was working on while the >> other had an often very large collection of library header files open. >> Often times I would keep 3 or 4 windows open with related groups of >> library files and switch between them depending on what I was doing. >> > > >> So now that I'm using jEdit I'm having a hard time adjusting to the >> "every buffer lives everywhere" world. I'm using a vertically split >> window to place two buffers side by side. The problem is that I can't >> find a way to segregate the panes into tasks such that it's easy to >> switch among a small group of related files. Tabs become useless when >> every pane has 30 of them. The buffer switcher remains usable, at >> least, but it's not much fun to scan every open file to find the one >> I'm looking for. >> > > >> What I would really like is a buffer switcher widget that could be >> made to only show a subset of all open files -- for example, only >> files from a given directory or project, or only files matching a >> given regex. Does such a thing exist? Would it be easy to make? Any >> tips on alternate workflows? >> > > >> Thanks, >> -n8 >> > > You can create another project with .h files only (with Project Viewer > plugin) and switch between projects when you need them. > > Andrey Khalyavin That's possibly a workaround, but switching sessions causes all your buffers to be closed and the new set of files to be opened - hardly ideal (the two issues I can see off the top of my head are that it won't work with unsaved changes in open buffers and that closing/re-opening lots of files is a fair time hit). I actually think completely seperate views like the original poster suggested could be a very very useful feature. - Ben -- "Everybody generalizes from one example. At least, I do." - Steven Brust [dreamcafe.com] |