Just a quick question about the overal goal of the project. Would vim
just become an editor inside eclipse? Or would we be able to still use
vim inside eclipse but still use code completion say from plugins like
zends php project for eclipse or phpeclipse or any of the languagle
specific plugins? Thanks
--Brendon

On 3/30/07, Sebastian Menge <sebastian.menge@...> wrote:
> Hi all
>
> After a long time of no activity we restarted the work on a small plugin
> to embed vim into the Eclipse IDE.
>
> See http://vimplugin.sf.net and http://sf.net/vimplugin for details.
>
> If you are familiar with eclipse, there is an update site
> http://vimplugin.sf.net/update with the latest build.
>
> Microsoft users have to use the cygwin version of vim.
>
> We also have a prototype of an eclipse-plugin that talks to a gvim that
> acts as "netbeans" server (:help netbeans).
>
> More detailed info on that can be found here:
>
http://vimplugin.svn.sourceforge.net/svnroot/vimplugin/branches/vimclient/doc/RE\
ADME
>
> Both projects are standard eclipse projects that can be checked out
> anonymously via subversion (you need subclipse then):
>
> http://vimplugin.svn.sourceforge.net/svnroot/vimplugin/trunk/vimplugin
> http://vimplugin.svn.sourceforge.net/svnroot/vimplugin/branches/vimclient
>
> This time we'll keep an better eye on community building: So please try
> it out and give some feedback. On http://sf.net/projects/vimplugin you
> can find forums and of course mailinglists.
>
> Best regards, Sebastian.
>
>

Alexei Alexandrov wrote:
> Hi All!
>
> When spell checking is on by default, quick fix window is full of spell
checking errors. Probably it should have off always, shouldn't it?
>

Spell checking is off by default (the default for 'spell' is off). If it is on
in a window you create, it must be because you set it yourself, maybe in your
vimrc.

To avoid setting it in "special" windows, use something like

	 :autocmd BufNewFile,BufReadPost * if &buftype != ''
		 \ | setlocal nospell | endif


Best regards,
Tony.
--
hundred-and-one symptoms of being an internet addict:
157. You fum through a magazine, you first check to see if it has a web
       address.

Hi All!

When spell checking is on by default, quick fix window is full of spell checking
errors. Probably it should have off always, shouldn't it?

--
Alexei Alexandrov

Am Sonntag, den 01.04.2007, 13:33 -0400 schrieb Silent1:
> Just a quick question about the overal goal of the project. Would vim
> just become an editor inside eclipse? Or would we be able to still use
> vim inside eclipse but still use code completion say from plugins like
> zends php project for eclipse or phpeclipse or any of the languagle
> specific plugins? Thanks
> --Brendon

[replying to vim-dev only]
[crossposting to vimplugin-devel]

The overall goal of the project is to tightly integrate vim into
eclipse. That means that the developer should choose what features of
what program to use.

On a higher level the idea is to treat vim as real editor component but
to let other things like compiling, cvs/svn, integration of
api-documentation, large scale refactorings, perhaps gui-building to the
IDE.

So the spirit is "Vim is not an IDE".

The eclipse core plugin architecture uses so called "extension points"
to define its interfaces. The idea of vimplugin is to map those
extension points to vim features where possible/adequate. That means
that if phpeclipse and the like work as intended with such interfaces,
the integration with vim could work out.

Problems will come when there are redundant features: Which one is the
better? (e.g. QuickFix, Buffers)

But that's still a long way to go.

At the moment we are struggling to build a text(terminal)-based vim with
netbeans support.

>From :help netbeans-configure

> Currently, only gvim is supported in this integration as NetBeans does not
> have means to supply a terminal emulator for the vim command.  Furthermore,
> there is only GUI support for GTK, GNOME, and Motif.

Any idea why it is like that or how one could change it !?

Help or suggestions are appreciated.

Sebastian.

