Keeping ProjectTree on the left and taglist on the right
bora
Hi all,
I am playing with eclim and it seems a very promising. Thanks for all
the contributors. However, I have one problem.
Normall I use NerdTree on the left and Taglist on the right. Between
them there is/are buffer window(s) and at the bottom quickfix for
search and build results.
When I want to use ProjectTree together with Taglist, things does not
work like the above setup. When there is only ProjectTree, it is on
the left like NerdTree. When I open taglist with tlistToggle, then
ProjectTree and taglist end up on the right side with horizantally
splitted. I do not prefer this schema. Instead ProjectTree on the left
and taglist on the right is better for me. I can optionally open
NerdTree on the left if I need it. (NerdTree and ProjectTree
combination does cause any problem in this regard)
How can I achieve this?
PS: Commit 695d48e did not work, though it is related to Buffers cmd
as far as I see.
--
Bora Sahin
Eric Van Dewoestine
>
> Hi all,
>
> I am playing with eclim and it seems a very promising. Thanks for all
> the contributors. However, I have one problem.
>
> Normall I use NerdTree on the left and Taglist on the right. Between
> them there is/are buffer window(s) and at the bottom quickfix for
> search and build results.
>
> When I want to use ProjectTree together with Taglist, things does not
> work like the above setup. When there is only ProjectTree, it is on
> the left like NerdTree. When I open taglist with tlistToggle, then
> ProjectTree and taglist end up on the right side with horizantally
> splitted. I do not prefer this schema. Instead ProjectTree on the left
> and taglist on the right is better for me. I can optionally open
> NerdTree on the left if I need it. (NerdTree and ProjectTree
> combination does cause any problem in this regard)
>
> How can I achieve this?
I checked in a fix[1] to prevent the project tree from merging with
the taglist window if they are configured to display in different
locations.
[1] https://github.com/ervandew/eclim/commit/a00d92b3ef3913228f9edb07a5de3552cb3f005e
> PS: Commit 695d48e did not work, though it is related to Buffers cmd
> as far as I see.
Can you give me an example of a case where it didn't work for you?
> --
> Bora Sahin
--
eric
bora
Hi Eric,
Wov! You entered a fix in hours after I mentioned about a usage
scenario. Thank you very much.
>
> > How can I achieve this?
>
> I checked in a fix[1] to prevent the project tree from merging with
> the taglist window if they are configured to display in different
> locations.
>
It seems that this fixes the problem. Needs more testing on my side.
Thanks again.
>
> > PS: Commit 695d48e did not work, though it is related to Buffers cmd
> > as far as I see.
>
> Can you give me an example of a case where it didn't work for you?
was experiencing but did not, and actually this is what it should be
expected from commit 695d48e. I could not create the problem "commit
695d48e" supposed to solve so I can't give you a case.
However, :Buffers might be promising if it is updated lively. The case
in point: Sometimes we tend to open lots of buffers and because of
this, buffer numbers goes very high. For example, the open buffer
count is 15 but the biggest buffer number is 43. This causes some
problems when it comes to buffer management (navigation etc.). If
there is buffer number recycling, it would be nice. As far as I
see :Buffers does this. It uses different buffer numbers than Vim's
numbers and recycles it. For example, if :Buffers number 3 is deleted
the next Buffer number will be 3 again, but in Vim's point, it will be
5 (I assumed their starting number is the same) Do I understand it
correctly?
PS: "let g:EclimTagListEnabled=0" is the correct setting? I use Eclim
1.7.2
--
Bora Sahin
Eric Van Dewoestine
>
> Hi Eric,
>
> Wov! You entered a fix in hours after I mentioned about a usage
> scenario. Thank you very much.
>
> >
> > > How can I achieve this?
> >
> > I checked in a fix[1] to prevent the project tree from merging with
> > the taglist window if they are configured to display in different
> > locations.
> >
> > [1]https://github.com/ervandew/eclim/commit/a00d92b3ef3913228f9edb07a5de...
>
> It seems that this fixes the problem. Needs more testing on my side.
> Thanks again.
>
> >
> > > PS: Commit 695d48e did not work, though it is related to Buffers cmd
> > > as far as I see.
> >
> > Can you give me an example of a case where it didn't work for you?
>
> Actually I thought it might cure the problem (commit a00d92b solved) I
> was experiencing but did not, and actually this is what it should be
> expected from commit 695d48e. I could not create the problem "commit
> 695d48e" supposed to solve so I can't give you a case.
>
> However, :Buffers might be promising if it is updated lively.
At some point I may add live updating, but my initial goal for
:Buffers was to just be a more user friendly version of vim's default
:buffers command.
> The case
> in point: Sometimes we tend to open lots of buffers and because of
> this, buffer numbers goes very high. For example, the open buffer
> count is 15 but the biggest buffer number is 43. This causes some
> problems when it comes to buffer management (navigation etc.). If
> there is buffer number recycling, it would be nice. As far as I
> see :Buffers does this. It uses different buffer numbers than Vim's
> numbers and recycles it. For example, if :Buffers number 3 is deleted
> the next Buffer number will be 3 again, but in Vim's point, it will be
> 5 (I assumed their starting number is the same) Do I understand it
> correctly?
Well, :Buffers doesn't display the actual buffer number, so I assume
you're referring to the line number displayed in the :Buffers window.
> PS: "let g:EclimTagListEnabled=0" is the correct setting? I use Eclim
> 1.7.2
That variable no longer exists since eclim's taglist was broken out
into a separate plugin[1].
[1] https://github.com/ervandew/taglisttoo
--
eric
bora
> At some point I may add live updating, but my initial goal for
> :Buffers was to just be a more user friendly version of vim's default
> :buffers command.
>
> Well, :Buffers doesn't display the actual buffer number, so I assume
> you're referring to the line number displayed in the :Buffers window.
gets a bit more cumbersome.
Could you please point me how I can achieve this? Where should I look
at? What pieces of code can I refer to? I have not done anything with
VIM scripting.
> > PS: "let g:EclimTagListEnabled=0" is the correct setting? I use Eclim
> > 1.7.2
>
> That variable no longer exists since eclim's taglist was broken out
> into a separate plugin[1].
>
> [1]https://github.com/ervandew/taglisttoo
--
Bora Sahin
Eric Van Dewoestine
>
> > At some point I may add live updating, but my initial goal for
> > :Buffers was to just be a more user friendly version of vim's default
> > :buffers command.
> >
> [Snip]
> >
> > Well, :Buffers doesn't display the actual buffer number, so I assume
> > you're referring to the line number displayed in the :Buffers window.
>
> Yes, exactly. I think if you open lots of buffers buffer management
> gets a bit more cumbersome.
>
> Could you please point me how I can achieve this? Where should I look
> at? What pieces of code can I refer to? I have not done anything with
> VIM scripting.
Eclim's :Buffers logic is located here:
https://github.com/ervandew/eclim/blob/master/org.eclim.core/vim/eclim/autoload/eclim/common/buffers.vim
It's also worth noting that there are several other existing buffer
management plugins, so be sure to check some out, there may be one
which already does what you want.
> > > PS: "let g:EclimTagListEnabled=0" is the correct setting? I use Eclim
> > > 1.7.2
> >
> > That variable no longer exists since eclim's taglist was broken out
> > into a separate plugin[1].
> >
> > [1]https://github.com/ervandew/taglisttoo
>
> Okay, I see.
>
> --
> Bora Sahin
--
eric