Hello fellow vim users!
I use vim for all my coding and text editing needs. Until now I've
only used it for small projects with all files in a single folder,
nothing complicated. However, my current job involves a lot of jumping
around between files in very different file hierarchies, copying
pas
Hello fellow vim users!
I use vim for all my coding and text editing needs. Until now I've
only used it for small projects with all files in a single folder,
nothing complicated. However, my current job involves a lot of jumping
around between files in very different file hierarchies, copying
pas
Date: Mon, 5 Jan 2009 12:01:54
To:
Subject: Navigating complicated file hierarchies
Hello fellow vim users!
I use vim for all my coding and text editing needs. Until now I've
only used it for small projects with all files in a single folder,
nothing complicated. However, my current job in
On Monday 05 January 2009 5:01 am, Per Thulin wrote:
as i attempt to respond to this post no-one else has yet
posted a reply -- i am sure this will change, and others'
replies may be more to your liking, but here goes
> I use vim for all my coding and text editing needs. Until now I've
> only u
>1. Use bash to jump around in the system and open/close new Vim
>instances when I need to edit something. This makes it easy to
>navigate the file system but doesn't work when I need to copy/paste
>content from e.g. /foo/b/c/d.txt to /bar/a/b/c/d.txt, as I need both
>these files open in the same
On Mon, 2009-01-05 at 12:01 +0100, Per Thulin wrote:
> Hello fellow vim users!
>
> I use vim for all my coding and text editing needs. Until now I've
> only used it for small projects with all files in a single folder,
> nothing complicated. However, my current job involves a lot of jumping
> aro
> So my question is: how do you manage long file hierarchies in vim?
If those files belong to a project, I'd suggest to use one of the
related plugins for project management. For obvious reasons, I'm
partial to tselectfiles. In general, people recommend project.vim[2]
You didn't tell us which fi
Per Thulin wrote:
> Hello fellow vim users!
>
> I use vim for all my coding and text editing needs. Until now I've
> only used it for small projects with all files in a single folder,
> nothing complicated. However, my current job involves a lot of jumping
> around between files in very different
On Monday 05 January 2009 1:29 pm, _sc_ wrote:
> if you have the benefit of konsole supplying your bash
> shell, you can have many shells open in the same window,
> each with its own path -- ctrl-shift-n will open new shells,
> and shift-cursor-left or shift-cursor-right will navigate
> around in
On 05/01/09 12:01, Per Thulin wrote:
> Hello fellow vim users!
>
> I use vim for all my coding and text editing needs. Until now I've
> only used it for small projects with all files in a single folder,
> nothing complicated. However, my current job involves a lot of jumping
> around between files
On 05/01/09 20:36, Reid Thompson wrote:
[...]
>
> http://www.vim.org/scripts/script.php?script_id=95
>
I notice that the screenshot link on that page is 404 not found (I
didn't try the other links), and the author's email bounces (User unknown).
Best regards,
Tony.
--
The goal of science is t
Tony Mechelynck said:
>
> There are several methods depending on your exact needs and procedures.
>
> For the kind of use-case described above, I think that I would use
> split-windows in one Vim instance (probably gvim but YMMV), with
> different local directories in different windows thanks
On 06/01/09 08:34, Per Thulin wrote:
> Hello fellow vim users!
>
> I use vim for all my coding and text editing needs. Until now I've
> only used it for small projects with all files in a single folder,
> nothing complicated. However, my current job involves a lot of jumping
> around between files
Thanks guys, I did not expect this much response and your answers have
been very helpful!
Someone asked me about which filetypes I work with and which terminal
application and desktop environment I'm using. I'm mostly editing
python source code and xml files, so I use vims indentation and syntax
Per Thulin wrote:
> I've had bad experience with using the systems clipboard as
> the resulting text often get very weird indentation
If you are pasting into console/terminal Vim (not gvim), see:
http://vim.wikia.com/wiki/Toggle_auto-indenting_for_code_paste
BTW it would be really easy for someo
On 06/01/09 10:06, Per Thulin wrote:
> Thanks guys, I did not expect this much response and your answers have
> been very helpful!
>
> Someone asked me about which filetypes I work with and which terminal
> application and desktop environment I'm using. I'm mostly editing
> python source code and
> When this comes up for me, I generally use the NERD tree plugin.
>
> There is, iir, method to make vims buffers global among all active vim
> sessions, but I do not recall the specifics.
>
> Thanks,
> Chris
Can't recommend the NERDtree plugin enough, means the entire coding
side of my deve
I use glob open plugin and MRU.
I think glob open is similar to the fuzzy finder plugin. However you can
still apply black and white filters and the first search result to find
the file you're looking for faster.
Navigating files can be done in many ways. You didn't tell us the most
important th
First of all, that gf command is awesome, didn't know about it! Thanks!
> Navigating files can be done in many ways. You didn't tell us the most
> important thing: How do you know which file you want to edit?
Well in python there are import statements, but they don't
necessariliy match file syst
Per Thulin wrote:
> Well in python there are import statements, but they don't
> necessariliy match file system paths. Maybe there's a script
> available to follow an import statement using the environment
> variable PYTHONPATH or something.
We have a tip:
http://vim.wikia.com/wiki/Automatical
(This is my first post in this group!)
Some notes you might find helpful:
1. I'd like to second whoever recommended GNU screen. It's great, and
you should learn to use it. Note that screen has its own virtual
terminal copy and paste functionality, which is occasionally useful.
2. As far as ente
itai wrote:
> (This is my first post in this group!)
Welcome, and thanks for the informative message.
For the future, please "bottom post". That is, quote a *small* relevant
part of the message you are replying to, then put your reply underneath.
I am periodically spraying the above advice in a
On 8 jan 2009, at 20.19, itai wrote:
> (This is my first post in this group!)
Welcome!
> 1. I'd like to second whoever recommended GNU screen. It's great, and
> you should learn to use it. Note that screen has its own virtual
> terminal copy and paste functionality, which is occasionally useful.
On Tue, Jan 13, 2009 at 17:22, Per Thulin
wrote:
> One simple little integration thing that would fix it all would be if could
> do this:
>
> 1. From vim, run :shell
> 2. Find the files I'm after
> 3. Open these in the vim session I ran :shell from.
>
> Hold your hats now, but Emacs users can do
On Tue, Jan 13, 2009 at 18:51, Itai Fiat wrote:
> On Tue, Jan 13, 2009 at 17:22, Per Thulin
> wrote:
>>
>> 1. From vim, run :shell
>> 2. Find the files I'm after
>> 3. Open these in the vim session I ran :shell from.
>
> This sound incredibly useful. This idea has never occurred to me, but it i
On Tue, Jan 13, 2009 at 3:22 PM, Per Thulin
wrote:
> [...]
>
> One simple little integration thing that would fix it all
> would be if could do this:
>
> 1. From vim, run :shell
> 2. Find the files I'm after
> 3. Open these in the vim session I ran :shell from.
>
> Hold your hats now,
On Tue, Jan 13, 2009 at 11:50 PM, Antony Scriven
wrote:
> On Tue, Jan 13, 2009 at 3:22 PM, Per Thulin
> wrote:
>
> > [...]
> >
> > One simple little integration thing that would fix it all
> > would be if could do this:
> >
> > 1. From vim, run :shell
> > 2. Find the files I'm after
On Tue, Jan 13, 2009 at 07:09:15PM +0200, Itai Fiat wrote:
> On Tue, Jan 13, 2009 at 18:51, Itai Fiat wrote:
> >> 1. From vim, run :shell
> >> 2. Find the files I'm after
> >> 3. Open these in the vim session I ran :shell from.
> > This sound incredibly useful. This idea has never occurred to
On Jan 8, 1:19 pm, itai wrote:
> 4. The vim help files seem to recommend against using 'autuchdir'. I
> use the following:
> autocmd BufEnter * lcd %:p:h
>
> (Seehttp://vim.wikia.com/wiki/Set_working_directory_to_the_current_file
> .)
>
Regarding 'autochdir'...why is it that the help files
> I've been using autochdir...the only broken thing I've noticed is
> saving and restoring sessions
The same here. I don't think it will break too many other plugins
since without that option you cannot make any assumptions about the
current directory anyway. The autocommand is probably worse bec
On Tue, Jan 20, 2009 at 1:03 PM, Ben Fritz wrote:
>
> On Jan 8, 1:19 pm, itai wrote:
>
>> 4. The vim help files seem to recommend against using 'autuchdir'. I
>> use the following:
>> autocmd BufEnter * lcd %:p:h
>
> Regarding 'autochdir'...why is it that the help files recommend
> against usi
On Tue, Jan 20, at 10:24 Tom Link wrote:
>
> > I've been using autochdir...the only broken thing I've noticed is
> > saving and restoring sessions
>
> The same here. I don't think it will break too many other plugins
> since without that option you cannot make any assumptions about the
> current
On Tuesday 20 January 2009 12:37 pm, Matt Wozniski wrote:
>
> On Tue, Jan 20, 2009 at 1:03 PM, Ben Fritz wrote:
> >
> > On Jan 8, 1:19 pm, itai wrote:
> >
> >> 4. The vim help files seem to recommend against using 'autuchdir'. I
> >> use the following:
> >> autocmd BufEnter * lcd %:p:h
> >
>
> Hold your hats now, but Emacs users can do this. From Emacs they do
> the equivalent of running :shell, then navigate to another directory
> which becomes Emacs working directory. Now they can do the equivalent
> of :e .
>
> Thanks!
> -Per Thulin
hi Per,
i had the same need as you, and indeed
Per Thulin wrote:
> Hello fellow vim users!
> [snip]
> 2. Have one Vim instance and use :Ex to navigate the file system. The
> biggest problem with this setup though is that when I've navigated to
> a different folder, I can't use :e to open a new file in this same
> folder because the working dir
I've updated the tip mentioned to include more emphasis on
'autochdir':
http://vim.wikia.com/wiki/Set_working_directory_to_the_current_file
I tried to incorporate our discussion about 'autochdir' and the
autocmd mentioned to do the same. Are there any concerns I missed? I'd
like the "Caveats" se
36 matches
Mail list logo