Sebastian Menge wrote:
> Am Sonntag, den 01.04.2007, 13:33 -0400 schrieb Silent1:
>> Just a quick question about the overal goal of the project. Would vim
>> just become an editor inside eclipse? Or would we be able to still use
>> vim inside eclipse but still use code completion say from plugins like
>> zends php project for eclipse or phpeclipse or any of the languagle
>> specific plugins? Thanks
>> --Brendon
>
> [replying to vim-dev only]
> [crossposting to vimplugin-devel]
>
> The overall goal of the project is to tightly integrate vim into
> eclipse. That means that the developer should choose what features of
> what program to use.
>
> On a higher level the idea is to treat vim as real editor component but
> to let other things like compiling, cvs/svn, integration of
> api-documentation, large scale refactorings, perhaps gui-building to the
> IDE.
>
> So the spirit is "Vim is not an IDE".
>
> The eclipse core plugin architecture uses so called "extension points"
> to define its interfaces. The idea of vimplugin is to map those
> extension points to vim features where possible/adequate. That means
> that if phpeclipse and the like work as intended with such interfaces,
> the integration with vim could work out.
>
> Problems will come when there are redundant features: Which one is the
> better? (e.g. QuickFix, Buffers)
>
> But that's still a long way to go.
>
> At the moment we are struggling to build a text(terminal)-based vim with
> netbeans support.

>>From :help netbeans-configure
>
>> Currently, only gvim is supported in this integration as NetBeans does not
>> have means to supply a terminal emulator for the vim command.  Furthermore,
>> there is only GUI support for GTK, GNOME, and Motif.
>
> Any idea why it is like that or how one could change it !?
>
> Help or suggestions are appreciated.

Vim is a single threaded application so using of windowing toolkit
facilities is the only approach to receive asynchronous notifications.
If you want Netbeans support for console you need to include polling
into relevant pieces of code.

Also I'm afraid it's impossible to create terminal emulation support for
Windows console version, just because there are no magic sequences in
windows console, you need to use respective WinAPI functions. So IMHO
it's quite pointless to create console Vim with Netbeans support for
Windows.

Personally I tried to create an Eclipse plugin for Netbeans protocol
using org.eclipse.ui.editors connection point. Currently, it's not ready
for public and I'm not improving it atm.

Hi all,

My name is David Terei, I applied for Google SOC with Vim (Eclipse
plug-in). I also applied for Mozilla (Thunderbird) and they contacted
me, telling me I have also been assigned a mentor by the Vim project and
asked me to please put them in contact with that person.

No one from Vim has tried to contact me yet so I'm just going off this
information, and I'm not sure who to contact regarding SOC (couldn't
find info on website and IRC failed as well), so I thought this would be
the next best place to ask.

Best Regards,

David Terei

Hi,
I tried to contact you about week ago (but I didn't notice, that I
must be subscribed to the list to post), and I also sent an e-mail to
Bram
last week, but I didn't get a reply.

Vim and Fityk both assigned mentors to student Diaa. I've contacted
Diaa, and he wrote me that he would choose Fityk (I'll be his mentor
from Fityk). Is it ok with you?

Cheers,
Marcin

--
Marcin Wojdyr | http://www.unipress.waw.pl/~wojdyr/

Wish: when search is slow, show the progress line number
every second on the bottom line (like, 12345 of 99999).

Maybe this can be done with plugin, I'm not sure.
Maybe simply status line can be refreshed once in a second,
temporarily setting line number to the current search position.

Some regexes take half minute to several minutes time
on multimegabyte file. It would be nice to see the progress numbers onscreen.

Thanks
Yakov

Hi,

I have a question regarding my google summer of code proposal for vim:
A mentor from the Nmap-team just asked me, wheter I would like to code for
them or for you, since he saw, that you've already assigned a mentor to me.
I saw that you haven't made any changes in the past week to my proposal
(the last modified field remained unchanged), so I am interested to know,
how likely it is for you to take me as a student during this year's summer
of code, and how you liked the proposal on persistent undo.

I hope the mentors and admins of the google SoC for vim are reading this
list.

thanks in advance
regards
stoiko ivanov

Hello all,
I just wanted to let you know that I am back on the vim and
vim-dev mailinglists. I won't have time to write many mails, but
my colleagues at work started to ask me a lot of questions about
vim when they found out that I wrote "syn on" and "colorscheme
koehler" in root's vimrc of all servers so I thought it might be
good to get back to the old habit of learning by reading the
solutions of fellow vim users to the questions of other vim
users. :-)
I might as well throw in a few mails, but as I only read my
private mail on the weekends there will be only a few mails from
me...

Ciao,
Thomas

--
  Thomas Köhler       Email:       jean-luc@...
      <><             WWW:              http://gott-gehabt.de
                      IRC:                           tkoehler
                      PGP public key available from Homepage!

