Re: Possible to make the + Register the default?
Yes, now it's possible to make the + Register the default so that it works with the X Window clipboard used in linux. In vim 7.3.74 and higher you can *set clipboard=unnamedplus* to alias unnamed register to the + register, which is the X Window clipboard. -- View this message in context: http://vim.1045645.n5.nabble.com/Possible-to-make-the-Register-the-default-tp1156330p5711462.html Sent from the Vim - General mailing list archive at Nabble.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
Need help to remove multiple copies of text
I have an XML document and wanted to remove the following strings: There are hundreds of places where the alphabetical-indexes are interspersed and "String", "key1" and "S" are variable, so what vi command string can I use to delete these text? I have tried many combinations, the simplest being: :1,$ s~~~g but the problem is with ".*", of which the search pattern takes out everything to very the last "/>" pattern found which is not what I want. -- 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
Need help to remove multiple copies of text
I have an XML document and wanted to remove the following strings: There are hundreds of places where the alphabetical-indexes are interspersed and "String", "key1" and "S" are variable, so what vi command string can I use to delete these text? I have tried many combinations, the simplest being: :1,$ s~~~g but the problem is with ".*", of which the search pattern takes out everything to very the last "/>" pattern found which is not what I want. -- 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: Problem Using :substitute to Replace Empty Fields in Tab Delimited File
On Wed, Oct 24, 2012 at 11:05 PM, John Slattery wrote: > Hi, > > In a tab delimited data file I want to replace empty fields with \N. I wasn’t > getting the result I expected and began working with a simple test file that > looked as follows with set list: > > ^I^I^I^I^I$ > ^I^I^I^I$ > ^I^I^I$ > ^I^I$ > ^I$ > $ For simplicity of typing here, I assumed a comma separated file: ,$ $ ,,,$ ,,$ ,$ $ The '$' is a literal dollar sign I assume - and is not meant to imply end-of-line. > The desired result would be: > > \N^I\N^I\N^I\N^I\N^I\N$ > \N^I\N^I\N^I\N^I\N$ > \N^I\N^I\N^I\N$ > \N^I\N^I\N$ > \N^I\N$ > \N$ I also simplified the replacement pattern to just "N". So we are looking for: N,N,N,N,N,N$ N,N,N,N,N$ N,N,N,N$ N,N,N$ N,N$ N$ > > What I started with, and what seemed the most obvious way to do it, doesn’t > work, leaving the final field of multi-field lines unfilled: I think the question is "what constitutes an empty field?". There are four patterns: ,, - a comma followed by comma ,$ - a comma followed by dollar , - a comma at start of line $ - start of line followed by dollar. So an empty field is: "either a start of line (^) or comma, followed by either a comma or a dollar". So the substitute pattern becomes: %s;\(^\|,\)\ze\(,\|\$\);\1N;gc To now look at the original problem, the pattern is: %s;\(^\|^I\)\ze\(^I\|\$\);\1\\N;gc ^I must be replaced by the literal tab character. Note: for some reason, the same substitute command as above, but with only "g" flag (and not "gc"), does not work for me! Still checking that.. > > %s/\(^\|\t\)\@<=\(\t\|$\)\@=/\\N/g > > The following works, the only difference being the match on end-of-line > instead of end-of-line at end of pattern with zero width: > > %s/\(^\|\t\)\@<=\(\t\|\n\)\@=/\\N/g > > Using zs and ze instead of @<= and @=, the following did not work, strangely > leaving the second field of multi-field lines unfilled: > > %s/\(^\|\t\)\zs\ze\(\t\|$\)/\\N/g Yes - I see this issue as well! And if you use "gc", it works correctly. > > Both of the commands above that failed achieve the desired result if executed > repeatedly until the command returns E486: Pattern not found: …. > > Vim is v7.3.429 as packaged for the Lubuntu 12.04 repositories. Same here. -- 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: gvim --help
Christian Brabandt wrote: > On Tue, October 23, 2012 21:48, Marc Weber wrote: > > What magic is gvim doing to hide its documentation? > > > > I understand this: > > [marc@nixos:~]$ gvim --help 1> /tmp/file; ls -l /tmp/file > > 3326 (bytes in /tmp/file) > > > > I'd expect stdout to be printed to my console > > [marc@nixos:~]$ gvim --help 2> /tmp/file; ls -l /tmp/file > > 0 (bytes in /tmp/file) > > > > I'd expect stdout to be written to the file > > [marc@nixos:~]$ bash -c "(gvim --help) >/tmp/file 2>&1" ; ls -l /tmp/file > > 0 (bytes in /tmp/file) > > > > So why is gvim hiding its documentation when stderr is redirected to a > > file? > > Vim checks, whether stderr is a terminal and if not, it doesn't > display anything and quits. But vim with a GNOME gui, works as > expected. That is indeed a little bit strange. > > Bram, the problem is in command_line_scan() when parsing the command > line options, gui.starting is set to FALSE only for GNOME builts, but > in mch_msg(), which is used for displaying the usage() > function explicitly checks for the GUI versions: > (isatty(2) || !(gui.in_use || gui.starting)) > > Since for non-gnome gui versions, gui.starting is still true, the > whole conditions becomes false and vim exits without displaying > anything. > > This patch should make it work with all gui versions of Vim: > > diff --git a/src/main.c b/src/main.c > --- a/src/main.c > +++ b/src/main.c > @@ -1933,8 +1933,9 @@ > break; > > case 'h': /* "-h" give help message */ > -#ifdef FEAT_GUI_GNOME > - /* Tell usage() to exit for "gvim". */ > +#ifdef FEAT_GUI > + /* Tell usage() to exit for "gvim". > + * but make sure usage() is displayed, even if stderr is > redirected */ > gui.starting = FALSE; > #endif > usage(); > > This fixes only gvim -h 2>/dev/null while gvim --help 2>/dev/null > still only displays the GNOME specific options (or nothing for > non-gnome builts) The idea is that when there is no terminal, gvim is started from the desktop, the output of --help is displayed in a GUI window. Thus you can't set gui.starting to FALSE in general. Vim detects that there is no terminal by checking if stderr is a tty. I don't know if there is a more reliable check. Perhaps checking whether stdin is a tty? GNOME has some weird startup stuff that exits in unexpected ways. I don't recall the details. The solution is somewhere else... -- A consultant is a person who takes your money and annoys your employees while tirelessly searching for the best way to extend the consulting contract. (Scott Adams - The Dilbert principle) /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- 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: Indenting
On 25/10/12 04:02, analogsix wrote: I created a 'scratch notes file' of VIM commands on gvim on my home pc's Fedora desktop environment. When I port this file to my workplace's UNIX environment and launch the notes from VIM, my tab spacing is thrown off. For example, at home my text looks like this: command1<- comment blah blah blah cmd2<- comment blah blah blah comnd3 <- comment blah blah blah at work, I get a near similar output when I open the file through VIM. When I open through gvim, I get something like this: command1<- comment blah blah blah cmd2 <- comment blah blah blah comnd3 <- comment blah blah blah Can you assist please? I think that tab stops are not set to the same width at home and at work. The responsible setting is 'tabstop' whose standard value is 8. I recommend keeping hard tabs at 8 characters and using soft tabs (by setting 'softtabstop' and/or 'shiftwidth') if you want the tab key to move the cursor by a different amount. Anyway: To see the file identically regardless of the tabstop setting, make sure it is edited with 'expandtab': 1) Add a modeline near the top or bottom (no more than 5 lines from the start or end), see :help modeline -- here are examples: Type 1 (nothing can follow on the same line) vim:et // vim:et = vim:et Type 2 (anything can precede, or, after a colon, follow) /* vim: set et :*/ == vim: set et :== This line is to tell Vim to ":setlocal expandtab" when editing this file. It needs 'modeline' on in order to work. 2) Then (once only, and at home where the file looks right) :setlocal et :retab! This will replace all tabs by the proper number of spaces, so you will see it the same way regardless of where Vim thinks the tab stops are. See: :help 'ts'" width of hard tab characters :help 'et'" if on, hitting adds spaces :help :retab " to change tabs <-> spaces :help modeline" what a modeline may look like :help 'modeline' " enable/disable modelines :help 'modelines' " how far from top/bottom they may be and possibly :help 'sts' " soft tab stop :help 'sw'" width of indenting columns Best regards, Tony. -- Talk sense to a fool and he calls you foolish. -- Euripides -- 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: Indenting
On 10/24/12 21:02, analogsix wrote: > I created a 'scratch notes file' of VIM commands on gvim on my home pc's > Fedora desktop environment. > When I port this file to my workplace's UNIX environment and launch the notes > from VIM, my tab spacing is thrown off. For example, at home my text looks > like this: > > command1<- comment blah blah blah > cmd2<- comment blah blah blah > comnd3 <- comment blah blah blah > > at work, I get a near similar output when I open the file through VIM. When I > open through gvim, I get something like this: > > command1<- comment blah blah blah > cmd2 <- comment blah blah blah > comnd3 <- comment blah blah blah > > Can you assist please? Check the settings for your tab-stops on both ends: :set ts? sts? et? sw? One of either 'ts' or 'sts' settings is most likely the culprit, but it's helpful to know the others too. Just make sure that you have the same setting for both in your vimrc and you should be good to go[*]. -tim [*] there are some caveats if you only want this to apply to one particular file name/type, in which case you can set it in an autocmd that gets triggered upon opening the file. :help BufRead :help 'ts' :help 'sts' :help autocmd -- 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: Spellcheck on Tex-Files
On Tuesday, October 16, 2012 10:47:54 PM UTC-4, skeept wrote:
> On Tuesday, October 16, 2012 3:10:38 PM UTC-4, Charles Campbell wrote:
>
> > > I would gladly put the specific rules in my after/ftplugin, but
>
> >
>
> > unfortunately I don't know exactly what to put there. Could you please
>
> >
>
> > tell me what specifically I would put there or point me for some files
>
> >
>
> > with specific examples?
>
> >
>
> >
>
> >
>
> > You need to recognize the regions and use add=@NoSpell with them.
>
> >
>
> >
>
> >
>
> > :help syn-region
>
> >
>
> >
>
> >
>
> > syntax/tex.vim has a number of "syn region" usages that you could use as
>
> >
>
> > an example. See "syn region DocZone" for example. You'll probably want
>
> >
>
> > to contains=@texFoldGroup, in the text region.
>
> >
>
> >
>
> >
>
> > Regards,
>
> >
>
> > C Campbell
>
>
>
> What I put in my after/ftplugin/tex.vim is
>
> syn region texTabularPos matchgroup=texSection
> start='\\begin\s*{\s*tabular\s*}{' end='}' fold
> contains=@texFoldGroup,@texDocGroup
>
>
>
> but it doesn't seem to work (I still see the the word marked as a miss spell).
>
>
>
> I also defined the following map
>
> map :echo "hi<" . synIDattr(synID(line("."),col("."),1),"name") . '>
> trans<'
>
> \ . synIDattr(synID(line("."),col("."),0),"name") . "> lo<"
>
> \ . synIDattr(synIDtrans(synID(line("."),col("."),1)),"name") . ">"
>
> from
>
> http://vim.wikia.com/wiki/Identify_the_syntax_highlighting_group_used_at_the_cursor
>
>
>
> and when I use it in the region I am interested I see
>
> hi trans<
>
>
>
> so I guess the region is not correctly defined.
>
> Any input is appreciated.
>
>
>
> Regards,
>
>
>
> Jorge
I would really appreciate a specific example on how to acomplish this.
My last try is
syn region texComment matchgroup=texStatement start='{tabular}{' end='}'
\ contains=@NoSpell
but it doesn't work...
--
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
Indenting
I created a 'scratch notes file' of VIM commands on gvim on my home pc's Fedora desktop environment. When I port this file to my workplace's UNIX environment and launch the notes from VIM, my tab spacing is thrown off. For example, at home my text looks like this: command1<- comment blah blah blah cmd2<- comment blah blah blah comnd3 <- comment blah blah blah at work, I get a near similar output when I open the file through VIM. When I open through gvim, I get something like this: command1<- comment blah blah blah cmd2 <- comment blah blah blah comnd3 <- comment blah blah blah Can you assist please? -- 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 check for $ProgramFiles(x86) ?
On Wed, Oct 24, 2012 at 2:50 PM, Ben Fritz wrote:
> On Wednesday, October 24, 2012 4:25:41 PM UTC-5, Gary Johnson wrote:
>>
>> I think the following or a variation should do it. I was only able
>> to test it on names without parentheses as I didn't see any variable
>> names with them in my environment.
>>
>> split(system('set ProgramFiles(x86)', '=')[1]
>>
>> gets the value and
>>
>> system('set ProgramFiles(x86)') =~ 'not defined'
>>
>> will evaluate to true if the variable is not defined.
>>
>
> Not quite. You get hit by Windows *#$&#ing command-line quoting.
>
> This works for me:
>
> :echo system('set PROGRAMFILES^(x86^)')
In the past, I've solved very similar problems with batch files [1]
and Bash scripts [2].
The parentheses in the environment variable name are asinine.
[1]
http://weblogs.asp.net/george_v_reilly/archive/2009/09/11/launching-32-bit-applications-from-batchfiles-on-win64.aspx
@setlocal
@set _pf=%ProgramFiles%
@if not "[%ProgramFiles(x86)%]"=="[]" set _pf=%ProgramFiles(x86)%
@start "" /b "%_pf%\SourceGear\DiffMerge\DiffMerge.exe" %*
[2] http://thread.gmane.org/gmane.comp.gnu.mingw.user/31262/focus=31273
#!/bin/sh
pf=`env | sed -n s,'^PROGRAMFILES(X86)=',,p`
if [ -z "$pf" ]; then pf="$PROGRAMFILES"; fi
"$pf/SourceGear/DiffMerge/DiffMerge.exe" $*
--
/George V. Reilly geo...@reilly.org Twitter: @georgevreilly
http://www.georgevreilly.com/blog http://blogs.cozi.com/tech
--
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 check for $ProgramFiles(x86) ?
On Wednesday, October 24, 2012 4:25:41 PM UTC-5, Gary Johnson wrote:
>
> I think the following or a variation should do it. I was only able
> to test it on names without parentheses as I didn't see any variable
> names with them in my environment.
>
> split(system('set ProgramFiles(x86)', '=')[1]
>
> gets the value and
>
> system('set ProgramFiles(x86)') =~ 'not defined'
>
> will evaluate to true if the variable is not defined.
>
Not quite. You get hit by Windows *#$&#ing command-line quoting.
This works for me:
:echo system('set PROGRAMFILES^(x86^)')
--
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 check for $ProgramFiles(x86) ?
On 2012-10-24, Timothy Madden wrote:
> Hello
>
> I am trying to see if the current system is 32-bit or 64-bit Windows.
> On 64-bit Windows the environment variable $ProgramFiles(x86) is
> known to exits, but Vim will just check for $ProgramFiles and the
> appendthe '(x86)' part. Is there a way to check if the environment
> variable $ProgramFiles(x86) exists in the current environment ?
>
> I tried both expand('$ProgramFiles(x86)') and
> exists('$ProgramFiles(x86)'), both of them check the '$ProgamFiles'
> part only.
I think the following or a variation should do it. I was only able
to test it on names without parentheses as I didn't see any variable
names with them in my environment.
split(system('set ProgramFiles(x86)', '=')[1]
gets the value and
system('set ProgramFiles(x86)') =~ 'not defined'
will evaluate to true if the variable is not defined.
Regards,
Gary
--
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
Thread safety not mentioned for python bindings
Hello I read the python bindings help file (if_python.txt) and I found nothing about thread safety. Although Vim itself does not use threads, the invoked python code can create them and than the main thread can return control to Vim normally. I would like to write a plug-in that listens to a TCP connection in the background, and somehow notifies Vim when new data arrives on the socket. Now, since the documentation says nothing about it, I would assume the python language bindings are not thread-safe, or even if they are thread-safe, that is still an undocumented feature. But does anyone have more specific information please ? Has anyone tried working with treads from python code in Vim ? Can the help file be updated to mention this aspect ? Thank you, Timothy Madden -- 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 check for $ProgramFiles(x86) ?
On Wednesday, October 24, 2012 3:25:41 PM UTC-5, Timothy Madden wrote:
>
> I am trying to see if the current system is 32-bit or 64-bit Windows. On
> 64-bit Windows the environment variable $ProgramFiles(x86) is known to
> exits, but Vim will just check for $ProgramFiles and the appendthe
> '(x86)' part. Is there a way to check if the environment variable
> $ProgramFiles(x86) exists in the current environment ?
>
> I tried both expand('$ProgramFiles(x86)') and
> exists('$ProgramFiles(x86)'), both of them check the '$ProgamFiles' part
> only.
>
:help expand-environment-var says that only letters, digits, and _ are allowed
in the environment variable name. I am not sure whether there is a workaround.
Perhaps Vim needs to allow a different set of characters for Windows
environment variables, or some way to escape the characters to indicate they
are part of the name.
--
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 check for $ProgramFiles(x86) ?
What your doing I would think would work, but check in the system applet in
control panel.
On Wed, Oct 24, 2012 at 3:25 PM, Timothy Madden wrote:
> Hello
>
> I am trying to see if the current system is 32-bit or 64-bit Windows. On
> 64-bit Windows the environment variable $ProgramFiles(x86) is known to
> exits, but Vim will just check for $ProgramFiles and the appendthe '(x86)'
> part. Is there a way to check if the environment variable
> $ProgramFiles(x86) exists in the current environment ?
>
> I tried both expand('$ProgramFiles(x86)') and
> exists('$ProgramFiles(x86)'), both of them check the '$ProgamFiles' part
> only.
>
> Thank you,
> Timothy Madden
>
> --
> 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
>
--
Gerald Klein DBA
contac...@geraldklein.com
www.geraldklein.com
How to check for $ProgramFiles(x86) ?
Hello
I am trying to see if the current system is 32-bit or 64-bit Windows. On
64-bit Windows the environment variable $ProgramFiles(x86) is known to
exits, but Vim will just check for $ProgramFiles and the appendthe
'(x86)' part. Is there a way to check if the environment variable
$ProgramFiles(x86) exists in the current environment ?
I tried both expand('$ProgramFiles(x86)') and
exists('$ProgramFiles(x86)'), both of them check the '$ProgamFiles' part
only.
Thank you,
Timothy Madden
--
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
Problem Using :substitute to Replace Empty Fields in Tab Delimited File
Hi, In a tab delimited data file I want to replace empty fields with \N. I wasn’t getting the result I expected and began working with a simple test file that looked as follows with set list: ^I^I^I^I^I$ ^I^I^I^I$ ^I^I^I$ ^I^I$ ^I$ $ The desired result would be: \N^I\N^I\N^I\N^I\N^I\N$ \N^I\N^I\N^I\N^I\N$ \N^I\N^I\N^I\N$ \N^I\N^I\N$ \N^I\N$ \N$ What I started with, and what seemed the most obvious way to do it, doesn’t work, leaving the final field of multi-field lines unfilled: %s/\(^\|\t\)\@<=\(\t\|$\)\@=/\\N/g The following works, the only difference being the match on end-of-line instead of end-of-line at end of pattern with zero width: %s/\(^\|\t\)\@<=\(\t\|\n\)\@=/\\N/g Using zs and ze instead of @<= and @=, the following did not work, strangely leaving the second field of multi-field lines unfilled: %s/\(^\|\t\)\zs\ze\(\t\|$\)/\\N/g Both of the commands above that failed achieve the desired result if executed repeatedly until the command returns E486: Pattern not found: …. Vim is v7.3.429 as packaged for the Lubuntu 12.04 repositories. Am I misunderstanding something or is Vim not handling this correctly? Thanks for reading along and any help you may offer. John Slattery -- 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: Vim under cygwin
On 23 Oct 2012, at 03:42, Tony Mechelynck wrote: > On 12/07/12 18:06, Andrew Long wrote: >> >> >> Begin forwarded message: >> >>> From: "Long, Andrew" >>> Subject: Vim under cygwin >>> Date: 12 July 2012 10:18:32 GMT+01:00 >>> To: andrew.l...@mac.com >>> >>> >>> 0126792@XP037234 ~/NRock/Projects/dbJnlStats/working >>> $ vim -gS Session.vim >>> cygwin warning: >>> MS-DOS style path detected: C:\winnt\profiles\0126792\vimfiles\plugin >>> Preferred POSIX equivalent is: /home/0126792/vimfiles/plugin >>> CYGWIN environment variable option "nodosfilewarning" turns off this >>> warning. >>> Consult the user's guide for more details about POSIX paths: >>> http://cygwin.com/cygwin-ug-net/using.html#using-pathnames >>> >>> 0126792@XP037234 ~/NRock/Projects/dbJnlStats/working >>> >>> -- >>> Andrew LongIT Specialist >>> Mainframe ManagementVirgin Money >>> +44 (191) 279 4537 Andrew dot Long at Virgin Money dot com >>> >>> >> >> The message above (sometimes) comes out of a fresh XTerm session when I >> start vim using a saved Session.vim file. I've tried to locate the offending >> file using egrep on all the .vim files in my vimfiles folder (which has a >> soft link of '.vim' pointing at it!)also in the Session.vim file, but no >> matches. >> >> It doesn't seem to cause any real problems, but it's a message I'd like to >> get rid of. Any suggestions as to how I can find the problem and put it >> right, please? >> >> Regards, Andy >> > > This message might happen if you use the same Session.vim with a > native-Windows Vim (compiled to run in Windows without Cygwin, for instance > Steve Hall's "Vim without Cream") and with a Cygwin version of Vim (compiled > to use the Cygwin DLL, for instance the console Vim distributed with Cygwin) > and if both of them use :mksession (for instance at shutdown). Then the > native-Windows Vim will probably write a Windows-like path (with backslashes) > which the Cygwin Vim won't like. I no longer have a native windows vim installed on my system at work - I uninstalled it many years ago and have stuck with cygwin ever since. > > If that string is in none of your *.vim files, it might be in a "system > vimrc" provided by Cygwin (see near the middle of the output of the :version > command of your Cygwin Vim to know where it is — $VIM/vimrc is the default, > but /etc/vimrc is often set instead at compile-time, in both cases normally > with no initial dot in the filename) or in a vim.bat wrapper if you have one > in your $PATH, or if none of these match, in some custom change brought by > the Cygwin engineers into the Vim C source. (The "system vimrc" case seems > most likely to me.) I haven't yet looked in all of the *.vim files. I don't have a system vimrc file at $VIM, thogh there is a vimrc_sample in $VIM/vim73 ($VIM points at /usr/share/vim) I think the path must be constructed somehow, as it's inheriting the path to my $HOME directory (either in a POSIX or Windows style) and then putting the terminal name of the .vim/vimfiles folder in front of 'plugin'; I only hear about it when it's using the Windows form of the path. If I get a chance before I go on holiday next week I'll try to find the place in my local or system *.vim files. Regards, Andy -- Andrew Long andrew dot long at mac dot 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: Issue with netrw copy and move
Marcin Szamotulski wrote: On 16:49 Tue 10 Apr , Charles Campbell wrote: A Loumiotis wrote: Hi, I'm facing exactly the same problem that Bart mentioned with netrw v146a as well. I'm using gVim 7.3 on Windows XP SP3. I'm not sure what other MS-DOS commands to use besides "MOVE" and "COPY" to set the variables "g:netrw_localmovecmd" and "g:netrw_localcopycmd". Any ideas? Try v146c (http://www.drchip.org/astronaut/vim/index.html#NETRW). I'd like to know if it works before giving it to Bram for major distribution. I'll be trying to get mingw and compile vim for native windows myself soon. I had a native vim under Windows, but that was before the latest updates to cygwin meant that the cygwin compiler no longer handles native windows executable production. 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 Hello, It seems that the function mathmenu#StartMathMenu() contains small bug in the definition of maps: MathMenuSubscript, MathMenuSuperscript and MathMenuMathify. The following I found in autoload/mathmenu.vim: vno MathMenuSubscript gv:B call mathmenu#Subscript() vno MathMenuSuperscript gv:B call mathmenu#Superscript() vno MathMenuMathify gv:B call mathmenu#Mathify() I guess in all three the B should be just , or just: vno MathMenuSubscript :call mathmenu#Subscript() vno MathMenuSuperscript :call mathmenu#Superscript() vno MathMenuMathify :call mathmenu#Mathify() And this works here just fine. Hello! Sorry its taken so long to reply to this (I think that my home computer downloaded the email and I didn't see it on my work computer). Actually the :B is intentional ; what's not is the missing plugin that needs to support this (vis.vim). I'll make the vis plugin part of the mathmenu package. You can get vis by itself from my website: http://www.drchip.org/astronaut/vim/index.html#VIS . 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
Re: Ruby 1.9 on Windows?
On Tue, Oct 23, 2012 at 10:34 PM, Cesar Romani wrote: > > Are you building vim on windows 32 or 64bit? I built vim 7.3.712 > with mingw on windows 7 32bit using Ruby 1.9.3-p125 without any > problem. I'm building 32-bit on Windows 7 with Cygwin. -- Steve Hall [ digitect dancingpaper 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: dab on escaped backslashes
On 2012-10-23 05:57, Bram Moolenaar wrote: What language has a backslash for ( but not for )? We should handle that in a more generic way then, not just for "dib". Perl for one. See $ perldoc perlref /enumerated Also something like /(...\(...)/ is very well possible in a regular expression as well. /bpj -- 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
