Paul wrote:
> I took a jab at a problem that experienced with netrw 140 for gvim on
> Windows 7. Within the past year some time, I dabbled in some of the
> more advanced features netrw, namely copy marked files to a marked
> target directory. (yes, I've been posting from different gmails
> depending on whether I'm at work machine). While I can mark the files
> and the target directory, "mc" doesn't seem to cause the files to be
> copied. I found this to be the case on two different computers (both
> Windows 7), one on which I had admin privileges and on which I did the
> troubleshooting. On that computer, netrw 140 works fine for gvim on
> Cygwin's Xwin.
>
[snip]
I'm not seeing that problem, but the latest netrw insures that
s:didstarstar exists. Please download a copy from my website:
http://www.drchip.org/astronaut/vim/index.html#NETRW
>
> >From a previous posting on this forum I was advised to try netrw 147,
> which I un-vimballed into "c:/Program Files (x86)/Vim/vimfiles". No
> need to set g:vimball_home because the above directory was the first
> valid directory in runtimepath.
[snip]
Hmm, that looks problematic, because it looks like where vim's system
files appear. I'll have to take a look at vimball and make sure that
its not unpacking into system directories automatically.
What does :echo &rtp show?
> I've been troubleshooting this problem a number of hours, and
> somewhere in my rummaging about, I recall getting an warning message
> that netrw 147 required vim 7.3.XXX, where XXX was a decimal number in
> the 100-199 range.
[snip]
I confirm: as the message said, the latest netrw requires 7.3.465, which
is referring to vim's patch level.
Regards,
C 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 because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Tuesday, April 2, 2013
Re: Setting the TEXINPUTS and BIBINPUTS varibles for latex inside vim/gVim
>
> Setting environment variables from within an app affects that app and
>
> its child apps. So, are you compiling from within vim? ie. do you
>
> leave vim and then try latex, bibtex, etc?
>
I do not really know how this is implemented in the latex package, but I guess I do leave vim for compilation. When I am using vim as a child process of the bash, then it works because it seems to use the parent for compilation. There the environment variables are set correctly in my bashrc.
When I work with gVim (which I generally prefer), then I do not really know where it goes when I compile. It seems to leave vim and invoke some shell where it can use the pdflatex command. However, it apparently does not set the environment variables specified in my bashrc there. For me it would be of great interest to know how to set variables in this environment invoked by gVim.
Thanks,
Christoph
--
--
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 because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> Setting environment variables from within an app affects that app and
>
> its child apps. So, are you compiling from within vim? ie. do you
>
> leave vim and then try latex, bibtex, etc?
>
I do not really know how this is implemented in the latex package, but I guess I do leave vim for compilation. When I am using vim as a child process of the bash, then it works because it seems to use the parent for compilation. There the environment variables are set correctly in my bashrc.
When I work with gVim (which I generally prefer), then I do not really know where it goes when I compile. It seems to leave vim and invoke some shell where it can use the pdflatex command. However, it apparently does not set the environment variables specified in my bashrc there. For me it would be of great interest to know how to set variables in this environment invoked by gVim.
Thanks,
Christoph
--
--
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 because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Setting the TEXINPUTS and BIBINPUTS varibles for latex inside vim/gVim
>
>
> The setting of the $TEXINPUTS variable and the g:Tex_TEXINPUTS
>
> variable is covered in
>
>
>
> :help custom-packages
>
> :help Tex_TEXINPUTS
>
>
>
> Something that doesn't seem to be covered very well by the LaTeX
>
> Suite documentation is where to set the g:Tex_TEXINPUTS variable.
>
> It is set by the package in the ftplugin/latex-suite/texrc file.
>
> The top of that file says:
>
>
>
> NOTE: Do NOT be edit this file directly:
>
> this file will be over-written each time you install a new
>
> copy of latex-suite.
>
>
>
> You can do one of the following:
>
> 1. Copy this file into $VIMFILES/ftplugin/tex/texrc
>
> and edit the values in that file.
>
> $VIMFILES is ~/.vim for UNIX systems and ~/vimfiles for
>
> WINDOWS systems.
>
I have made the directory tex in my ftplugin folder, then I copied the original texrc there and added the following line:
TexLet g:Tex_TEXINPUTS = "pathtolatex/latex/"
but that does not work and gVim still does not search the specified folder.
>
>
> 2. Just set values of each setting individually in your
>
> $VIMFILES/ftplugin/tex.vim file. (See above for what
>
> $VIMFILES is). You will need to use :let instead of
>
> :TexLet in this case.
Neither does that (I did change TexLet to let).
Thank you anyway for your help,
Christoph
--
--
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 because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
>
> The setting of the $TEXINPUTS variable and the g:Tex_TEXINPUTS
>
> variable is covered in
>
>
>
> :help custom-packages
>
> :help Tex_TEXINPUTS
>
>
>
> Something that doesn't seem to be covered very well by the LaTeX
>
> Suite documentation is where to set the g:Tex_TEXINPUTS variable.
>
> It is set by the package in the ftplugin/latex-suite/texrc file.
>
> The top of that file says:
>
>
>
> NOTE: Do NOT be edit this file directly:
>
> this file will be over-written each time you install a new
>
> copy of latex-suite.
>
>
>
> You can do one of the following:
>
> 1. Copy this file into $VIMFILES/ftplugin/tex/texrc
>
> and edit the values in that file.
>
> $VIMFILES is ~/.vim for UNIX systems and ~/vimfiles for
>
> WINDOWS systems.
>
I have made the directory tex in my ftplugin folder, then I copied the original texrc there and added the following line:
TexLet g:Tex_TEXINPUTS = "pathtolatex/latex/"
but that does not work and gVim still does not search the specified folder.
>
>
> 2. Just set values of each setting individually in your
>
> $VIMFILES/ftplugin/tex.vim file. (See above for what
>
> $VIMFILES is). You will need to use :let instead of
>
> :TexLet in this case.
Neither does that (I did change TexLet to let).
Thank you anyway for your help,
Christoph
--
--
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 because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Monday, April 1, 2013
netrw copy fails, trouble installing v.147
I took a jab at a problem that experienced with netrw 140 for gvim on
Windows 7. Within the past year some time, I dabbled in some of the
more advanced features netrw, namely copy marked files to a marked
target directory. (yes, I've been posting from different gmails
depending on whether I'm at work machine). While I can mark the files
and the target directory, "mc" doesn't seem to cause the files to be
copied. I found this to be the case on two different computers (both
Windows 7), one on which I had admin privileges and on which I did the
troubleshooting. On that computer, netrw 140 works fine for gvim on
Cygwin's Xwin.
I know it's nothing to do with my vimrc (where I do some abominations
to be able to shell out to bash) because I used the vim73/
vimrc_example.vim that came with the installation. I also found this
topic at http://groups.google.com/forum/#!topic/vim_use/BVcfJHdD6x8,
so I checked that g:netrw_localcopycmd was already set to 'copy'. I
additionally let g:netrw_local_copycmd='copy', but that didn't work.
I did the following to capture any messages in register "a" and Put it
into a New file:
:redir @a
mc
:redir END
:new
"aP
The message is verbose, but identical for both Windows & Xwin
versions, with the exception of the double-dotted "y" character in the
"Pattern not found" messages. I manually folded the longer lines to
try and minimize confusion:
22 fewer lines
<cygwin\home\LoalAdmin\tmp" --No lines in buffer--
Error detected while processing function <SNR>24_NetrwMarkFileCopy
..<SNR>24_LocalBrowseShellCmdRefresh..<SNR>24_NetrwRefresh
..netrw#LocalBrowseCheck..<SNR>24_NetrwBrowse
..<SNR>24_BrowserMaps:
line 102:
E121: Undefined variable: s:didstarstar
Error detected while processing function <SNR>24_NetrwMarkFileCopy
..<SNR>24_LocalBrowseShellCmdRefresh..<SNR>24_NetrwRefresh
..netrw#LocalBrowseCheck..<SNR>24_NetrwBrowse
..<SNR>24_BrowserMaps:
line 102:
E15: Invalid expression: s:didstarstar || !mapcheck("<s-down>","n")
Error detected while processing function <SNR>24_NetrwMarkFileCopy
..<SNR>24_LocalBrowseShellCmdRefresh..<SNR>24_NetrwRefresh
..netrw#LocalBrowseCheck..<SNR>24_NetrwBrowse
..<SNR>24_BrowserMaps:
line 106:
E121: Undefined variable: s:didstarstar
Error detected while processing function <SNR>24_NetrwMarkFileCopy
..<SNR>24_LocalBrowseShellCmdRefresh..<SNR>24_NetrwRefresh
..netrw#LocalBrowseCheck..<SNR>24_NetrwBrowse
..<SNR>24_BrowserMaps:
line 106:
E15: Invalid expression: s:didstarstar || !mapcheck("<s-up>","n")
Error detected while processing function <SNR>24_NetrwMarkFileCopy
..<SNR>24_LocalBrowseShellCmdRefresh..<SNR>24_NetrwRefresh
..netrw#LocalBrowseCheck..<SNR>24_NetrwBrowse
..<SNR>24_PerformListing..<SNR>24_NetrwBookHistHandler
..<SNR>24_NetrwBookmarkMenu:
line 10:
E329: No menu "Bookmarks"
Error detected while processing function <SNR>24_NetrwMarkFileCopy
..<SNR>24_LocalBrowseShellCmdRefresh..<SNR>24_NetrwRefresh
..netrw#LocalBrowseCheck..<SNR>24_NetrwBrowse
..<SNR>24_PerformListing..<SNR>24_NetrwBookHistHandler
..<SNR>24_NetrwBookmarkMenu:
line 11:
E329: No menu "Bookmark Delete"
E486: Pattern not found: ^$
E486: Pattern not found: ^\d\{3}ÿ\d\{3}\/
E486: Pattern not found: \.h$
E486: Pattern not found: ^\d\{3}ÿ\d\{3}\/
E486: Pattern not found: \.c$
E486: Pattern not found: ^\d\{3}ÿ\d\{3}\/
E486: Pattern not found: \.cpp$
E486: Pattern not found: ^\d\{3}ÿ\d\{3}\/
E486: Pattern not found: \.o$
E486: Pattern not found: ^\d\{3}ÿ\d\{3}\/
E486: Pattern not found: \.obj$
E486: Pattern not found: ^\d\{3}ÿ\d\{3}\/
E486: Pattern not found: \.info$
E486: Pattern not found: ^\d\{3}ÿ\d\{3}\/
E486: Pattern not found: ^\d\{3}ÿ\d\{3}\/
E486: Pattern not found: \.bak$
E486: Pattern not found: ^\d\{3}ÿ\d\{3}\/
E486: Pattern not found: ^\d\{3}ÿ\d\{3}\/
Because of the identicalness, I assumed that these messages didn't
contain the clue to the problem.
From a previous posting on this forum I was advised to try netrw 147,
which I un-vimballed into "c:/Program Files (x86)/Vim/vimfiles". No
need to set g:vimball_home because the above directory was the first
valid directory in runtimepath. I confirmed that files unloaded into
their subdirectories and that it superceded the corresponding files in
"c:/Program Files (x86)/Vim/vim73". In fact, I later also un-
vimballed them into "c:/Program Files (x86)/Vim/vim73". In both
cases, it seemed that netrw failed to run. Doing ":e ." yields the
message
"." is a directory
and the buffer appears exactly as an empty file would. Redirecting
messages to @a captures these messages:
"." is a directory
Error detected while processing function <SNR>14_LocalBrowse:
line 14:
E117: Unknown function: netrw#LocalBrowseCheck
I confirmed that all files and subdirectories were readable and
executable/accessible by all users and that there was no funny
business with Windows 7 virtualization i.e. the following directory
was completely empty of visible & hidden files:
c:/Users/LoalAdmin/AppData/Local/VirtualStore
I've been troubleshooting this problem a number of hours, and
somewhere in my rummaging about, I recall getting an warning message
that netrw 147 required vim 7.3.XXX, where XXX was a decimal number in
the 100-199 range. I don't recall how I got it, but I remember
wondering whether XXX corresponded to the patch number. If so, that
might explain it because the gvim for Xwin was around patch 172 (which
was higher than XXX) whereas Windows gvim only "Included patches:
1-46". Is this correct? My Windows version is:
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Oct 27 2010 17:59:02)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-46
Compiled by Bram@KIBAALE
Big version with GUI. Features included (+) or not (-):
+arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset
+cindent
+clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info
+comments
+conceal +cryptv +cscope +cursorbind +cursorshape +dialog_con_gui
+diff
+digraphs -dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search
+farsi
+file_in_path +find_in_path +float +folding -footer +gettext/dyn -
hangul_input
+iconv/dyn +insert_expand +jumplist +keymap +langmap +libcall
+linebreak
+lispindent +listcmds +localmap -lua +menu +mksession +modify_fname
+mouse
+mouseshape +multi_byte_ime/dyn +multi_lang -mzscheme +netbeans_intg
+ole
-osfiletype +path_extra +perl/dyn +persistent_undo -postscript
+printer
-profile +python/dyn +python3/dyn +quickfix +reltime +rightleft +ruby/
dyn
+scrollbind +signs +smartindent -sniff +startuptime +statusline -
sun_workshop
+syntax +tag_binary +tag_old_static -tag_any_white +tcl/dyn -tgetent
-termresponse +textobjects +title +toolbar +user_commands +vertsplit
+virtualedit +visual +visualextra +viminfo +vreplace +wildignore
+wildmenu
+windows +writebackup -xfontset -xim -xterm_save +xpm_w32
system vimrc file: "$VIM\vimrc"
user vimrc file: "$HOME\_vimrc"
2nd user vimrc file: "$VIM\_vimrc"
user exrc file: "$HOME\_exrc"
2nd user exrc file: "$VIM\_exrc"
system gvimrc file: "$VIM\gvimrc"
user gvimrc file: "$HOME\_gvimrc"
2nd user gvimrc file: "$VIM\_gvimrc"
system menu file: "$VIMRUNTIME\menu.vim"
Compilation: cl -c /W3 /nologo -I. -Iproto -DHAVE_PATHDEF -DWIN32 -
DFEAT_CSCOPE -DFEAT_NETBEANS_INTG -DFEAT_XPM_W32 -DWINVER=0x0400 -
D_WIN32_WINNT=0x0400 /Fo.\ObjGOLYHTR/ /Ox /GL -DNDEBUG /Zl /MT -
DFEAT_OLE -DFEAT_MBYTE_IME -DDYNAMIC_IME -DFEAT_GUI_W32 -
DDYNAMIC_ICONV -DDYNAMIC_GETTEXT -DFEAT_TCL -DDYNAMIC_TCL -
DDYNAMIC_TCL_DLL=\"tcl83.dll\" -DDYNAMIC_TCL_VER=\"8.3\" -DFEAT_PYTHON
-DDYNAMIC_PYTHON -DDYNAMIC_PYTHON_DLL=\"python27.dll\" -DFEAT_PYTHON3 -
DDYNAMIC_PYTHON3 -DDYNAMIC_PYTHON3_DLL=\"python31.dll\" -DFEAT_PERL -
DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\"perl512.dll\" -DFEAT_RUBY -
DDYNAMIC_RUBY -DDYNAMIC_RUBY_VER=191 -DDYNAMIC_RUBY_DLL=\"msvcrt-
ruby191.dll\" -DFEAT_BIG /Fd.\ObjGOLYHTR/ /Zi
Linking: link /RELEASE /nologo /subsystem:windows /LTCG:STATUS
oldnames.lib kernel32.lib advapi32.lib shell32.lib gdi32.lib
comdlg32.lib ole32.lib uuid.lib /machine:i386 /nodefaultlib gdi32.lib
version.lib winspool.lib comctl32.lib advapi32.lib shell32.lib /
machine:i386 /nodefaultlib libcmt.lib oleaut32.lib user32.lib /
nodefaultlib:python27.lib /nodefaultlib:python31.lib e:\tcl\lib
\tclstub83.lib WSock32.lib e:\xpm\lib\libXpm.lib /PDB:gvim.pdb -debug
--
--
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 because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Windows 7. Within the past year some time, I dabbled in some of the
more advanced features netrw, namely copy marked files to a marked
target directory. (yes, I've been posting from different gmails
depending on whether I'm at work machine). While I can mark the files
and the target directory, "mc" doesn't seem to cause the files to be
copied. I found this to be the case on two different computers (both
Windows 7), one on which I had admin privileges and on which I did the
troubleshooting. On that computer, netrw 140 works fine for gvim on
Cygwin's Xwin.
I know it's nothing to do with my vimrc (where I do some abominations
to be able to shell out to bash) because I used the vim73/
vimrc_example.vim that came with the installation. I also found this
topic at http://groups.google.com/forum/#!topic/vim_use/BVcfJHdD6x8,
so I checked that g:netrw_localcopycmd was already set to 'copy'. I
additionally let g:netrw_local_copycmd='copy', but that didn't work.
I did the following to capture any messages in register "a" and Put it
into a New file:
:redir @a
mc
:redir END
:new
"aP
The message is verbose, but identical for both Windows & Xwin
versions, with the exception of the double-dotted "y" character in the
"Pattern not found" messages. I manually folded the longer lines to
try and minimize confusion:
22 fewer lines
<cygwin\home\LoalAdmin\tmp" --No lines in buffer--
Error detected while processing function <SNR>24_NetrwMarkFileCopy
..<SNR>24_LocalBrowseShellCmdRefresh..<SNR>24_NetrwRefresh
..netrw#LocalBrowseCheck..<SNR>24_NetrwBrowse
..<SNR>24_BrowserMaps:
line 102:
E121: Undefined variable: s:didstarstar
Error detected while processing function <SNR>24_NetrwMarkFileCopy
..<SNR>24_LocalBrowseShellCmdRefresh..<SNR>24_NetrwRefresh
..netrw#LocalBrowseCheck..<SNR>24_NetrwBrowse
..<SNR>24_BrowserMaps:
line 102:
E15: Invalid expression: s:didstarstar || !mapcheck("<s-down>","n")
Error detected while processing function <SNR>24_NetrwMarkFileCopy
..<SNR>24_LocalBrowseShellCmdRefresh..<SNR>24_NetrwRefresh
..netrw#LocalBrowseCheck..<SNR>24_NetrwBrowse
..<SNR>24_BrowserMaps:
line 106:
E121: Undefined variable: s:didstarstar
Error detected while processing function <SNR>24_NetrwMarkFileCopy
..<SNR>24_LocalBrowseShellCmdRefresh..<SNR>24_NetrwRefresh
..netrw#LocalBrowseCheck..<SNR>24_NetrwBrowse
..<SNR>24_BrowserMaps:
line 106:
E15: Invalid expression: s:didstarstar || !mapcheck("<s-up>","n")
Error detected while processing function <SNR>24_NetrwMarkFileCopy
..<SNR>24_LocalBrowseShellCmdRefresh..<SNR>24_NetrwRefresh
..netrw#LocalBrowseCheck..<SNR>24_NetrwBrowse
..<SNR>24_PerformListing..<SNR>24_NetrwBookHistHandler
..<SNR>24_NetrwBookmarkMenu:
line 10:
E329: No menu "Bookmarks"
Error detected while processing function <SNR>24_NetrwMarkFileCopy
..<SNR>24_LocalBrowseShellCmdRefresh..<SNR>24_NetrwRefresh
..netrw#LocalBrowseCheck..<SNR>24_NetrwBrowse
..<SNR>24_PerformListing..<SNR>24_NetrwBookHistHandler
..<SNR>24_NetrwBookmarkMenu:
line 11:
E329: No menu "Bookmark Delete"
E486: Pattern not found: ^$
E486: Pattern not found: ^\d\{3}ÿ\d\{3}\/
E486: Pattern not found: \.h$
E486: Pattern not found: ^\d\{3}ÿ\d\{3}\/
E486: Pattern not found: \.c$
E486: Pattern not found: ^\d\{3}ÿ\d\{3}\/
E486: Pattern not found: \.cpp$
E486: Pattern not found: ^\d\{3}ÿ\d\{3}\/
E486: Pattern not found: \.o$
E486: Pattern not found: ^\d\{3}ÿ\d\{3}\/
E486: Pattern not found: \.obj$
E486: Pattern not found: ^\d\{3}ÿ\d\{3}\/
E486: Pattern not found: \.info$
E486: Pattern not found: ^\d\{3}ÿ\d\{3}\/
E486: Pattern not found: ^\d\{3}ÿ\d\{3}\/
E486: Pattern not found: \.bak$
E486: Pattern not found: ^\d\{3}ÿ\d\{3}\/
E486: Pattern not found: ^\d\{3}ÿ\d\{3}\/
Because of the identicalness, I assumed that these messages didn't
contain the clue to the problem.
From a previous posting on this forum I was advised to try netrw 147,
which I un-vimballed into "c:/Program Files (x86)/Vim/vimfiles". No
need to set g:vimball_home because the above directory was the first
valid directory in runtimepath. I confirmed that files unloaded into
their subdirectories and that it superceded the corresponding files in
"c:/Program Files (x86)/Vim/vim73". In fact, I later also un-
vimballed them into "c:/Program Files (x86)/Vim/vim73". In both
cases, it seemed that netrw failed to run. Doing ":e ." yields the
message
"." is a directory
and the buffer appears exactly as an empty file would. Redirecting
messages to @a captures these messages:
"." is a directory
Error detected while processing function <SNR>14_LocalBrowse:
line 14:
E117: Unknown function: netrw#LocalBrowseCheck
I confirmed that all files and subdirectories were readable and
executable/accessible by all users and that there was no funny
business with Windows 7 virtualization i.e. the following directory
was completely empty of visible & hidden files:
c:/Users/LoalAdmin/AppData/Local/VirtualStore
I've been troubleshooting this problem a number of hours, and
somewhere in my rummaging about, I recall getting an warning message
that netrw 147 required vim 7.3.XXX, where XXX was a decimal number in
the 100-199 range. I don't recall how I got it, but I remember
wondering whether XXX corresponded to the patch number. If so, that
might explain it because the gvim for Xwin was around patch 172 (which
was higher than XXX) whereas Windows gvim only "Included patches:
1-46". Is this correct? My Windows version is:
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Oct 27 2010 17:59:02)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-46
Compiled by Bram@KIBAALE
Big version with GUI. Features included (+) or not (-):
+arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset
+cindent
+clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info
+comments
+conceal +cryptv +cscope +cursorbind +cursorshape +dialog_con_gui
+diff
+digraphs -dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search
+farsi
+file_in_path +find_in_path +float +folding -footer +gettext/dyn -
hangul_input
+iconv/dyn +insert_expand +jumplist +keymap +langmap +libcall
+linebreak
+lispindent +listcmds +localmap -lua +menu +mksession +modify_fname
+mouse
+mouseshape +multi_byte_ime/dyn +multi_lang -mzscheme +netbeans_intg
+ole
-osfiletype +path_extra +perl/dyn +persistent_undo -postscript
+printer
-profile +python/dyn +python3/dyn +quickfix +reltime +rightleft +ruby/
dyn
+scrollbind +signs +smartindent -sniff +startuptime +statusline -
sun_workshop
+syntax +tag_binary +tag_old_static -tag_any_white +tcl/dyn -tgetent
-termresponse +textobjects +title +toolbar +user_commands +vertsplit
+virtualedit +visual +visualextra +viminfo +vreplace +wildignore
+wildmenu
+windows +writebackup -xfontset -xim -xterm_save +xpm_w32
system vimrc file: "$VIM\vimrc"
user vimrc file: "$HOME\_vimrc"
2nd user vimrc file: "$VIM\_vimrc"
user exrc file: "$HOME\_exrc"
2nd user exrc file: "$VIM\_exrc"
system gvimrc file: "$VIM\gvimrc"
user gvimrc file: "$HOME\_gvimrc"
2nd user gvimrc file: "$VIM\_gvimrc"
system menu file: "$VIMRUNTIME\menu.vim"
Compilation: cl -c /W3 /nologo -I. -Iproto -DHAVE_PATHDEF -DWIN32 -
DFEAT_CSCOPE -DFEAT_NETBEANS_INTG -DFEAT_XPM_W32 -DWINVER=0x0400 -
D_WIN32_WINNT=0x0400 /Fo.\ObjGOLYHTR/ /Ox /GL -DNDEBUG /Zl /MT -
DFEAT_OLE -DFEAT_MBYTE_IME -DDYNAMIC_IME -DFEAT_GUI_W32 -
DDYNAMIC_ICONV -DDYNAMIC_GETTEXT -DFEAT_TCL -DDYNAMIC_TCL -
DDYNAMIC_TCL_DLL=\"tcl83.dll\" -DDYNAMIC_TCL_VER=\"8.3\" -DFEAT_PYTHON
-DDYNAMIC_PYTHON -DDYNAMIC_PYTHON_DLL=\"python27.dll\" -DFEAT_PYTHON3 -
DDYNAMIC_PYTHON3 -DDYNAMIC_PYTHON3_DLL=\"python31.dll\" -DFEAT_PERL -
DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\"perl512.dll\" -DFEAT_RUBY -
DDYNAMIC_RUBY -DDYNAMIC_RUBY_VER=191 -DDYNAMIC_RUBY_DLL=\"msvcrt-
ruby191.dll\" -DFEAT_BIG /Fd.\ObjGOLYHTR/ /Zi
Linking: link /RELEASE /nologo /subsystem:windows /LTCG:STATUS
oldnames.lib kernel32.lib advapi32.lib shell32.lib gdi32.lib
comdlg32.lib ole32.lib uuid.lib /machine:i386 /nodefaultlib gdi32.lib
version.lib winspool.lib comctl32.lib advapi32.lib shell32.lib /
machine:i386 /nodefaultlib libcmt.lib oleaut32.lib user32.lib /
nodefaultlib:python27.lib /nodefaultlib:python31.lib e:\tcl\lib
\tclstub83.lib WSock32.lib e:\xpm\lib\libXpm.lib /PDB:gvim.pdb -debug
--
--
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 because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
macvim font for windows
I have a Mac at home, but at work I use a Windows machine. I'd like my Vim at work look the same as it is at home, in particular the font. Does anybody know where I can get the font used for MacVim, so I could use it on my Windows Machine? I typed set guifont? on a Mac but the value was blank. So I don't know the name of the font used.
Any help is appreciated.
--
--
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 because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Any help is appreciated.
--
--
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 because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Register overwritten only when clipboard=unnamed
PARK, Kyung-Kook wrote:
> On Saturday, March 30, 2013 3:03:45 AM UTC+9, Bee wrote:
>> On Mar 29, 8:26 am, <kyu...@gmail.com> wrote:
>>
>>> I am trying to copy & paste a word under the cursor.
>>
>>
>> Are you trying to 'exchange' the word under the cursor with the one on
>>
>> the clipboard?
>>
>>
>>
>> What version of vim?
>>
>> What platform: Windows, Linux, Mac ?
>>
>>
>>
>> Bill
> I am using gVim 7.3 on Windows x64 platform.
>
> Yes, I want to replace a word at the cursor position by
> another word yanked from a different position.
>
Then you might like visswap.vim.
You can get visswap from:
http://www.drchip.org/astronaut/vim/index.html#VISSWAP
Quick overview: swapping text using visual mode
Use visual mode (any of the three) to select some text; press ctrl-y .
Use visual mode (any of the three) to select some other text; press
ctrl-x .
I think of ctrl-y as my "yank" step and ctrl-x as my "exchange" step.
To install if you're using vim7.1 or later:
Install a new version of visswap:
vim visswap.vba.gz
:so %
:q
Regards,
C 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 because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> On Saturday, March 30, 2013 3:03:45 AM UTC+9, Bee wrote:
>> On Mar 29, 8:26 am, <kyu...@gmail.com> wrote:
>>
>>> I am trying to copy & paste a word under the cursor.
>>
>>
>> Are you trying to 'exchange' the word under the cursor with the one on
>>
>> the clipboard?
>>
>>
>>
>> What version of vim?
>>
>> What platform: Windows, Linux, Mac ?
>>
>>
>>
>> Bill
> I am using gVim 7.3 on Windows x64 platform.
>
> Yes, I want to replace a word at the cursor position by
> another word yanked from a different position.
>
Then you might like visswap.vim.
You can get visswap from:
http://www.drchip.org/astronaut/vim/index.html#VISSWAP
Quick overview: swapping text using visual mode
Use visual mode (any of the three) to select some text; press ctrl-y .
Use visual mode (any of the three) to select some other text; press
ctrl-x .
I think of ctrl-y as my "yank" step and ctrl-x as my "exchange" step.
To install if you're using vim7.1 or later:
Install a new version of visswap:
vim visswap.vba.gz
:so %
:q
Regards,
C 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 because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Get netrw to ignore executability of file
Christian Brabandt wrote:
> On windows, there is no executable bit and is actually not needed,
> because only certain file types are executable. So in principle is
> should be possible to simply highlight .exe .bat .cmd .com files as
> executable on Windows. regards, Christian
However, under cygwin, under windows, plus NTFS, there is an executable
bit and it does affect whether cygwin may try to execute that file or
not (especially scripts). There's also ACLs, which may also cause files
to be considered executable. Again, see (using cygwin)\:
man getfacl
man setfacl
Regards,
C 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 because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> On windows, there is no executable bit and is actually not needed,
> because only certain file types are executable. So in principle is
> should be possible to simply highlight .exe .bat .cmd .com files as
> executable on Windows. regards, Christian
However, under cygwin, under windows, plus NTFS, there is an executable
bit and it does affect whether cygwin may try to execute that file or
not (especially scripts). There's also ACLs, which may also cause files
to be considered executable. Again, see (using cygwin)\:
man getfacl
man setfacl
Regards,
C 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 because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Subscribe to:
Posts (Atom)