The manSubHeading is defined as

syn match  manSubHeading      "^\s\{3\}[a-z][a-z ]*[a-z]$"

This will, however, match more lines than I think is intended.  It
will, for example, match the line

\t  returns are what are recorded and compared with the data git keeps

where "\t" is a horizontal tabulation.  I'm guessing that the actual
regex should be

   ^ \{3\}[a-z][a-z ]*[a-z]$

but I'm not sure; I haven't been able to find a reference for the
display of manual pages.

Anyone have any insight into this issue?

   nikolai

On 4/9/07, Charles E Campbell Jr <drchip@...> wrote:
> Nikolai Weibull wrote:

> > The manSubHeading is defined as
> >
> > syn match  manSubHeading      "^\s\{3\}[a-z][a-z ]*[a-z]$"
> >
> > This will, however, match more lines than I think is intended.

> > Anyone have any insight into this issue?

> I suggest bringing up syntax highlighting issues for a specific filetype
> with the syntax highlighting file's maintainer.
> In this case, by looking at syntax/man.vim, its:  Gautam H. Mudunuri
> <gmudunur AT informatica.com>.

Or, as the file mentions four lines down, Johannes Tanzler
<johannes.tanzler@...>, who was responsible for this particular
rule.  However, I reasoned that someone with better knowledge than
myself of the output format of manual pages could jump in and correct
me or, better yet, confirm my change.  I would then be in a position
to post a patch to the maintainer.  If the maintainer or the person
responsible for this particular rule has subscribed to this list, then
they would also benefit from this discussion.  Sure, I could have
Cc:ed the responsible parties right away, but I figured that if they
don't subscribe to this list they don't want bothersome emails about
syntax-highlighting definitions that don't have a conclusion to an
issue at hand.

Some further digging has revealed that what manSubHeading tries to
match is lines marked as ".SS", that is "Subsection Heading", and that
groff and nroff formats these lines with an indent of three spaces, so
my initial suspicion was correct.  I'll therefore contact the
appropriate parties with a unified diff.

   nikolai

On 4/9/07, Nikolai Weibull <now@...> wrote:
> The manSubHeading is defined as
>
> syn match  manSubHeading      "^\s\{3\}[a-z][a-z ]*[a-z]$"
>
> This will, however, match more lines than I think is intended.  It
> will, for example, match the line
>
> \t  returns are what are recorded and compared with the data git keeps
>
> where "\t" is a horizontal tabulation.  I'm guessing that the actual
> regex should be
>
>   ^ \{3\}[a-z][a-z ]*[a-z]$
I hope nobody minds if I take this opportunity to ask a question about
vim's pattern matching.

After reading |pattern| I wonder if the following is more efficient:

syn match manSubHeading '^ \{3\}\l\l\?\l$'

Taken from |pattern|:

         - Matching with a collection can be slow, because each character in
           the text has to be compared with each character in the collection.
           Use one of the other atoms above when possible.  Example: "\d" is
           much faster than "[0-9]" and matches the same characters

Do people find this to make a different for moderate file sizes, e.g.
the man page for 'less' being ~2000 lines?

--
Ian Tegebo

On 4/9/07, Charles E Campbell Jr <drchip@...> wrote:

> In this case, by looking at syntax/man.vim, its:  Gautam H. Mudunuri
> <gmudunur AT informatica.com>.

Actually, this was actually the wrong maintainer.  Gautam was the
previous maintainer of this file.  Nam SungHyun <namsh@...>
maintains it now.

   nikolai

Nikolai Weibull wrote:

> The manSubHeading is defined as
>
> syn match  manSubHeading      "^\s\{3\}[a-z][a-z ]*[a-z]$"
>
> This will, however, match more lines than I think is intended.  It
> will, for example, match the line
>
> \t  returns are what are recorded and compared with the data git keeps
>
> where "\t" is a horizontal tabulation.  I'm guessing that the actual
> regex should be
>
>  ^ \{3\}[a-z][a-z ]*[a-z]$
>
> but I'm not sure; I haven't been able to find a reference for the
> display of manual pages.
>
> Anyone have any insight into this issue?

I suggest bringing up syntax highlighting issues for a specific filetype
with the syntax highlighting file's maintainer.
In this case, by looking at syntax/man.vim, its:  Gautam H. Mudunuri
<gmudunur AT informatica.com>.

Regards,
Chip Campbell

