Re: Python plugin using PyWin32

On Thursday, June 30, 2011 09:35:51 Alexandre Martani wrote:

> Hello all,

> I am trying to use Vim R plugin [1], which is a Python plugin
> that uses PyWin32 on Windows. I have installed Python 2.7.1
> and PyWin32. It is installed correctly, as I am able to do a
> "import win32api" from python

> shell without errors. But, on GVim, if I do:
> :python import win32api

> I receive the following error:

> Traceback (most recent call last):
>     File "<string>", line 1, in <module>
> ImportError: DLL load failed: The specified module could not
> be found.

> Notice that this is not the standard error for module not
> found ("No module named x"). It is probably related to the
> path python uses for its DLL modules. I have played with
> sys.path, but without success.

> I also noticed the first path in sys.path is
> "C:\\must>not&exist", which is probably a bug. Don't know if
> this could be related, but I tried do a sys.path.pop(0), and
> it didn't work.

> Anyone has an idea of the problem?

Fold the output of grep

Your output sounds great, and the grep display format is one I prefer, but it 
is not supported directly by gnu grep.

Is there a way to fold the context lines that appear in your popup window?
If so, how?

--

-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Keeping the Cursor in the Taglist Window

Re: Keeping the Cursor in the Taglist Window

On Thu, Jun 30, 2011 at 9:54 PM, Roy Fulbright <rfulbrig <at> hotmail.com> wrote:
> I have the taglist plugin and it works great. I have
> 'Tlist_GainFocus_On_ToggleOpen' set so that the cursor is in the taglist
> window when it opens. This works fine, but when I scroll the cursor down to
> an entry and press ENTER the cursor is moved to the main Vim window. I would
> like the cursor to remain in the taglist window as I select different
> taglist entries so I won't have to keep moving it back each time to make
> another selection. Is there a setting that keeps the cursor in the taglist
> window while making selections from the taglist? Thanks.
>
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>

Instead of <Enter> press 'p'. Also :help taglist.txt

-- 
Kent

--

-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Re: How to retrigger 'autocmd' ?

On 29 June 2011 11:08, Ben Fritz <fritzophrenic <at> gmail.com> wrote:
>
>
> On Jun 28, 4:31 am, narke <narkewo... <at> gmail.com> wrote:
>> Hi,
>>
>> When I 'vimgrep' on a large file tree, I usually turn of 'autocmd' by
>> ':noau vimgrep /xxx/ **/*.c'.   Then I got c file open in a buffer but
>> without the syntax highlighting (maybe also other good things). So I
>> think what I need to do is to retriggle those 'autocmd' that would
>> been usually executed if I don't do 'noau ...'.  Can anyone tell me
>> how to, if possible?
>>
>> Thanks in advance.
>>
>
> I normally add the 'j' flag to my vimgrep to avoid an automatic jump
> to the first match. Then I can use the quickfix window with :copen, or
> just use :cnext/:cprev/:ccurrent to navigate. When these commands load
> a new file, it triggers all the proper autocmds.
>
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>

Thanks for all your inputs.  At the end, I so much like Ben's
solution: using the 'j' flag of vimgrep.

Cheers!
narke

-- 
Life is the only flaw in an otherwise perfect nonexistence
    -- Schopenhauer

narke
public key at http://subkeys.pgp.net:11371 (narkewoody <at> gmail.com)

--

-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Re: Fold the output of grep

On Jul 1, 3:54 am, howard Schwartz <howard... <at> gmail.com> wrote:
> Is there a way to fold the context lines that appear in your popup window?
> If so, how?

Not at the moment. The idea is interesting, though, so I will add it
to my todo list and implement it some day.

Marko

--

-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Re: vimSubst

I'll read the material, thank you, that is surely what I needed.

cts

--- On Thu, 6/30/11, Charles Campbell <Charles.E.Campbell <at> nasa.gov> wrote:

> From: Charles Campbell <Charles.E.Campbell <at> nasa.gov>
> Subject: Re: vimSubst
> To: vim_use <at> googlegroups.com
> Date: Thursday, June 30, 2011, 7:03 AM
> Charles Smith wrote:
> > The "after" directory is new to me, thank you for
> introducing it to me.  Unfortunately, I can find very
> little information about how it works exactly (vim version
> 7.2.264).
> > 
> > I don't understand this mechanism...
> > 
> >    Normally, when a file matching a
> particular name pattern is loaded
> >    into a buffer, a syntax file matching
> that pattern is loaded and
> >    invoked.  Now, the rules that are
> causing me trouble are defined in a
> >    file called vim.vim and I don't find any
> matching patterns using
> >    that syntax file in my own filetypes.vim
> or the system-wide one.
> > 
> >    In general, it seems a pity that new
> features should break such
> >    simple, unambiguous, and useful
> functionality as, e.g. "syn clear":
> > 
> >      "This command should be used when
> you want to switch off syntax
> >      highlighting, or when you want to
> switch to using another syntax.
> >      It's normally not needed in a
> syntax file itself, because syntax is
> >      cleared by the autocommands that
> load the syntax file.  The command
> >      also deletes the
> "b:current_syntax" variable, since no syntax is
> >      loaded after this command."
> > 
> > Hopefully, I'm still missing something ...
> >    
> "syn clear" is not broken.  If one loads syntax
> definitions after a "syn clear", then that new syntax
> applies; in fact, many of the syntax files distributed with
> vim have "syn clear" embedded in them.
> 
> So your difficulty I suspect is in understanding the
> loading sequence.  Here's some reading on the subject:
> 
> :help .vimrc
> :help load-plugins
> :help 'runtimepath'
> 
> Your first email mentioned that "syn clear" didn't work in
> your syntax file.  What is it named, in what directory
> is it in (so we may infer when it gets loaded), how are you
> triggering your syntax to be loaded (.vim/filetype.vim?) and
> how does syntax/vim.vim get involved?
> 
> Remember that things that are loaded later can modify
> what's happened thus far.  So, if your syntax file is
> loaded with its "syn clear" and then syntax/vim.vim is
> loaded, naturally vim.vim's definitions have not been
> cleared; in this case they weren't even loaded and defined
> when that "syn clear" was issued.
> 
> Regards,
> Chip Campbell
> 
> -- You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are
> replying to.
> For more information, visit http://www.vim.org/maillist.php
> 

--

-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

RE: Python plugin using PyWin32

Alexandre Martani wrote:
> :python import win32api
>
> I receive the following error:
>
> Traceback (most recent call last):
>      File "<string>", line 1, in <module>
> ImportError: DLL load failed: The specified module could not be found.

I think sc is correct. In Vim, use :version and carefully
inspect what it says about the Python support which was
configured when your Vim was compiled.

John

--

-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

www.vim.org - future

I've been thinking about how to optimize that user find plugins
- and how to make it easier for devs to expose their plugins to the
  public (of course this should be better than google).

And the result is: Do it like google: Ask authors to register their
upstream (git,svn,hg,..) urls and be done. The page should fetch updates
and generate the content based on the repos. Eg those who are hosted on
github already have a README.* file which could be used to render
content. the doc/*.txt files could be used to render the description
(and details). Its horrific that you have to download a plugin in order
to start reading its documentation, isn't it?

Of course each author should be able to assign tags to his/her plugin
and create cross references to other plugins such as

my plugin "xptemplate" -is-related-to snipmate
my plugin "xptemplate" -is-related-to ultisnips

my plugin "xptemplate" supersedes XY because FOO

In the end that's almost all users care about.

We could move all existing plugins on www.vim.org (which don't have any
maintainers) to a github account - the way vim-scripts has done it.

Does this make sense to you?
Do you see any major problems which such an "open" design?

I'm not going to replace www.vim.org in the near future.
However may be willing to setup an alternative site which could be good
enough to replace www.vim.org one day if Bram agrees, funding and
support of the page suffices and the charity aspect of Vim is honored etc.

And to make this a success I'd like to allow everyone to participate.

Marc Weber

--

-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

RE: Keeping the Cursor in the Taglist Window