Timeline for What are good techniques for keeping your place in code?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 8, 2011 at 18:59 | comment | added | Spencer Rathbun | This is one of the reasons I use vim myself. But the must have feature for me, and one I have been unable to find in any other IDE, is split windows. Same file, different spots. I can be buried in a function, and have a split open to the relevant spot that calls it. It even works with different files. | |
| Sep 30, 2011 at 23:02 | comment | added | Jess Telford | @DaveKirby Awesome - I love learning new things about vim :D | |
| Sep 30, 2011 at 15:59 | comment | added | Dave Kirby | @Jess: marks are not necessarily buffer local. Marks using capital letters are global. | |
| Sep 30, 2011 at 6:28 | comment | added | Jess Telford | Agreed. I am an advanced beginner with vim (can use without thinking most of the time, but have barely scratched the surface), so I am sure there are things I don't know. Even still, I don't imagine it's possible to do anything such as psr's answer in vi(m) (at least, not from my research). | |
| Sep 30, 2011 at 6:10 | comment | added | mattnz | I am a Vi amature, but have seen what can be done with it in the hands of power user who's prepared to write a few short scripts, spend some time to learn to really use VIM, or change to a tool that has features setup in a way that works for you, and spent time learning that. Thats my point. Learn you tools. A good tradesman does not blame his tools, niether does a good programmer. | |
| Sep 29, 2011 at 11:47 | comment | added | Jess Telford | I agree a proper IDE is best. I use vim's great marks and tag jumping features. However, they both have limitations: marks are buffer-local, and tag histories are linear. For complex situations, this still is not enough (hence asking this question). | |
| Sep 29, 2011 at 7:57 | history | answered | mattnz | CC BY-SA 3.0 |