On 4/9/07, Ian Tegebo <ian.tegebo@...> wrote:
> On 4/9/07, Nikolai Weibull <now@...> wrote:

> >   ^ \{3\}[a-z][a-z ]*[a-z]$
> I hope nobody minds if I take this opportunity to ask a question about
> vim's pattern matching.
>
> After reading |pattern| I wonder if the following is more efficient:
>
> syn match manSubHeading '^ \{3\}\l\l\?\l$'

Yes, and it may be more correct as well, at least in the first and
last instance.  However, the second part may also contain a space, so
\l isn't correct there; and I don't know where you get that \? from.
This is the correct pattern:

   ^ \{3}\l[[:alpha:] ]*\l$

(I also noticed that the apparently accepted "\{m\}" is being used in
this file instead of the documented "\{m}")

One can of course ask oneself if a subsection heading must consist of
at least two letters.  I'm guessing that the intent was to force the
line to end with a non-space:

   ^ \{3}\l\%([[:alpha:] ]*\l\)\=$

In fact, I'd prefer it be written as

   ^ \{3}\a\%([[:alpha:] ]*\a\)\=$

as 'syn case ignore' is on, \l and \a will be the same.  However, \a
meshes better with [:alpha:] and may, depending on how all this is
implemented, be a miniscule amount faster.

> Taken from |pattern|:
>
>         - Matching with a collection can be slow, because each character in
>           the text has to be compared with each character in the collection.
>           Use one of the other atoms above when possible.  Example: "\d" is
>           much faster than "[0-9]" and matches the same characters
>
> Do people find this to make a different for moderate file sizes, e.g.
> the man page for 'less' being ~2000 lines?

Probably not.

   nikolai

Ian Tegebo wrote:

> On 4/9/07, Nikolai Weibull <now@...> wrote:
>
>> The manSubHeading is defined as
>>
>> syn match  manSubHeading      "^\s\{3\}[a-z][a-z ]*[a-z]$"
>>
>> This will, however, match more lines than I think is intended.  It
>> will, for example, match the line
>>
>> \t  returns are what are recorded and compared with the data git keeps
>>
>> where "\t" is a horizontal tabulation.  I'm guessing that the actual
>> regex should be
>>
>>   ^ \{3\}[a-z][a-z ]*[a-z]$
>
> I hope nobody minds if I take this opportunity to ask a question about
> vim's pattern matching.
>
> After reading |pattern| I wonder if the following is more efficient:
>
> syn match manSubHeading '^ \{3\}\l\l\?\l$'

(snip)

The pattern you've provided isn't matching the same thing.
The current one: start the line with exactly three spaces or tabs,
followed by a lower case character, followed by any number of
lower case characters or spaces, up to a lower case character
at the end-of-line.

   example:  <space><tab><space>aaaa aaa aaaaaa

Nikolai W's modifies that to "start the line with exactly three spaces"; the
rest is the same.

   example: <space><space><space>aaa aaaaaa aaa

Yours: start the line with exactly three spaces, followed by two or three
lower case characters, which then terminates the line.

   example: <space><space><space>aa

> Do people find this to make a different for moderate file sizes, e.g.
> the man page for 'less' being ~2000 lines?


Depends on the line lengths.  Your pattern would terminate quite
quickly on each line, as only 5 or 6 characters may be at the beginning
of matching lines; anything more is a mismatch.  The original and NW's
both examine the entire line; so if every line had 1GB of characters, these
two patterns would take considerably longer than yours.

Regards,
Chip Campbell

Nikolai Weibull wrote:

> On 4/9/07, Charles E Campbell Jr <drchip@...> wrote:
>
>> In this case, by looking at syntax/man.vim, its:  Gautam H. Mudunuri
>> <gmudunur AT informatica.com>.
>
>
> Actually, this was actually the wrong maintainer.  Gautam was the
> previous maintainer of this file.  Nam SungHyun <namsh@...>
> maintains it now.

Whoops -- yes, you're quite right.  Sorry 'bout that...

Chip Campbell

Hello Bram,
Is it possible to add this item to the vim voting list ?:

   "collaboration of N vim instances editing same file"
   -- Ability of N instances of vim to absorb, merge and show changes
   to the same file made by other running vim instances [ either by reading
   other vim's swapfiles, or somehow else ] ?

Can this be added to SOC ?

Yakov

The attached patch very simply implements the following from the todo:

7   There is no way to change directory and go back without changing the local
     and/or global directory.  Add a way to find out if the current window uses
     a local directory.  Add cdcmd() that returns ":cd" or ":lcd"?

I personally would prefer the function be called something like 'isdirlocal()'.

I need this feature for my vcscommand.vim plugin, which changes
directory a fair amount, and can screw up the user environment if the
user makes use of :lcd.

Thank you,

bob


---------- Forwarded message ----------
From: Bob Hiestand <bob.hiestand@...>
Date: Apr 11, 2007 4:06 PM
Subject: Re: Determining whether a window used :lcd
To: Yakov Lerner <iler.ml@...>
Cc: "vim@..." <vim@...>


On 4/11/07, Yakov Lerner <iler.ml@...> wrote:
> I needed this once in of my script. I ended with some rude
> simplification/workaround, lackng the direct simple solution.
> I don't know your specific case, but you might find simlpistic workaround.
>
> One weird attempt to determine this would be to (I did not do it):
>   (1) get getcwd() in the window in quiestion
>   (2) create temp new window with :new
>   (3)  get getcwd() in the new temp window
>   (4) compare cwd from step (3) against cwd from step(1)
>   (5) :bw the temp window
> This has lots of drawcacks:
> - I am not sure this sequence works in the presence of :acd thought.
> - I am not sure this sequence works at all, but I can't think of other
> method either.
> - This sequence won't detect one subtle case: case the :lcd is set, but is set
> to directory X where X is same as current directory. (This case behaves
> differently that case without  :lcd, but this difference might not
> matter to you).

I don't think it works.  When you use :new, you inherit the :lcd, if
it was used.

> Maybe vim needs new functions getlcwd(), hetgcwd(), or additional 2nd
> param to getcwd() to return global/local dir.

After looking in the :help todo, it appears that others have requested
it.  I've thrown together a quick patch to implement the described
'cdcmd()' (I prefer a more direct 'isdirlocal()'), but that's fine.
I'll try submitting it.

Thank you,

bob

Hello Yakov,

Couldn't you hook into the FileChangedShell autocmd event and merge the changes
into your buffer from there? You can also handle the swap file message with
SwapExists event.

regards,
Peter



--- Yakov Lerner <iler.ml@...> wrote:

> Hello Bram,
> Is it possible to add this item to the vim voting list ?:
>
>   "collaboration of N vim instances editing same file"
>   -- Ability of N instances of vim to absorb, merge and show changes
>   to the same file made by other running vim instances [ either by reading
>   other vim's swapfiles, or somehow else ] ?
>
> Can this be added to SOC ?
>
> Yakov
>


Send instant messages to your online friends http://au.messenger.yahoo.com

Hi!
It's my first mail to this list.

I'm using vim on Win32 this Russian keyboard. There are some bugs with mapping
of russians special keys. I've made some patches to fix these bugs.

Let start step by step.
1. Special key may contain multi-byte character (ex. unicode) after  modifier.
For example, if I press a key Alt-k with russian input (Alt-Ì) then vim's got
key K_SPECIAL K_SPECIAL 0x08 0xd0 0xbb, where 0xd0 0xbb is the unicode character
CYRILLIC_SMALL_LETTER_EL.
2. In functions find_special_key (misc2.c) and str2special (message.c) vim
supposes that there is only _1_ byte after modifiers.

I can offer the corrected code for these functions.

(There are 2 other patches to fix this problem in the console Win32 application)

Hallo Freunde von vim oder die, die es werden wollen,

der deutsche vimtutor wurde stark erweitert und somit an das englische
Original angepaßt.
Die Version ist 1.7.

Für jeden entdeckten Fehler gibt es einen Punkt.

Man kann sich den tutor einfach ansehen unter:

http://freenet-homepage.de/schuttvim/tutor.de

oder praktisch in Echtbedingung durcharbeiten
(zum erlernen von vim empfehlenswert!):

-) Kopiere die Datei "tutor.de" in das Vim-Runtime-Tutor-Verzeichnis
    (also z.B vim62\tutor\ oder vim70\tutor\, ältere "tutor.de"
    überschreiben)

-) Starte die ausführbare Datei "vimtutor" im Runtime-Verzeichis
    (z.B. für Windows: vim70\vimtutor.bat)

-) Durcharbeiten und viel Lernen, fertig.


Gruß

Joachim
###########################################

This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.f-secure.com/

Hi,

This might already be possible, please excuse me if it is.

I love the editting features of vim, but find that navigating between
open files is quite difficult.

Ideally I think I would be quite confortable with a kate like
interface for listing open files:
http://www.kde.org/screenshots/images/3.1/fullsize/2.png (screenshot)

I got quite close by messing about with netrw in a vertical split, but
the list pane did not:

- Remain the same size
- Show only one file to be open in the right hand pane. It would
always split again for each newly selected file.

Does anyone know how to do this?

Would anyone find this useful?

I have looked into using vim-part inside kate, but this is not
supported for my UNIX distribution.

--
Best Regards

Edd

Edd Barrett wrote:
  > Hi,
  >
  > This might already be possible, please excuse me if it is.
  >
  > I love the editting features of vim, but find that navigating between
  > open files is quite difficult.
  >
  > Ideally I think I would be quite confortable with a kate like
  > interface for listing open files:
  > http://www.kde.org/screenshots/images/3.1/fullsize/2.png (screenshot)
  >
  > I got quite close by messing about with netrw in a vertical split, but
  > the list pane did not:
  >
  > - Remain the same size
  > - Show only one file to be open in the right hand pane. It would
  > always split again for each newly selected file.
  >
  > Does anyone know how to do this?
  >
  > Would anyone find this useful?
  >
  > I have looked into using vim-part inside kate, but this is not
  > supported for my UNIX distribution.
  >

I haven't used Kate, but I'm using a combination of
- project (http://vim.sourceforge.net/scripts/script.php?script_id=69) to
(re-)open files belonging to a custom file structure,
- ProjectBrowse (http://vim.sourceforge.net/scripts/script.php?script_id=943) to
open files in subdirectories and - most useful -
- bufexplorer (http://vim.sourceforge.net/scripts/script.php?script_id=42) to
navigate between files currently open in buffers.

I've set up those plugins to open in a vertical split at the left side (like in
most IDEs). Each view can be toggled on/off via a function key (F2, F3, F4). If
one view is already open, trying to open another one will close the former, so
that they don't eat up all of my window space.

To achieve that, I've written mappings and VIM scripts like this (Attention!
Incomplete code, just for illustration!):

function s:IsProjectWindowEnabled()
      if exists("g:proj_running")
	 if( bufwinnr( bufname( g:proj_running ) ) != -1 )
	     return 1
	 endif
      endif
      return 0
endfunction

function s:ToggleProjectWindow()
      " Project, TagList, JavaBrowser and BufExplorer vie for the same screen
real estate; so
      " close other windows first.
      if( s:IsTagListEnabled() )
	 call s:ToggleTagListWindow()
      endif
      if( s:IsJavaBrowserEnabled() )
	 call s:ToggleJavaBrowserWindow()
      endif
      if( s:IsBufExplorerEnabled() )
	 call s:ToggleBufExplorerWindow()
      endif

      " :Project has no toggle semantic itself, so we have to close the window
      " on our own.
      if( ! s:IsProjectWindowEnabled() )
	 silent execute "Project"
      else
	 silent execute "Project"
	 silent execute "close"
      endif
endfunction

nmap <silent> <F2> :call <SID>ToggleProjectWindow()<CR>
imap <silent> <F2> <C-O>:call <SID>ToggleProjectWindow()<CR>

-- regards, ingo

/^-- Ingo Karkat -- /^-- /^-- /^-- /^-- /^-- /^-- http://ingo-karkat.de/ --

On 4/12/07, Ingo Karkat <swdev@...> wrote:
> Edd Barrett wrote:
>  > Hi,
>  >
>  > This might already be possible, please excuse me if it is.
>  >
>  > I love the editting features of vim, but find that navigating between
>  > open files is quite difficult.
>  >
>  > Ideally I think I would be quite confortable with a kate like
>  > interface for listing open files:
>  > http://www.kde.org/screenshots/images/3.1/fullsize/2.png (screenshot)
>  >
>  > I got quite close by messing about with netrw in a vertical split, but
>  > the list pane did not:
>  >
>  > - Remain the same size
>  > - Show only one file to be open in the right hand pane. It would
>  > always split again for each newly selected file.
>  >
>  > Does anyone know how to do this?
>  >
>  > Would anyone find this useful?
>  >
>  > I have looked into using vim-part inside kate, but this is not
>  > supported for my UNIX distribution.
>  >
>
> I haven't used Kate, but I'm using a combination of
> - project (http://vim.sourceforge.net/scripts/script.php?script_id=69) to
> (re-)open files belonging to a custom file structure,
> - ProjectBrowse (http://vim.sourceforge.net/scripts/script.php?script_id=943)
to
> open files in subdirectories and - most useful -
> - bufexplorer (http://vim.sourceforge.net/scripts/script.php?script_id=42) to
> navigate between files currently open in buffers.
>
> I've set up those plugins to open in a vertical split at the left side (like
in
> most IDEs). Each view can be toggled on/off via a function key (F2, F3, F4).
If
> one view is already open, trying to open another one will close the former, so
> that they don't eat up all of my window space.
I was hoping the SideBar.vim plugin would do this for me:

http://www.vim.org/scripts/script.php?script_id=720

Unfortunately it's broken for me in vim70 (shame on me for not
contacting the maintainer or fixing it myself).  At the moment it
doesn't properly control the width of the sidebar.

I was hoping to use only one function key that would cycle through my
sidebars; maybe CTRL-FX would drop a sidebar or prompt to add another.
  Thanks for you code!

--
Ian Tegebo

On 4/12/07, Edd Barrett <vext01@...> wrote:
> Hi,
>
> This might already be possible, please excuse me if it is.
>
> I love the editting features of vim, but find that navigating between
> open files is quite difficult.
>
> Ideally I think I would be quite confortable with a kate like
> interface for listing open files:
> http://www.kde.org/screenshots/images/3.1/fullsize/2.png (screenshot)
You might want to look at winmanager:

http://robotics.eecs.berkeley.edu/~srinath/vim/snapshot2.JPG
http://www.vim.org/scripts/script.php?script_id=95

It seems a very popular plugin for accomplishing this.  If you search
for 'tree' or 'file explorer' in the scripts section you'll see many
more options.

--
Ian Tegebo

Hi,

is it not a little bit unfair to write German at an English-mailing list? ;-)

Found two small things:
- Kapitel 7.3
- Outro
-> "and" not translated. 8-)
( /\<and\> should give 2 hits)

Nice to see a German translation for the vim-tutor.
I like it.

Greetings,
Manu



j.hofmann@... wrote:
> Hallo Freunde von vim oder die, die es werden wollen,
>
> der deutsche vimtutor wurde stark erweitert und somit an das englische
> Original angepaßt.
> Die Version ist 1.7.
>
> Für jeden entdeckten Fehler gibt es einen Punkt.
>
> Man kann sich den tutor einfach ansehen unter:
>
> http://freenet-homepage.de/schuttvim/tutor.de
>
> oder praktisch in Echtbedingung durcharbeiten
> (zum erlernen von vim empfehlenswert!):
>
> -) Kopiere die Datei "tutor.de" in das Vim-Runtime-Tutor-Verzeichnis
>    (also z.B vim62\tutor\ oder vim70\tutor\, ältere "tutor.de"
>    überschreiben)
>
> -) Starte die ausführbare Datei "vimtutor" im Runtime-Verzeichis
>    (z.B. für Windows: vim70\vimtutor.bat)
>
> -) Durcharbeiten und viel Lernen, fertig.
>
>
> Gruß
>
> Joachim
> ###########################################
>
> This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
> For more information, connect to http://www.f-secure.com/
>

I'm not sure if this is the right way to submit a patch.

Anyway the attached patch should solve the problem with symbolic links.
For ex. when editing /etc/hosts we get the warning
    E303: Unable to open swap file for "hosts", recovery impossible
(/etc/hosts is a symlink in cygwin)

Regards.

Luca.

Hi,

I like VIM. I want to use VIM as my everyday editor. I even spent a
frustrating week trying to determine if VIM could replace Textmate as
my main editor. VIM is very good for working with a single file but
the concept of a project is not really there. I looked at plugins,
talked with people in #vim about plugins and how to extend VIM. I
figured it would probably take a year of spare time for me to learn
how and then write the plugin to do what Textmate can do with respect
to projects right when it is installed: a project drawer, project
tabs, multiple open projects, project-wide search and selective
replace. And now I see that VIM doesn't need more features...

http://www.vim.org/soc/ideas.php

Darn.

Peter