Re: How about dropping the MzScheme interface?

[Eric Christopherson]

On Sun, Feb 2, 2020 at 7:00 PM rob  wrote:

> I'm wondering if this is a person at all.  I suspect some one or group is
> testing their AI bot.
>
> The question is just too bizarre for an actual human to be asking.
>
> --rob solomon
>
I know I found "John Mon"'s email address on Scribd in a supposed dump of
email addresses and passwords, so I wouldn't be surprised.

John, if you're listening: Change your password.


>
> On 1/29/20 8:57 AM, Jesus Arocho wrote:
>
> Probably so.
>
> On Wed, Jan 29, 2020 at 7:57 AM Christian Brabandt 
> wrote:
>
>>
>> On Mi, 29 Jan 2020, Jesus Arocho wrote:
>>
>> > I have been reading this thread and I am not sure I understand the
>> question:
>> > "why would anyone need to alter text"
>>
>> I have actually been wondering, if he has been trolling successfully.
>>
>> Best,
>> Christian
>> --
>> 10E12  Mikrophone = 1 Megaphon
>> 10E-6 Fisch = 1 Mikrofiche
>> 10E21 Picolos = 1 Gigolo
>> 10 Rationen = 1 Dekoration
>> 3 1/3 Tridents = 1 Dekadent
>> 10 Monologe = 5 Dialoge
>> 2 Monogramme = 1 Diagramm
>>
>> --
>> --
>> 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+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/vim_use/20200129125716.GA803%40256bit.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
>
> ---
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_use/CACacrc0KbJsRb0%2BXK5vA639-zhuDdwS26zzCOUCpi2KAcoaM-A%40mail.gmail.com
> <https://groups.google.com/d/msgid/vim_use/CACacrc0KbJsRb0%2BXK5vA639-zhuDdwS26zzCOUCpi2KAcoaM-A%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> --
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_use/73a02e2d-d628-ab03-62f3-e04893fef10f%40fastmail.com
> <https://groups.google.com/d/msgid/vim_use/73a02e2d-d628-ab03-62f3-e04893fef10f%40fastmail.com?utm_medium=email_source=footer>
> .
>


-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_use/CADyB93BySbPJKJ9JZe14r-NgHadHP9zP%3D-NpLe-V-fc4871jVA%40mail.gmail.com.

Re: sed whole file

[Eric Christopherson]

On Tue, Oct 8, 2019 at 4:29 AM Paul  wrote:

> On Sun, Oct 06, 2019 at 12:25:20PM +0200, Bram Moolenaar wrote:
> >Perhaps we could go back to the original view when typing the search
> >separator.  So long as the user is typing the search pattern it is
> >useful to show the match, but when typing ":%s/foo/", thus starting to
> >type the replacement, it is useful to jump back?
> >
> >I actually cannot guess if the user wants to see the original text or
> >the context of what is going to be replaced. If you have something
> >specific, you can copy it beforehand.  And the jumping around can be
> >annoying.  Thus I rather leave it like it is.
>
> Not sure if this helps to contribute to the discussion, but personally, I
> like to see what is going to be replaced, and with what it will be
> replaced, so I can experiment and get the command right real-time, so I use
> the traces.vim plugin (https://github.com/markonm/traces.vim).
>

It can also be helpful to edit the command line as if it were a regular Vim
buffer, by executing q: in normal mode or using C-f after you've already
started entering the command line using :. I developed the habit of using
q/ to edit search lines when I explicitly don't want the cursor to jump to
the first occurrence of the string.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_use/CADyB93Bx7m8GP4pktiq%3DLjQqp-7jCRtac-RUe1cRbJ-qQR1yfw%40mail.gmail.com.

Re: Vim terminal syntax highlights

[Eric Christopherson]

On Mon, Jun 10, 2019 at 2:59 PM Tatenda Biti  wrote:

> On Saturday, June 8, 2019 at 11:38:23 AM UTC-4, JESii wrote:
> > I agree with meine -- when I look at your vim screenshot, it's clear to
> me that there IS synta highlighting applied to your file. It's just
> different than the newvim screenshot you provided.
> >
> > > > it probably depends on the colorscheme you use (what and how your
> syntax
> > > > is displayed) and on a line in your .vimrc: `syntax enable'
> > > >
> > > > see also `:help syntax' for further instructions on the use and
> > > > possibilities.
> > > >
> > > > //meine
> > >
> > > Pretty sure that is not the case:
> > >
> I don't think I was clear this is Gvim on windows. When you create a
> terminal buffer there are no colors. Do you use Windows Gvim and have
> colors in the terminal??
>

When you say "terminal", are you talking about the window at the bottom
that shows the Python interpreter? I'm pretty sure those "windows" (they
aren't really first-class citizens in Vim's window layout, e.g. you can't
resize them, move them around, etc.) have never had syntax coloring in Vim
proper; you need an actual window with an actual buffer (for instance a
file you're editing) to have syntax highlighting. I'm not sure how NeoVim
goes about it; it looks like they just use one style for things in quotes,
one for sequences that look like times, and another for sequences that look
like integer or floating-point numbers; whether there's an actual file
*type* behind all that I don't know. It might be that they just figured

In my experience, for whatever reason, when I run commands like :!python in
Windows gVim, I always get a separate Windows command prompt window that
holds the command I've launched from Vim. On other platforms, I get
something like what you show in the Vim 8 screenshot.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_use/CADyB93DTaM8nMonPdMaC4Ps-5WjOkv4-6y_fSXzF1ZzaQ-gUjQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Is it a matter of Unix ABC, B-A-BA', basics, school stuff, RTFM ?

[Eric Christopherson]

On Sat, Jun 30, 2018 at 1:02 PM, Renato Fabbri 
wrote:

> Em domingo, 24 de junho de 2018 05:05:17 UTC-3, Christian Brabandt
> escreveu:
> > On Sa, 23 Jun 2018, Renato Fabbri wrote:
> >
> > > https://www.facebook.com/groups/124928894848184/
> permalink/174455496562190/
> >
> > Please do not make us all click here random faceboook pages. Rather
> > either keep the discussion here or there. You might as well post a
> > summary of that page.
> >
> > Best,
> > Christian
> > --
> > Ein Glaube, der unruhig macht, ist Aberglaube.
> >   -- Carl Ludwig Schleich
>
> I am really sorry.
> Maybe I sould have given a short description.
> It is the same content of this email, in another Vim users group.
>

It would be helpful if you'd explain in plain English what your question
is. From the body of your message, it looks like you're just asking* if Vim
is the right tool for writing and reading; that's incredibly subjective and
open-ended. But your subject line doesn't make any sense to me.

* At least I'm assuming you're asking a question, since you end it with two
question marks; but your sentence doesn't include the word order inversion
usually used of questions in English, and has a period at the end, so it
looks like a statement.


> --
> --
> 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+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: syntax highlighting disabled with :bufdo e in gvim

[Eric Christopherson]

On Tue, Mar 20, 2018 at 1:48 PM, BPJ <b...@melroch.se> wrote:

> As the subject says: when I do `:bufdo e` in gvim syntax highlighting is
> turned off in the reloaded buffers.  Why? and more importantly: what can I
> do so that syntax is left on/turned on in all reloaded buffers?  The only
> fix I know of ATM is to do `:e` for each individual buffer, but the idea is
> of course to not have to do that!
>
> /bpj


Hi, BPJ.

It's messy, but here's a mapping I use for just such a purpose:

" Use b to start a bufdo command line that keeps highlighting active
" in the buffers it touches, even if they haven't been loaded yet. Also
" restores the # and % buffers afterward.
noremap b :let g:bufdo_bufnr=bufnr('%') \| let
g:bufdo_bufnr_prev=bufnr('#') \| bufdo set eventignore-=Syntax \|  \| exec
'buffer '.g:bufdo_bufnr_prev \| exec 'buffer
'.g:bufdo_bufnr

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Windows Subsystem for Linux and gvim

[Eric Christopherson]

On Sat, Mar 17, 2018 at 10:27 AM, Mun <mjeli...@gmail.com> wrote:

> Hi,
>
> I'm running Ubuntu on my PC via the Windows Subsystem for Linux (WSL)
> and of course it only comes with vim (not gvim).  However, I've also
> installed gvim80.  I can launch gvim from within the WSL Bash window
> but it doesn't see my WSL files.
>
> Web searches state it's not a good idea to try to access WSL files
> from Windows proper.  I just thought I'd ask this community if anyone
> has come up with a good solution to use gvim from within WSL.
>

If I understand correctly, the program that starts when you type gvim in
WSL (as you have it configured currently) is the Windows GVim; therefore I
believe you haven't installed gvim in the Linux part (via vim-gnome or
vim-gtk or similar). If you do install a Linux gvim package, it will give
you a GUI running on X, which would require you to run an X server (e.g.
Xming or VcXsrv) on Windows as well. That would give you access to the
Linux files, and to Windows-side files through /mnt/c and the like. Note
that I'm not sure what kinds of caveats exist for accessing /mnt/c from
Linux.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Modern Vim

[Eric Christopherson]

On Sun, Nov 5, 2017 at 12:04 AM, 'Grant Taylor' via vim_use <
vim_use@googlegroups.com> wrote:

> On 11/04/2017 07:50 AM, Phil Dobbin wrote:
>
>> I recently bought a copy of Drew Neil's 'Modern Vim':
>>
>
> I've been eyeing "Modern Vim".
>
> From reading through it (a cursory glance it has to be said) it seems well
>> written & covers Vim 8 & NeoVim also.
>>
>
> I've been quite happy with all of Drew's material that I've looked at,
> including "Mastering Vim" and "Vim Casts".


I'm guessing you mean _Practical Vim_.


>
>
> At this point I have to say of course that I have no affiliation with the
>> author or the publishers at all, yada, yada, yada.
>>
>
> Likewise.  ;-)
>
>
>
> --
> Grant. . . .
> unix || die
>
>
> --
> --
> 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+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Cursor isn't at right position for Commit message

[Eric Christopherson]

On Sun, Jun 04, 2017, Kaartic Sivaraam wrote:
> Hello all,
> 
> I am currently using Vim 8.0. When I use vim as my preferred editor for
> git. 
> 
> When I try to commit a change in git it open up vim to type the commit
> message. Most of the time the text cursor seems to be positioned
> somewhere in the middle of the commit template (the comments). As a
> result, I am unable to type in the commit message directly after
> switching to "insert" mode in vim. Any reasons for this misbehaviour ?
> 
> Environments:
> Operating System: Debian GNU/Linux 9 (stretch)
> Shell: bash
> 
> --
> Regards,
> Kaartic Sivaraam <kaarticsivaraam91...@gmail.com>

Do you have an autocmd to resume the last position in a file when
opening that file later? I had one like that (I forget where I copied it
from), which I eventually modified to exclude gitcommit files. See the
solutions at
https://stackoverflow.com/questions/2393671/vim-restores-cursor-position-exclude-special-files
.

> 
> -- 
> -- 
> 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+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Vim maximise weirdness

[Eric Christopherson]

On Tue, Mar 14, 2017 at 10:05 PM, Ken Takata <ktakata65...@gmail.com> wrote:

> Hi,
>
> 2017/3/15 Wed 0:33:25 UTC+9 Eric Christopherson wrote:
> > On Tue, Mar 14, 2017 at 5:07 AM, A. S. Budden <abu...@gmail.com> wrote:
> >
> > With the newly compiled version of vim (details below), `:simalt ~x`
> >
> > doesn't do quite what I was expecting: the window gets bigger but the
> >
> > drawn area doesn't - https://snag.gy/3VfqUe.jpg
> > How interesting -- for me, :simalt ~x works, but actually pressing
>  doesn't bring down the menu. I have to define a mapping for it
> to work:
> >
> >
> > :nnoremap  :simalt ~
> > :inoremap  :simalt ~
>
> I confirmed that `:simalt ~x` worked fine on v8.0.0274.
> However, on v8.0.0275, `:simalt ~x` makes the window maximized but the
> contents is not properly updated. I need to hit Ctrl-L to update the
> contents.
>
> Alt-Space doesn't work on neither 0274 nor 0275.
>
> Regards,
> Ken Takata
>
>
I see that I was incorrect about alt-space-based maximizing working for me;
it does maximize the window, but much of the resulting window has a gray
background with no text in it. Ctrl-L causes it to redraw and take up the
whole space, as stated by others.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Vim maximise weirdness

[Eric Christopherson]

On Tue, Mar 14, 2017 at 5:07 AM, A. S. Budden <abud...@gmail.com> wrote:

> With the newly compiled version of vim (details below), `:simalt ~x`
> doesn't do quite what I was expecting: the window gets bigger but the
> drawn area doesn't - https://snag.gy/3VfqUe.jpg
>

How interesting -- for me, :simalt ~x works, but actually pressing
 doesn't bring down the menu. I have to define a mapping for it
to work:

:nnoremap  :simalt ~
:inoremap  :simalt ~

I can't remember exactly where I got my Vim binary, but the top of its :ver
command shows:

VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Feb  1 2017 23:55:18)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-295
Compiled by appveyor@APPVYR-WIN
Huge version with GUI.  Features included (+) or not (-):

Although I have to say I've had the same problem with physically pressing
 also in several releases of Vim 7.3, and I think in several
different Windows builds.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Compile and Run Java Projects

[Eric Christopherson]

On Mon, Oct 17, 2016, Luis Henriquez-Perez wrote:
> On Monday, October 17, 2016 at 6:08:35 PM UTC-4, Luis Henriquez-Perez wrote:
> > I am using vim to code my java projects. I've been noticing I've been 
> > jumping back to the terminal a lot to compile and run my code. So I want to 
> > create a function that does all this for me (and gets rid of the class 
> > files afterwards). The code below is my attempt. Could someone let me know 
> > how I can fix my code?
> > 
> > func! CompileFolderJava()
> > 
> > " compile all java files in folder of the current buffer
> > :!javac "%:p:h" . "/*.java"   "  javac 
> > path/name/to/current/buffer/directory/*.java
> > 
> > 
> > " run Main java file in that folder
> > :!java "%:p:h" . ".Main"" java 
> > path/name/to/current/buffer/directory.Main
> > 
> > " delete all the .class files in that folder
> > :!rm "%:p:h" . ".class"
> > 
> > " :echo "Done"
> > endfunc
> 
> The solution of  " :!java -cp %:p:h Main"  did not work out. 
> 
> I think this might be because my java files all have the following line:
> Package myjavafiles;
> 
> as of yet the only way I've found to compile and run it from the terminal 
> (and not from vim)
> is by being in the parent directory of myjavafiles and doing:
> 
> javac myjavafiles/*.java
> java myjavafiles.Main
> 
> I've found that I can specify the directory of the java files I want to 
> compile in the "javac" command. But when the "java" command will only work 
> when I'm in the directory that has the folder of java files. 
> 
> I came to this conclusion after doing the following in vim from myjavafiles 
> directory:
> 
> // succesful
> : cd ..
> : !javac myjavafiles/*.java
> : !java myjavafiles.Main
> 
> // not successful
> : !javac *.java  <---worked
> : !java Main <did not work
> 
> // suprisingly not successful
> : cd ..
> : !javac myjavafiles/*.java
> : !java ~/path/to/myjavafiles.Main
> 
> Because of these tests I think that perhaps I need to change directories to 
> compile. But I'm not sure how to get only the folder name "myjavafiles" 
> instead of the whole path. 

Try %:p:h:t to get just 'myjavafiles'.

The help for %'s modifiers is can be accessed at :help
filename-modifiers.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Compile and Run Java Projects

[Eric Christopherson]

On Mon, Oct 17, 2016, Luis Henriquez-Perez wrote:
> On Monday, October 17, 2016 at 6:08:35 PM UTC-4, Luis Henriquez-Perez wrote:
> > I am using vim to code my java projects. I've been noticing I've been 
> > jumping back to the terminal a lot to compile and run my code. So I want to 
> > create a function that does all this for me (and gets rid of the class 
> > files afterwards). The code below is my attempt. Could someone let me know 
> > how I can fix my code?
> > 
> > func! CompileFolderJava()
> > 
> > " compile all java files in folder of the current buffer
> > :!javac "%:p:h" . "/*.java"   "  javac 
> > path/name/to/current/buffer/directory/*.java
> > 
> > 
> > " run Main java file in that folder
> > :!java "%:p:h" . ".Main"" java 
> > path/name/to/current/buffer/directory.Main
> > 
> > " delete all the .class files in that folder
> > :!rm "%:p:h" . ".class"
> > 
> > " :echo "Done"
> > endfunc
> 
> I managed to get the compiling and the removing to work. For running, I think 
> I have to be in the parent directory of the file. The format needs to be: 
> java ParentDir.Main

Well, what's going wrong with it? I would suggest, though, that instead
of changing directories you use the classpath (-cp) option to tell Java
where to find the Main class. E.g.

:!java -cp %:p:h Main

> 
> func! CompileFolderJava()
>   " compile all java files in folder
>   :!javac %:p:h/*.java
> 
>   " a java thing I have to be in this directory to call java main
>   :cd ..
>   " run all the java files in folder
>   :!java %:h.Main
> 
>   " delete all the .class files in folder
>   :!rm %:p:h/*.class
> 
>   " :echo "hello"
> endfunc

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to input character 'ƒ' (U+0192)

[Eric Christopherson]

On Sat, Oct 08, 2016, Steve wrote:
> Hi Linda,
> 
> diphraphs are what you are looking for.
> 
> Type :h digraphs or simply :digraphs for a comprehensive list.
> 
> for some usefull information.
> 
> I would type km3 to get ϝ.

That's a different character. I don't see that Vim has a predefined
digraph for LATIN SMALL LETTER F WITH HOOK.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Vim 8 64-bit for windows 10? -> run 32bit

[Eric Christopherson]

On Wed, Sep 14, 2016 at 9:17 AM, boB Stepp <robertvst...@gmail.com> wrote:

> On Tue, Sep 13, 2016 at 10:25 PM, Eric Christopherson
> <echristopher...@gmail.com> wrote:
> > On Wed, Sep 14, 2016, Sven Guckes wrote:
> >> * boB Stepp <robertvst...@gmail.com> [2016-09-14 04:36]:
> >> > I tried the link given in the announcement, but this installed a
> >> > 32-bit version of Vim 8.0.2.  Where can I find the 64-bit version?
> >>
> >>   http://www.vim.org/download.php#pc
> >>   Win64
> >>   The 32-bit version of Vim runs fine on 64-bit windows.
> >>   There was a 64-bit binary, but it
> >>   wasn't used much and maintenance stopped.
> >
> > I may be misremembering, but wasn't there some problem with creating an
> > "Edit in Vim" Explorer context menu entry when the bits of Explorer
> > don't match those of Vim?
> >
> On a similar note, the reason I was looking for 64-bit Vim, is that I
> believe I previously had problems with Python within Vim when I tried
> to use my normal installation of 64-bit Python.  I had been getting
> 64-bit Vim from
> https://bintray.com/veegee/generic/vim_x64/#
> but there currently is no build for Vim 8.
>

Is there a list of the known third-party Vim builds online?

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Vim 8 64-bit for windows 10? -> run 32bit

[Eric Christopherson]

On Wed, Sep 14, 2016, Sven Guckes wrote:
> * boB Stepp <robertvst...@gmail.com> [2016-09-14 04:36]:
> > I tried the link given in the announcement, but this installed a
> > 32-bit version of Vim 8.0.2.  Where can I find the 64-bit version?
> 
>   http://www.vim.org/download.php#pc
>   Win64
>   The 32-bit version of Vim runs fine on 64-bit windows.
>   There was a 64-bit binary, but it
>   wasn't used much and maintenance stopped.

I may be misremembering, but wasn't there some problem with creating an
"Edit in Vim" Explorer context menu entry when the bits of Explorer
don't match those of Vim?

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Question born from pure curiosity...

[Eric Christopherson]

On Sun, Jul 31, 2016, Nikolay Aleksandrovich Pavlov wrote:
> 2016-07-31 16:00 GMT+03:00 Nikolay Aleksandrovich Pavlov <zyx@gmail.com>:
> > 2016-07-31 10:31 GMT+03:00  <meino.cra...@gmx.de>:
> >> Hi,
> >>
> >> this NOT meant as implicit or explicit critism, complain
> >> or what else...
> >>
> >> Its just interest in vim and driven by curiosity... :)
> >>
> >> To set an option or feature inside vim one do
> >>
> >> : set =
> >>
> >> But why it is
> >>
> >> :colorscheme 
> >
> > :colorscheme is *not* an option. It is a shortcut to `runtime
> > colors/.vim` with some more work (e.g. `doautocmd ColorScheme
> > ` or dealing with g:colors_name).
> 
> I would rather ask why  or  are options: setting them
> does similar things as :colorscheme or :compiler (note: this is also
> not an option).

And then there's :set filestype vs. :setfiletype.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: vim: keep undo when moving a file?

[Eric Christopherson]

On Tue, Jul 05, 2016, ping song wrote:
> I have a file that I keep using for quite a long while, it's convenient to
> keep the editing history forever, so if something gone wrong I can always
> undo back and locate the issue.
> 
> today I moved the file to another folder and all undo history gone.
> I tried to rename my original undo file according to the new location , but
> still not work...
> anyone has a good solution?

I just realized that a plugin I enjoy using, vim-eunuch, does allow the
history to be saved when you move or rename files. It defines a handful
of ex commands for Unix-like file operations; the ones I'm talking about
are of the form

:Rename newname

and 

:Move newfolder

(you run those while you have the file open and it moves it in place).

-- 
    Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: vim: keep undo when moving a file?

[Eric Christopherson]

On Tue, Jul 05, 2016, ping song wrote:
> I have a file that I keep using for quite a long while, it's convenient to
> keep the editing history forever, so if something gone wrong I can always
> undo back and locate the issue.
> 
> today I moved the file to another folder and all undo history gone.
> I tried to rename my original undo file according to the new location , but
> still not work...
> anyone has a good solution?

I would love to see that.

-- 
    Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Vim is too clever for me

[Eric Christopherson]

On Mon, May 23, 2016, Mikołaj Machowski wrote:
> Dnia Poniedziałek, 23 Maja 2016 10:44 Michał Urban 
> <motivaproducti...@gmail.com> napisał(a) 
> > Hi,
> > 
> > If I write quotation mark " and then press "o" (new line) then I've got the 
> > same quotation mark on the new line. How to disable it? The same behavior I 
> > noticed when pasting text from clipboard.
> > 
> 
> :help formatoptions
> :help fo-table

Also, when pasting text into Vim in a terminal, it's best not to just
use the terminal's paste capability because, as you saw, sometimes Vim
tries to do clever things with the pasted text. Besides continuation of
comment characters, it can try to keep existing indentation, and
probably some other things I can't think of, which in my experience is
often unwanted when I'm pasting. So, if you're using a version of
terminal Vim with GUI integration (e.g. vim-gnome under X11, MacVim
under OS X; I think it's just sort of standard in Windows Vim), learn
the use of the clipboard register "+. You can paste using "+gP.

Another way to do it, which works even if your Vim has no GUI
integration, is to use the pastetoggle functionality. You set up a
certain key to put Vim into paste mode, which makes it ignore most of
its clever insert-mode behaviors (and input mode key mappings too).
Press that key once, paste, and then press it again. It works in insert
or normal mode. Since insert-mode mappings are disabled in paste mode,
it's best to set the toggle key using :set pastetoggle instead of :imap.

See:
  :h "+
  :h 'paste'
  :h 'pastetoggle'

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Reproducible issue reading large registry file

[Eric Christopherson]

On Fri, May 20, 2016, Eric Christopherson wrote:
> On Thu, May 19, 2016, 'Suresh Govindachar' via vim_use wrote:
> > 
> > Steps to reproduce issue:
> > 
> > System:  Windows 7 64 bit
> > 
> > Gvim:  VIM - Vi IMproved 7.4 (2013 Aug 10,
> >  compiled Jan  2 2016 14:36:11)
> >MS-Windows 32-bit GUI version with OLE support
> >Included patches: 1-1023
> >Compiled by mool@tororo
> >Big version with GUI.
> > 
> > 1) Export entire registry to file (in my case, about 500 MBytes)
> 
> How are you exporting it? From within regedit's GUI? Or by invoking
> regedit on the command line?
> 
> > 
> > 2) gvim.exe -u NONE -U NONE --noplugin all_reg.reg
> > 
> > 3) takes some time and then get message just before file shows up
> > 
> > 4) Observe message before file shows up: "all_reg.reg" [Incomplete last
> > line][unix format] 3912091 lines, 523120802 characters
> > Press ENTER or type command to continue
> > 
> > 5) Hit enter
> > 
> > 6) Observe contents of buffer:
> > 
> > ÿ[with two dots on the top of it]þ[funny looking p]W^@i^@n^@d^@o^@w^@s
> > 
> > [more such triples:  @^]
> > 
> > 7) Open all_reg.reg in notepad++:  no issues, file opens very quickly, text
> > is clearly seen.
> > 
> > Please look into this.
> 
> As Tim said, this looks just like a UTF-16 file (specifically
> little-endian, with a BOM) being opened as if it were in another
> encoding. The only weird things to me are that it's in Unix format
> instead of DOS (=Windows), and it has "Incomplete last line".  I've been
> successful at turning a registry text file into one such as you
> describe, but it only seems to happen if I resave the file from within
> Vim, and it probably depends on a few options being set. When I open a
> registry text file from Vim before I've modified the file at all, it
> opens correctly.
> 
> Try this -- a small elaboration on what Tim said:
> After opening the file, issue:
> :e ++enc=utf-16le ++ff=dos
> 
> Or you can do it from the command line with
> vim ++enc=utf-16le ++ff=dos all_reg.reg

Sorry, I messed that up. It should be:
vim -c '++enc=utf-16le ++ff=dos all_reg.reg'

> 
> The only difference from Tim's recommendation is that we're telling it
> to use DOS line endings, since it seems to incorrectly pick Unix ones.

Another correction: this also differs from Tim's in that it specifies
specifically little-endian UTF-16.

> (Then again, maybe you accidentally saved the file from within Vim and
> thereby caused it to save with Unix line endings, in which case leave
> off the ++ff=dos part.)
> 
> -- 
> Eric Christopherson

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Reproducible issue reading large registry file

[Eric Christopherson]

On Thu, May 19, 2016, 'Suresh Govindachar' via vim_use wrote:
> 
> Steps to reproduce issue:
> 
> System:  Windows 7 64 bit
> 
> Gvim:  VIM - Vi IMproved 7.4 (2013 Aug 10,
>  compiled Jan  2 2016 14:36:11)
>MS-Windows 32-bit GUI version with OLE support
>Included patches: 1-1023
>Compiled by mool@tororo
>Big version with GUI.
> 
> 1) Export entire registry to file (in my case, about 500 MBytes)

How are you exporting it? From within regedit's GUI? Or by invoking
regedit on the command line?

> 
> 2) gvim.exe -u NONE -U NONE --noplugin all_reg.reg
> 
> 3) takes some time and then get message just before file shows up
> 
> 4) Observe message before file shows up: "all_reg.reg" [Incomplete last
> line][unix format] 3912091 lines, 523120802 characters
> Press ENTER or type command to continue
> 
> 5) Hit enter
> 
> 6) Observe contents of buffer:
> 
> ÿ[with two dots on the top of it]þ[funny looking p]W^@i^@n^@d^@o^@w^@s
> 
> [more such triples:  @^]
> 
> 7) Open all_reg.reg in notepad++:  no issues, file opens very quickly, text
> is clearly seen.
> 
> Please look into this.

As Tim said, this looks just like a UTF-16 file (specifically
little-endian, with a BOM) being opened as if it were in another
encoding. The only weird things to me are that it's in Unix format
instead of DOS (=Windows), and it has "Incomplete last line".  I've been
successful at turning a registry text file into one such as you
describe, but it only seems to happen if I resave the file from within
Vim, and it probably depends on a few options being set. When I open a
registry text file from Vim before I've modified the file at all, it
opens correctly.

Try this -- a small elaboration on what Tim said:
After opening the file, issue:
:e ++enc=utf-16le ++ff=dos

Or you can do it from the command line with
vim ++enc=utf-16le ++ff=dos all_reg.reg

The only difference from Tim's recommendation is that we're telling it
to use DOS line endings, since it seems to incorrectly pick Unix ones.
(Then again, maybe you accidentally saved the file from within Vim and
thereby caused it to save with Unix line endings, in which case leave
off the ++ff=dos part.)

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Vim and gpg

[Eric Christopherson]

On Mon, May 16, 2016 at 8:18 AM, Mario D  wrote:

> > As a workaround (without forcing term=builtin_ansi), do you have any
> > success if you hit backspace a bunch of times at the password prompt,
> > before you start typing the password?
>
> Yes: this works. If I remove forcing the term and I hit backspace a few
> times, then I can edit the file properly.
>
> I really would like to understand why this happens: it looks like there is
> a reason but I am not able to guess it.
>
> It doesn't seem to depend on my settings: I created a brand new user
> without any prior custom setting and it is the same behaviour.
>

Does it happen when you run Vim in a terminal? Which terminal(s)? Try a few
to narrow it down.

I'm guessing the 16.04 upgrade introduced a new behavior (bug) in the
terminal you use.

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Combinations with CTRL key don't work on Mac. Do you have the same problem?

[Eric Christopherson]

On Thu, May 12, 2016, Frosty Frosty wrote:
> Combinations like Ctrl + [ , Ctrl + W (work with windows) or Ctrl + U, Сtrl + 
> D e.t.c. don't work for El Capitan and MacVim 7.4. Do you have the same 
> problem or this is only my system bug?

It's not true on mine. Do you have Ctrl remapped to something else? Does
Ctrl work in terminal apps (either Vim or other)?

-- 
    Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Vim can't recognize text file, but Notepad++ can

[Eric Christopherson]

On Sun, May 15, 2016, Tim Chase wrote:
> On 2016-05-15 19:08, 'Suresh Govindachar' via vim_use wrote:
> > I exported the entire Windows registry -- resulting text file is
> > about 500 MBytes.  I can open this text file in Notepad++ -- but
> > opening it in Vim results in just tons of @ signs.
> 
> Does the content alternate between "@" signs and actual content
> characters?  It sounds suspiciously like a UTF-16 file (Windows likes
> to call this "Unicode") that Vim is reading yet somehow
> misinterpreting.  Is your vimrc trying to set the 'encoding' or
> 'fileencoding' settings in an incongruous way?
> 
> You might try
> 
>   :e ++enc=utf16 file.txt
> 
> to force Vim to use utf16 to open the file.  It would also help to
> know what vim outputs when you issue
> 
>   :set encoding? fileencodings?

I'm actually thinking the @ signs are the ones used by Vim when there
isn't enough space on the screen to completely fit one or more logical
lines of text in the file. I wouldn't expect that to happen with a
registry *text* file, though.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Vim and gpg

[Eric Christopherson]

On Sun, May 15, 2016, Mario D wrote:
> 
> > You might try with a different terminal or trying, if any of those settings 
> > circumvents this problem
> > 
> > :set term=builtin_ansi
> > :set t_RV=
> > :set t_u7=
> > 
> 
> Yes: the first setting seems to do the job.
> I added the line
> 
> autocmd BufReadPre,FileReadPre  *.asc,*.gpg set term=builtin_ansi
> 
> in my .vimrc and everything seems to work nicely. Sure, this way I am stick 
> to a somewhat primitive set of colors for syntax highlighting while editing 
> encrypted files, but I can cope with this :)

As a workaround (without forcing term=builtin_ansi), do you have any
success if you hit backspace a bunch of times at the password prompt,
before you start typing the password?


-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: vim doesn't read ~/.vim

[Eric Christopherson]

On Mon, May 09, 2016, Gary Johnson wrote:
> On 2016-05-09, Bob Holtzman wrote:
> > On Mon, May 09, 2016 at 02:46:57PM -0400, Charles E Campbell wrote:
> > > Nikolay Aleksandrovich Pavlov wrote:
> > > > 2016-05-09 19:52 GMT+03:00 sinbad:
> > > >> vim is not reading the scripts present in ~/.vim folder.
> > > > It is not supposed to read them. Automatically read are scripts in
> > > > ~/.vim/plugin assuming you have not disabled this in one way or the
> > > > other.
> > > >
> > > > In any case you are missing critical details: vimrc, how you run Vim,
> > > > what scripts do you mean.
> > > >
> > > >> the following is the version.
> > > >>
> > > >> VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jan  2 2014 19:39:32)
> > > >>
> > > More details, please: vim --version .  Does it, for example, have +eval
> > > or not?
> > 
> > The version was plainly stated in th original post.
> 
> I think Dr. C. meant the rest of the output of 'vim --version',
> including the features it was compiled with.
> 
> We really do need more information from the OP such as:  what
> scripts are not being read, where did you put them, and what makes
> you think they're not being read.
>   
> http://www.catb.org/esr/faqs/smart-questions.html

And if it's Windows, it would be in %USERPROFILE%/vimfiles instead of
~/.vim, I believe.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: RFE: support POSIX standard and developing RE's

[Eric Christopherson]

On Tue, Apr 12, 2016 at 12:45 PM, L. A. Walsh  wrote:

> Christian Brabandt wrote:
>
> There is https://github.com/vim/vim/issues/99
> You might want to check, if this works for you.
>
>
> 
> If vim supported posix extended RE's, then, like, say grep,
> it could also support Perl RE's, from the PCRE library.  Perl supports
> the "/x" to ignore whitespace for readability.  I.e. the author was saying
> they wanted to implement some flavor of PCRE's, but really wanted the "/x"
> feature, which would have been alot easier to do from Vim's current
> feature set.
>
> If Vim could _at least_ support extended 'RE's, and if it was done
> in a modular fashion, then it seems adding other 'RE' engines would be
> easier.  Note, I don't know about current benchmarks, but PCRE was the
> fastest 'RE' engine out of any of the standard 'RE' engines as well, by
> far, the most expressive.  Perl even bent over backwards to implement
> Python-RE specific features to make it easy to port Python-RE's along
> with all the POSIX RE's.
>
> -
> BPJ wrote:
>
> There is https://github.com/vim/vim/issues/99
>> You might want to check, if this works for you.
>
>
> If I'm not mistaken that's "extended" as in /x,  a different sense from
> "extended" as in ERE.
>
> i would like to have "extended as in /x" FWIW.
>
> If vim could include the PCRE engine (then you'd have this automatically).
> And you are right "/x" is not the same as POSIX extended RE's, but is the
> same as PCRE's "/x" switch.
>

Just FYI:

The name Perl-Compatible Regular Expressions is a misnomer. PCRE is not
strictly Perl-compatible (and I'm guessing Perl doesn't deal 100%
appropriately when fed PCRE either, although it has picked up at least some
of PCRE's extensions). It's not part of the Perl project.

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Packages

[Eric Christopherson]

On Mon, Mar 07, 2016, Nikolay Aleksandrovich Pavlov wrote:
> Without isolated namespaces this is absolutely useless behaviour. If A
> depends on B, C depends on B and D does not depend on anything and
> plugin manager created packages (A,B1), (C,B2) and (D) then out of B1
> and B2 there will be only one used, whatever was found first (or last
> or first with errors from last, depending on how plugins and plugin
> manager are written). On the other hand creating package (A,B,C) and
> (D) if B is a library, A and D are filetype plugins and C is a
> universal linter would be rather strange choice, also where plugin
> manager is going to pull a package name from? Not to mention what is
> needed to be done if a plugin E is added that depends on D and B?
> Moving plugins around without an explicit reason is not fine.
> 
> So if plugin manager is using packages it will create one package
> containing all plugins. Maybe additionally a user-defined packages
> that are needed to group plugins loaded at request by user when it is
> needed to load at one request more then one plugin, without “grouping
> by dependencies” nonsense.

I think it would be nice -- but plugins and VimL would have to be
heavily modified -- if things worked much like npm packages. I.e. each
plugin could have a tree of dependencies inside it, and it would only
recognize the particular versions bundled inside. Likewise, other
plugins outside its tree would not see its bundled plugins.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Packages

[Eric Christopherson]

On Sun, Mar 06, 2016, Benjamin Fritz wrote:
[in attachment]
> +directory under your package, whereas plugins you enable on demand go in an
> +"opt" directory so that |:packadd| can find them. See |pack-add| below.

OK, I see that the intended semantics of the word "ever" is as a synonym
of "always". I wasn't clear on that.

I would strongly advise using "always" instead. "Ever" in modern English
is a negative-polarity word, which means you can't say "Vim should
_ever_ load this plugin". You're limited to stating a negative ("Vim
shouldn't ever...") or positing a conditional ("if Vim should ever...")
or asking a question ("should Vim ever...?"), and maybe a few other uses
I can't think of right now.

"Vim should _always_ load this plugin" is fine.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Packages

[Eric Christopherson]

On Fri, Mar 04, 2016, Matthew Desjardins wrote:
> On Friday, March 4, 2016 at 12:37:08 PM UTC-5, Bram Moolenaar wrote:
> > It does add the extra directory level, so that groups of plugins can be
> > installed together.  Some installed always, some optionally (or when
> > needed or when specific features are present, e.g. Python).
> > 
> > This does make it a bit more complicated, but the docs have the one
> > extra command to do it:
> > % mkdir -p ~/.vim/pack/my/ever/always
> > % cd ~/.vim/pack/my/ever/always
> > % unzip /tmp/myplugin.zip

Is there semantic significance to the names "my" and "ever" and
"always"? Or are these arbitrary example directory names?

If they are meaningful, what is the reason for those particular names?

> 
> No, the problem that makes it more complicated is that if non-plugins are 
> treated differently, users now have to know that they have to add some lines 
> to their vimrc to get it to load.  It's a fairly meaningless distinction that 
> the user doesn't care about.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: outdenting in visual block mode

[Eric Christopherson]

On Sat, Feb 27, 2016, Brian Feeny wrote:
> I am trying to outdent in visual block mode (Ctrl-V), but when I press < it 
> doesn't outdent.  when I press > it properly indents.  I am fairly new to 
> VIM.  Here is my .vimrc, I am wondering if something could be interfering 
> with <

Does it outdent after a certain timeout? Or not at all? I used to have
the former problem; it turned out I had a mapping starting with < (which
was intended to be a special thing like  or the like; not literally
a less-than sign followed by whatever). I don't see that in your .vimrc,
though.

-- 
    Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Temporarily stop sending T_SI/t_SR/t_EI?

[Eric Christopherson]

I'm interested in having Vim stop sending the cursor-shape-change
sequences temporarily, e.g. when using a plugin that enters and exits
normal mode behind the scenes.

>   t_SIstart insert mode (bar cursor shape)*t_SI* *'t_SI'*
>   t_SRstart replace mode (underline cursor shape) *t_SR* *'t_SR'*
>   t_EIend insert or replace mode (block cursor shape) *t_EI* *'t_EI'*

Is there a better way to arrange this than to have each guilty plugin
have code to temporarily unset t_SI/t_SR/t_EI when it's about to switch
modes and reset it later?

-- 
    Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: List of potential insert mode control character mappings?

[Eric Christopherson]

On Feb 22, 2016 1:38 PM, "Josef Fortier"  wrote:
>
> Just some followup on my original request for consensus advice on what
insert mode mappings could be reasonably available. Some (at least
tentative) conclusions:
>
> There aren't really any non-mapped insert mode control characters, which
means "stealing" and re- purposing existing mappings.
>
> SAFE
>
>  is the most common candidate. It's NewLine, as opposed to
C-M/Return, something that's almost never actually typed. It's also
something that would lend itself to overloading, i.e. remap to add
functionality and also return . And, importantly it's easy to hit.
>
>  is almost certainly usefully re-purposed. It's original purpose, to
aid using vim in an "always insert" mode is almost always going to be
unused.
>
>   likewise are intended for insertmode.
>
> REASONABLE
>
>  (or ) This is mapped to switch keyboards, a use case I'm not
all that familiar with. But I suspect even in an alternate keyboard
situation it's reasonable to give up a hot key and instead map the
functionality to a command. This doesn't seem that useful off the top
(undescore is typically awkward to type which effects the primary use case
for insert mode mappings) but... it turns out that all the terminal
environments I've tested map  to  which makes this mapping *much*
more useful. Question mark is prime 101 keyboard territory (as opposed to
underscore).

 is even more conveniently provided by , at least on US
keyboards. (I'm sort of surprised that  doesn't do the same as DEL,
since often that's notated as  or <^?>.)

>
> REASONABLE WITH QUALIFICATIONS
>
>  These are all intended to adjust indentation on the fly.
It could be argued that normal mode are almost always the way to do this.
But there is also a large degree of overlap here. For the most common use
case scenario, adjusting pasted in text,  most likely is all that's
really needed (YMMV).

I personally use / when for whatever reason indentation isn't set
up right after I hit enter. That probably should be done in normal mode,
but it's convenient to have it in insert mode, sort of like the arrow keys.

>
>  are terminal flow control. They're really only useful if your
terminal is set to ignore flow control (a very reasonable step, but not one
that's done by default).

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: 'f','t','F','T' til word/regex instead of char

[Eric Christopherson]

On Tue, Feb 02, 2016, meino.cra...@gmx.de wrote:
> 
> Hi,
> 
> with the movements f,F,t,T one can determine a certain point in a
> line, at which a movement of the cursor should end.
> This point is given by a single character.
> 
> Is it possible to specifiy a regex or string instead of a single
> character for the same purpose without makeing a akademic adventure 
> from it ? :) :)) ;)))
> 
> (or am I a little blinded by the bright light of vim? :)

You can use /foo as a motion; the motion will be taken up to just before
the start of the matched text. ?foo as a motion goes backward to the
beginning of the matched text. I wish there were ways to duplicate the
tT/fF distinction in those cases.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can you edit EBCDIC files on non-OS390 builds of VIM?

[Eric Christopherson]

On Sat, Jan 30, 2016, Justin Dearing wrote:
> I'd like to edit EBCDIC encoded files in VIM on windows vim --version shows 
> this:
> 
> VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Sep 16 2015 08:44:57)
> Included patches: 1-872
> Compiled by <alex...@gmail.com>
> Huge version without GUI.  Features included (+) or not (-):
> 
> -ebcdic  +mouse   +smartindent -xim
> 
> 
> I cloned the git repo and configure --enable-ebcdic was not an option.
> Looking at src/auto/configure, it looks like ebcdic support is enabled
> if ASCII support is not present. Is there an option to turn it on?

Sorry, I don't know the answer to that, but I find it interesting to see
this question, just a few days after reading a page laying out the case
for NeoVim -- although I can't find the exact page now, I believe it
gave EBCDIC support as an example of something that no one would ever
use Vim for!

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: feature work in console vim , but not over ssh

[Eric Christopherson]

On Tue, Jan 19, 2016 at 9:25 PM, ping song <songpingem...@gmail.com> wrote:

> + vim group...
>
> anyone has any idea, of why same feature works in console vim, but not in
> console vim over ssh?
>
> regards
> ping
>

I'm not sure what terminals you two are using, but in all the Unix
terminals I've used, Shift is the key used to prevent mouse clicks on the
terminal from being transmitted *at all* to the program running within it.
This might be modifiable in some of the terminals, but I've never done so.

Or does shift+click/drag work locally but not over SSH?


>
> -- Forwarded message --
> From: Charles Campbell <charles.e.campb...@nasa.gov>
> Date: Tue, Jan 19, 2016 at 11:23 AM
> Subject: Re: vim drawit vs. http://asciiflow.com/#Draw
> To: ping <songpingem...@gmail.com>
>
>
> ping wrote:
> > On Friday, April 11, 2014 at 10:47:56 AM UTC-4, Charles Campbell wrote:
> >> ping song wrote:
> >>> hi Dr. Chip:
> >>> I'm a big fan of your Drawit plugin (thanks!).
> >>> today I hear of asciiflow.com/#Draw <http://asciiflow.com/#Draw>, it
> >>> looks surprisingly nice too.
> >>> I guess it's not possible to have the similiar ability in vim?
> >>>
> >> I just glanced at asciiflow.  What is it that you want that DrawIt
> >> doesn't have?  The only thing I saw was the ability to "grab a line (or
> >> box)" and resize it.  I think that would entail having DrawIt remember
> >> hotspots on each drawing activity so that they could be "grabbed" and
> >> redone.
> >>
> >> Regards,
> >> Chip Campbell
> > Hi Dr. Chip:
> >
> > I just tried drawit new features of "drag and draw" and I found some
> issues:
> >
> > the shift-mouse seems doesn't work for me. I'm on console vim over ssh.
> >
> > I press shift and then left mouse, then move the mouse, nothing happens.
> >
> > did I miss anything?
> >
> > the "left mouse " to select region and "ctrl+left mouse" to drag and
> move a selection works fine.
> >
> Terminals can be obstreperous.  I just tried
>
> ssh [hostname]
> vim -u NONE testmouse.vim
> :so %
>
> and I, too, see that  does not work.  This seems to be a
> vim+ssh problem, though -- the testmouse.vim script knows nothing about
> DrawIt, for example.
>
> I'm afraid that I don't know the answer to how to get
> vim+ssh+shift-leftmouse working, though.
>
> 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 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+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: There is a mistake in my « makefile »

[Eric Christopherson]

On Jul 27, 2015 12:49 AM, aubertin.sylvain aubertin.sylv...@sfr.fr
wrote:

 Le vendredi 24 juillet 2015 07:59:40 UTC+2, aubertin.sylvain a écrit :
  I am a beginner, in vim. Something is wrong in my makefile. At the end
of my shell, when I type  :makeit works well. All my shell is compiled.
But no trace of the object file, named essai.o
 My source file is essai. Somewhere « make » or « /bin/bash »  says
to me : cyclic permutation is no correct. That is something I don't
understand.
I should like to save my object file. Shall I use « sudo make
install » or « sudo essai.o install » ? ?
  For installing must I use commands put inside the makefile or am I
forced to do that in second time, out of my makefile ? ?  Here is my
makefile :
  # indiquer quel compilateur utiliser
  #!/bin/bash
  #makefile
  all: essai.o
  essai.o: essai
/bin/bash essai -o essai.o
  My OS is : xubuntu 14.4.1 My vim version is 7.4. 52  My PC is hp Mini
110 1100
  THANKS A LOT TO ALL MY REPLIERS
 I do all that in order to learn how it works. Compiling shells is good
for the secrets. Please,if you know well makefiles, tell me if this one
seems good to you. I'll try that once I installed my shell compiler.
 #makefile
 all: essai.o
 essai.o: essai
 compiler essai essai.o
 MANY THANKS

The web page whose address you posted was clear about how to invoke shc.
Please refer back to it, and then try the command in the shell (and by that
I mean *not* inside of Vim or in a makefile) until you're comfortable with
how it works.

Then see if you can apply that knowledge in a makefile. You have a good
start already; but you might want to consult a makefile tutorial.

When you have it working so you can just type `make` on the command line,
the :make command in Vim should also work. This really is all about general
commands line/shell usage and not about Vim at all.

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: There is a mistake in my « makefile »

[Eric Christopherson]

On Fri, Jul 24, 2015 at 12:59 AM, aubertin.sylvain
aubertin.sylv...@sfr.fr wrote:
 I am a beginner, in vim. Something is wrong in my makefile. At the end of my 
 shell, when I type  :makeit works well. All my shell is compiled. But no 
 trace of the object file, named essai.o
My source file is essai. Somewhere « make » or « /bin/bash »  says to me : 
 cyclic permutation is no correct. That is something I don't understand.
   I should like to save my object file. Shall I use « sudo make install » or 
 « sudo essai.o install » ? ?
 For installing must I use commands put inside the makefile or am I forced to 
 do that in second time, out of my makefile ? ?  Here is my makefile :
 # indiquer quel compilateur utiliser
 #!/bin/bash
 #makefile
 all: essai.o
 essai.o: essai
 /bin/bash essai -o essai.o
 My OS is : xubuntu 14.4.1 My vim version is 7.4. 52  My PC is hp Mini 110 1100
 THANKS A LOT TO ALL MY REPLIERS

I don't think this is Vim-related, but you can find out by just
executing make from the command line outside of Vim. Really there's no
way of knowing what the problem is without seeing the essai file. The
way your makefile is written, bash runs essai, and essai needs to
understand how to process `-o essai.o` itself.

I'm wondering if there's been a mixup; if you're using a makefile
anyway, I don't see a reason to have it call a shell script that
compiles something into a .o file.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can makefile allow me to compile programs I modify and see on my screen ?

[Eric Christopherson]

On Sat, Jul 18, 2015, aubertin.sylvain wrote:
 I can use « make » in order to compile programs written on my disk.
 But when I modify a program, I should like, not to register it, before
 I compile it with « make ».  I suppose I can compile the program I
 have on my screen, instead of that one I have on my disk.  So, it will
 go much qicker.  I should like, somebody gives to me an example of a
 makefile that avoids registering, before compiling.  Thanks

By registering you mean saving? I don't know of any compiler like that
except for tcc, which is very minimalistic. I can't really think of a
reason to compile something that's not saved, though; it wouldn't make
things noticeably quicker.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: V selects past end of line. How to stop this?

[Eric Christopherson]

On Fri, Jul 10, 2015 at 6:25 AM, Marcin Szamotulski msza...@gmail.com wrote:
 Hi Reckoner,

 A one character shorter solution is to use `0y$` but if what you really
 need is the visual mode then `g_` seems unavoidable.

 -Marcin

Note that g_ doesn't include any whitespace that might be at the end
of the line. If you want that space, you can use 0v$h.


 On 21:59 Thu 09 Jul , h_east wrote:
 Hi Reckoner,

 2015-7-10(Fri) 12:48:11 UTC+9 ZyX:
  2015-07-10 5:36 GMT+03:00 Reckoner recko...@gmail.com:
   The normal 'V' command visually selects the line past the end of the 
   line. I
   want to select only to the end of the line, but *not* beyond that. I 
   looked
   at the 'selection' option but that does not help.
 
  V is a linewise selection. You *cannot* omit including the line break
  in linewise selection, its very purpose is to select the whole line.
 
  
   What am I missing here?
  
   Thanks!

 Probably you want to 'g_'.

 :h g_

 When following command typed in normal mode, Those of your hopes are 
 character-wise visual selected.

 0vg_

 --
 Best regards,
 Hirohito Higashi (a.k.a. h_east)

 --
 --
 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+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

 --
 --
 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+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.



-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: what does CR mean in the vim command?

[Eric Christopherson]

On Tue, Jul 07, 2015, elearn2...@gmail.com wrote:
 Here is a viim command
 
 nnoremap silent F6f :!firefox 'http://127.0.0.1/%:t' CR  
 
 What does CR in the end of the command mean?

The CR means a carriage return is sent at the end. The  is a Unix
shell directive (I'm not sure if that's the right word) to make it
execute the command (i.e., the firefox command) in the background and
immediately return control.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: what does CR mean in the vim command?

[Eric Christopherson]

On Wed, Jul 08, 2015, Nikolay Pavlov wrote:
 2015-07-08 9:06 GMT+03:00 Eric Christopherson echristopher...@gmail.com:
  On Tue, Jul 07, 2015, elearn2...@gmail.com wrote:
  Here is a viim command
 
  nnoremap silent F6f :!firefox 'http://127.0.0.1/%:t' CR
 
  What does CR in the end of the command mean?
 
  The CR means a carriage return is sent at the end. The  is a Unix
  shell directive (I'm not sure if that's the right word) to make it
  execute the command (i.e., the firefox command) in the background and
  immediately return control.
 
 It is not a directive, it is officially an operator:
 http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_09_03.
 And it does not need to return control at all; the only thing that
 standard says on the matter is that “the shell shall not wait for the
 command to finish before executing the next command”. I have not found
 anything regarding what shall be done with backgrounded commands when
 shell exits, but all shell implementations I know simply exit without
 sending backgrounded processes anything, thus letting init take the
 parentship and background process continue to run.
 
 Shell does not return control intentionally, it simply exits when
 there are no more commands to run.

Weird. I just tried it (in the shell, not Vim) and it seems you're
right. I always thought it would send the subprocess HUP.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Auto-commenting

[Eric Christopherson]

On Sun, Jun 28, 2015, meino.cra...@gmx.de wrote:
 Hi,
 
 when using vim for editing Perl sources, vim proceeds
 the next line with an comment sign '#', if the previous
 one was a comment line using RET in insert mode.
 
 To not to miss even one of the wonderful feature of vim ;)  :
 
 Suppose the situation is as follows (inser mode)
 
 # this is a comment in perl _
 
 and _ is, where my coursor is, Now I want to start
 coding in the next line. RET gives me a new line, but
 with a # in front of it, which I need to delete.
 
 Another way to get commentless to the next line would
 be ESCo
 
 Is there any other more elegant and/or shorter way to accomplish this?
 
 Thanks a lot for any help in advance!
 Best regards,
 Meino

I use these two mappings, Alt+Enter and Shift+Enter. I've found that
different Vim UIs have issues with one or the other of these, so I map
both.

inoremap silent A-CR C-o:let b:fo=foBarset 
fo-=rCRCRxBackspaceC-o:let fo=b:foBarnormal! giCR
inoremap silent S-CR C-o:let b:fo=foBarset 
fo-=rCRCRxBackspaceC-o:let fo=b:foBarnormal giCR

I believe Raimondi on FreeNode did most of the work on creating these.
fo is formatoptions (:h formatoptions).

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Reverse CTRL-P list ?

[Eric Christopherson]

On Mon, Jun 08, 2015, meino.cra...@gmx.de wrote:
 Jack Stratton j...@phroa.net [15-06-08 16:54]:
  On 2015-06-07 20:12, meino.cra...@gmx.de wrote:
  Hi,
  when programming I am using CTRL-P
  Is there a way to reverse this list?
  
  Hi, have you considered using Ctrl-N for completion instead?
  
  If I'm thinking straight, it should highlight them in reverse order.
  
  HTH
[snip]
 Hi Jack,
 
 shame on me... :)
 Sometimes solutions are far to simple for me, hahahaha!
 Many thanks for you help!
 Best regards,
 Meino

It's interesting to note the commands each individual knows about and
how that set varies from person to person. I personally always use ^N
and forget that ^P is there; you had the opposite.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: search for a list of words

[Eric Christopherson]

On Fri, May 08, 2015, Fetchinson . wrote:
 Is it possible to search for a list of words?
 I mean if I have a text I'd like to search for
 either 'foo' or 'bar' and when the matches
 are highlighted, I'd like to be able to jump
 between the matches (which include both
 words 'foo' and 'bar').

I know this has been answered, and my recommendation doesn't seem to
quite match your use case, but I thought people should be aware of a few
other projects:

https://github.com/tpope/vim-abolish
https://github.com/msbmsb/stem-search.vim

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: search for a list of words

[Eric Christopherson]

On Fri, Jun 05, 2015, Waters, Bill wrote:
 I guess it's a nuance of nnoremap that I am forgetting.
 
 This...
   map F12 \+
 
 Or, better, this...
   map F12 Leader+
 
 ...both work.

Yes. The purpose of the *noremap commands is to make mappings that
invoke only operations built into Vim; in other words, they don't go
through any additional layers of mapping.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Sourcing .vimrc for use in bash shell?

[Eric Christopherson]

On Sat, Jun 06, 2015, Paul wrote:
 On Saturday, June 6, 2015 at 11:24:25 PM UTC-4, Eric Christopherson
 wrote:
  On Sat, Jun 06, 2015, Paul wrote:
  I don't find that my vimrc settings take effect when using vi
  editing mode in readline.  However, I can use the fc commad to
  switch into full fledged vim.  Googling hasn't clarified whether it
  is built-in to bash or a separate command (there's info indicating
  both cases).  In Cygwin, it seems to be a separate executable, so
  not part of bash.
 
  You can tell for sure what kind of command fc is with
 
  type fc
 
  in the shell. For me it outputs fc is a shell builtin. There's a
  shortcut, though: hitting Ctrl-X Ctrl-E on any line will bring up an
  editor for that particular line, like fc does. I think it also uses
  the same environment variables as fc does to determine which editor
  to launch.
 
 Actually, I'm blind.  I did in fact use type -a and what came back
 was 
 
fc is a shell builtin
fc is /c/Windows/system32/fc
 
 The Windows version does something completely unrelated.
 
 As for Ctrl-X Ctrl-E, it doesn't do anything in my setup.

That's strange. I don't have it explicitly enabled in .inputrc, but
`bind -p` shows it as 

\C-x\C-e: edit-and-execute-command

So you should be able to add that to your .inputrc. Or pick a key
binding that suits you better.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Sourcing .vimrc for use in bash shell?

[Eric Christopherson]

On Sat, Jun 06, 2015, Paul wrote:
 On Thursday, June 4, 2015 at 2:31:24 AM UTC-4, Sonny Chee wrote:
  Hey Guys,
  
  Is it possible to source .vimrc so that the mappings and settings
  within are available for command line editing in the shell?
 
 I don't find that my vimrc settings take effect when using vi editing
 mode in readline.  However, I can use the fc commad to switch into
 full fledged vim.  Googling hasn't clarified whether it is built-in to
 bash or a separate command (there's info indicating both cases).  In
 Cygwin, it seems to be a separate executable, so not part of bash.

You can tell for sure what kind of command fc is with

type fc

in the shell. For me it outputs fc is a shell builtin. There's a
shortcut, though: hitting Ctrl-X Ctrl-E on any line will bring up an
editor for that particular line, like fc does. I think it also uses the
same environment variables as fc does to determine which editor to
launch.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: quotation text object consternation

[Eric Christopherson]

On Tue, Jun 02, 2015, Eric Christopherson wrote:
 

Whoops; sorry about the empty posting.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: quotation text object consternation

[Eric Christopherson]

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: macvim for Yosemite?

[Eric Christopherson]

On Thu, May 21, 2015, Richard Mitchell wrote:
 On Thursday, May 21, 2015 at 1:41:43 PM UTC-4, russur wrote:
  Hi All,
  
  I have been using Macvim on my old Powerpc mac for some time now, no 
  problems. My wife bought me a newish mac mini running Yosemite OS X. In 
  looking to see if there is a version of Macvim that runs on this, i seem to 
  be getting conflicting reports. So i ask you the community, does any one 
  know if there is a build for Macvim that runs ok under Yosemite?
  
  Thanks,
  
  
  Russ
 
 Aren't I all wet.  I was going to ask why not just get the binaries straight 
 from macvim.org, but I see the site is gone now.  That has always worked 
 great for me and will surely be missed.
 
 Is it going to come back or is gone for good?

I'm not sure how long it's been gone, but I don't remember seeing it for
quite some time. Its current home, if the Homebrew formula can be
believed, is now https://code.google.com/p/macvim/ - which redirects to
https://github.com/macvim-dev/macvim . (I'm unsure of how canonical it
is, though, since it's a fork of b4winckler's MacVim.)

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: vim how to edin same file in different window

[Eric Christopherson]

On Sat, May 16, 2015, Gary Johnson wrote:
 On 2015-05-16, Christian Brabandt wrote:
  Hi Daniel!
  
  On Sa, 16 Mai 2015, Daniel Dimitrov wrote:
  
   I have splited the window in 2 different views by Ctrl+W, V but what i
   want to achieve is to edit them separately without affecting the other
   and after that save them with different names. Thanx in advance
  
  After splitting do a
  :saveas name
  in each window to make sure, that each window has its own buffer with 
  its own name for the original buffer.
  
  (Obviously it would be better to use a different name in each window ;))
 
 When I try that, the buffer name changes in both windows.  The
 windows are just different views into the one buffer.
 
 The way I usually do that is yank the buffer into a register, open a
 new buffer in a new window, paste the register into that buffer, and
 delete the empty first line, e.g.,
 
 ggyG
 :new
 p
 kdd
 
 Or you could read the file into the new buffer, e.g.,
 
 :new
 :r#
 :0d_
 
 Regards,
 Gary

A shortcut would be to, before splitting windows or starting new
buffers, follow these steps with the original buffer active:

1. :w   (with filename if it hasn't already got one. IMPORTANT)
2. :sav filename2
3. :sp #(or :vsp # for vertical)

:sav automatically saves the current buffer as a new file _and_ opens a
buffer in Vim for that file; that new buffer is made active. Then :sp #
opens a split on the alternate file, which is the file from which the
current buffer was cloned. This puts the original file's window above or
to the left of the clone, unless :bel is prefixed in step 3.

Step 1 is important because, if you've made changes in the original
buffer, the changes will end up getting saved to filename2, and lost in
the original buffer. (Although I suppose sometimes one might intend to
do this, if the buffers aren't meant to be identical to begin with.)

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: surround vim + rails vim : ERB tags are added on the separate line

[Eric Christopherson]

On Sun, May 03, 2015, Robert Balejík wrote:
 I use those 2 plugins so I wanna use them so I tried to put ERB tags on the 
 line - so I visually select line do S = just as is suggested here 
 https://stackoverflow.com/questions/4275209/how-do-i-insert-erb-tags-with-vim
 but it put ERB tags %=  % on the sperarate line? did anyone have this 
 problem

For me, that only happens when I have a whole line selected, as with
Vim's capital-V visual mode. I assume that's the intended behavior. When
I have text selected in non-linewise mode, it puts the beginning and end
of the tag on the same line.

(I also see there seems to be a bug that's triggered if you do a
characterwise selection on the last line in a file, up to and including
EOL.)

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Gnome warnings?

[Eric Christopherson]

On Sat, Apr 18, 2015, Christian Brabandt wrote:
 Hi catch22!
 
 On Fr, 17 Apr 2015, catch22 wrote:
 
  Thanks, but that's a bit over my head. I installed vim-gtk just now
  but it doesn't change anything; I suppose I have to delete vim-gnome
  but don't want to risk having to set everything up from scratch again
  to get vim working. It looks like the warnings don't harm anything, so
  I'll leave it as is.
 
 Check the :version output, if you actually run the vim.gtk or still the 
 vim.gnome version. Other than that the warning is harmless.

I agree. Quite many *nix GUI programs have those warning messages on stdout
if you run them from a terminal.

 
 Best,
 Christian

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Motif equivalent of GTK font

[Eric Christopherson]

It's possible Motif still uses the old-style XLFD method of specifying
fonts. Monospace is likely a Fontconfig alias for a specific
monospace family like FreeMono or Luxi Mono. I've been looking for a
while just now but can't seem to find anything that would allow you to
translate that alias into XLFD, but you can at least list the XLFD
names of all the Unicode monospace fonts on your system with

xlsfonts -fn '-*-*-*-*-*-*-*-*-*-*-m-*-iso10646-*'

For more information on this type of font specification, see
https://wiki.archlinux.org/index.php/X_Logical_Font_Description.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Editing tar file under osx

[Eric Christopherson]

On Feb 20, 2015 1:56 PM, Subbu subbus.jo...@gmail.com wrote:
 I will try using rm -f command for the tar --delete -f on my vim and
give a try if I could make it work. I will keep you guys posted :)

That sounds dangerous; you'll end up deleting your tar file and possibly
other files.

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Any poets here?

[Eric Christopherson]

On Fri, Jan 30, 2015 at 3:56 PM, Eric Weir eew...@bellsouth.net wrote:

 On Jan 30, 2015, at 3:49 PM, Tim Chase v...@tim.thechases.com wrote:

 But for merely editing text, whether code, prose, or poetry, I'd take
 vim any day.

 I’ve never written an inch of code, but vim is by far my preferred editor. 
 When I have to use TextEdit, I’m always typing in vim commands. Oh if they 
 only had the same effect. QuickCursor used let me use vim as my preferred 
 editor in other apps, e.g., in Apple Mail. Alas, the steps Apple took to 
 improve security by isolating apps from one other rendered QuickCursor 
 unusable. Oh how I wish that problem could be overcome.

QuickCursor can still be used, if you compile it yourself; it's just
that Apple's sandboxing rules don't allow it to be in the App Store.
Its source is available at
https://github.com/jessegrosjean/quickcursor . Since you say you're
not a coder, I put a compiled version of it up on my Dropbox at
https://www.dropbox.com/s/1hmp013km6odzzg/QuickCursor.app.zip?dl=0 ; I
hope it works for you.

(I find that MacVim works fine, although I decided to change my MacVim
Open files from applications preference to in a new window so the
temporary files used by QuickCursor don't pollute my existing Vim
instances. I haven't had any luck with it using Emacs or SublimeText
as editor, but I assume that won't bother many people here!)


 --
 Eric Weir
 Decatur, GA  USA
 eew...@bellsouth.net

 Imagining the other is a powerful antidote to fanaticism and hatred.

 - Amos Oz

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Vim colorscheme

[Eric Christopherson]

On Thu, Jan 15, 2015, Justin Licata wrote:
 Hi all,
 
 Thanks for taking a look at the question.
 
 I'm trying to use the solarized theme for vim. 
 http://ethanschoonover.com/solarized
 
 I've cloned the package into my bundle directory `~/.vim/bundle`

Are you using vim-pathogen or Vundle or NeoBundle? If not, the
~/.vim/bundle directory probably won't be seen by Vim.

 
 The folder `~/.vim/colors` is empty.
 
 When I use vim, I get the error:
 
 Error detected while processing /Users/justin/.vimrc:
 line   94:
 E185: Cannot find color scheme solarized
 Press ENTER or type command to continue
 
 However, when I click enter the color scheme is correct and it looks like it 
 should.

I hope someone else can help with this part; I'm not sure why the color
scheme would look correct when Vim doesn't see it. Are you running Vim
in a terminal -- and if so, is that terminal set to use Solarized (i.e.
even outside of Vim)? If so, it might be that you're just seeing the
default Vim color scheme, but it's being filtered through the terminal's
own color settings.

 
 Now, when I copy the file
 `~/.vim/bundle/vim-colors-solarized/colors/solarized.vim` over into
 `~/.vim/colors/solarized.vim`, the error goes away but the colorscheme
 is all wrong. It has a light grey background and the colors are all
 different.

Not sure about this either.

 
 Clearly I'm new to using vim. Any help into this would be appreciate.
 
 Thanks,
 
 Justin
 
 -- 
 -- 
 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+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: default indentation of perl code

[Eric Christopherson]

On Sat, Jan 03, 2015, kamaraju kusumanchi wrote:
 On Sat, Jan 3, 2015 at 1:35 PM, Eric Christopherson
 echristopher...@gmail.com wrote:
  On Sat, Jan 03, 2015, kamaraju kusumanchi wrote:
  I am finding that the default indentation settings used for perl code
  are not very intuitive.
 
  After spending some time scourging through help files, google etc., I
  arrived at these
 
  autocmd FileType perl set autoindent | set smartindent
  autocmd FileType perl inoremap # X ^H#
 
  What is the purpose of the second autocmd?
 
 
 I used it to get the comment(s) indentation right. With out that if I
 write a comment after a subroutine definition, the comment would be
 moved to the first column.
 
 For example, say I have
 
 sub read_file()
 {
 # some comment here
 
 this would be changed as
 
 sub read_file()
 {
 # some comment here
 
 This is explained in :help smartindent as follows
 
 When typing '#' as the first character in a new line, the indent for
 that line is removed, the '#' is put in the first column.  The indent
 is restored for the next line.  If you don't want this, use this
 mapping: :inoremap # X^H#, where ^H is entered with CTRL-V CTRL-H.
 
 hope that helps
 raju

Oh, that makes sense. I was confused because your message gave an extra
space after the X.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: default indentation of perl code

[Eric Christopherson]

On Sat, Jan 03, 2015, kamaraju kusumanchi wrote:
 I am finding that the default indentation settings used for perl code
 are not very intuitive.
 
 After spending some time scourging through help files, google etc., I
 arrived at these
 
 autocmd FileType perl set autoindent | set smartindent
 autocmd FileType perl inoremap # X ^H#

What is the purpose of the second autocmd?

 
 My question is why are these options not turned on by default? These
 would make life so much easier for a novice perl programmer using the
 vim editor. Often learning a new language is hard enough... why add
 the additional pain of mastering the editor?
 
 There are probably tons of other vim settings that the majority of
 perl programmers find useful. But I am not knowledgeble enough to
 speak for all of them. In any case turning on the above should be
 least controversial, no?
 
 FWIW the default behavior in emacs is very similar to what I get with
 the above settings. In fact, emacs does something even better. If a
 line does not end in ';' it automatically adds an indent.
 
 For example, if I have
 
 $ emacs parse.pl
 sub read_data()
 {
 a=1
 pressing enter takes me here
 
 sub read_data()
 {
 a=1;
 pressing enter takes me here
 
 
 How can I get similar behavior in vim?
 
 raju

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Unknown option argument: --multiprocessing-fork

[Eric Christopherson]

On Tue, Dec 23, 2014, Canis Major wrote:
 On Tuesday, December 23, 2014 1:24:08 PM UTC+1, Christian Brabandt wrote:
  Hi CanisMajorWuff!
  
  On Di, 23 Dez 2014, CanisMajorWuff wrote:
  
   I have an error on Windows vim version 7.4.417: Unknown option
   argument: --multiprocessing-fork . It is related to using python
   multiprocessing. How I can fix that?
  
  There is no such argument --multiprocessing-fork for vim. How did you 
  encounter that?
  
  Mit freundlichen Grüßen
  Christian
  -- 
  Kunst ist eine Art zwanghafter Akrobatik.
  -- Emilio Vendova (ART - Das Kunstmagazin 1985 / 7)
 
 I encountered it by using python plugin which uses python multiprocessing 
 module.

I don't understand how pymode or rope passes this argument to Vim, but
this thread https://github.com/klen/python-mode/issues/422 makes it
look like this has to do with using HEAD by default; try using commit
20e14aa as it says in that thread. (I don't know if there's a newer
commit that would also work, but it's worth investigating.)

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Changing line numbers from normal to relative

[Eric Christopherson]

On Mon, Nov 10, 2014, Ben Fritz wrote:
 On Monday, November 10, 2014 12:41:06 PM UTC-6, Christian Brabandt wrote:
  Hi Ben!
  
  On Mo, 10 Nov 2014, Ben Fritz wrote:
  
   On Monday, November 10, 2014 10:25:55 AM UTC-6, Christian Brabandt wrote:
Am 2014-11-10 14:51, schrieb Ben Fritz:
 I've noticed this myself over the last few years I've been using the
 mapping. Especially this is apparent in operator-pending mode. It
 looks like some sort of bug in Vim. I thought I reported it before but
 I can't find it now.

I think the explicit redraw causes this. I think you might get around 
this,
by not redrawing explicitly and using the silent flag for the
mappings.
   
   Without the explicit redraw, sometimes the line number column does not 
   update. I think the main problem was in operator pending mode.
  
  I haven't seen that, when using the silent flag, but I haven't tested 
  it heavily.
  
 
 Thanks! I removed the redraw, and added silent to each mapping, and now the 
 line numbers update properly and the cursor stays put!

That isn't what I get. In my case, the number column doesn't appear or
disappear at all until I do C-l.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: vim: surround plug bug

[Eric Christopherson]

On Sun, Nov 09, 2014, Eric Christopherson wrote:
 On Sat, Nov 08, 2014, ping song wrote:
  I believe this is easy to reproduce:
  
  test string 1. hi hello world.
  test string 2. hi hello world .
  
  I want to surround hello world (generating -  hi hello world).
  using surround.vim plugin, if my cursor is within hello, but not on h,
  the provided method is as following:
  ys2aw
  
  if my cursor is on 'h' in hello, then this also works:
  ys2w
  
  the first method save a move (b key) but does not work for test
  string1, but works well for test string 2. I think this might be a
  bug...
 
 That does seem wrong (specifically, in the first example, the quote goes
 before the space between `hi` and `hello`). You should notify Tim Pope,
 the author of the plugin. Do you have a GitHub account? If so, post the
 bug at https://github.com/tpope/vim-surround/issues .

Actually, it appears the bug you've found is related to these:

https://github.com/tpope/vim-surround/issues/137
https://github.com/tpope/vim-surround/issues/138

Tim Pope admits there might be some edge cases, but it sounds like the
core problem is a non-issue.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Changing line numbers from normal to relative

[Eric Christopherson]

On Thu, Nov 06, 2014, Ben Fritz wrote:
 On Thursday, November 6, 2014 2:53:02 PM UTC-6, Salman Halim wrote:
  Hi,
  
  I was wondering if it was possible to switch to relative line numbers once 
  I'm in operator-pending mode and then switch back when done. For example, 
  say I have regular line numbers turned on and I hit 'c' in normal mode on 
  line 24. The numbering changes to relative and goes back to regular numbers 
  after the rest of the command is executed.
  
  I couldn't find an autocommand, but was hoping someone else had already 
  come up with an ingenious way to address this.
  
 
 I did not find any autocmd for it, but I use an expression mapping returning 
 an empty string in normal, visual, and operator-pending modes to accomplish 
 the task:
 
 if exists('+relativenumber')
   nnoremap expr C-Space CycleLNum()
   xnoremap expr C-Space CycleLNum()
   onoremap expr C-Space CycleLNum()
 
function to cycle between normal, relative, and no line numbering
   func! CycleLNum()
 if l:rnu  !l:nu
   setlocal nu
 elseif l:rnu  l:nu
   setlocal nornu
 elseif l:nu  !l:rnu
   setlocal nonu
 else
   setlocal rnu
 endif
  sometimes (like in op-pending mode) the redraw doesn't happen
  automatically
 redraw
  do nothing, even in op-pending mode
 return 
   endfunc
 endif
 
 Thus when I hit C-Space in any of these modes, nothing happens, which 
 allows me to continue with my operation, but the line numbering changes as a 
 side effect.

Great idea! But I find it only works in the terminal when I call the map
C-@ (even though my terminal treats C-Space as C-@).

If I use C-Space as the map name, when I try the C-Space combination
in one of those modes, I just get a bell. I tried running Vim with
-V20vim.out to log what's going on, and it didn't show that CycleLNum()
was ever called.

Two other minor quibbles here:
- it doesn't reset the old numbering style after a motion or visual
  operation has been done.
- the visual representation of the cursor moves to the end of the
  screen, although the actual logical cursor position in Vim isn't
  changed. Surprisingly, this affects GUI vim too.

I'm using MacVim 7.4 (73), which has Vim 7.4.258 in it.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: vim: surround plug bug

[Eric Christopherson]

On Sat, Nov 08, 2014, ping song wrote:
 I believe this is easy to reproduce:
 
 test string 1. hi hello world.
 test string 2. hi hello world .
 
 I want to surround hello world (generating -  hi hello world).
 using surround.vim plugin, if my cursor is within hello, but not on h,
 the provided method is as following:
 ys2aw
 
 if my cursor is on 'h' in hello, then this also works:
 ys2w
 
 the first method save a move (b key) but does not work for test
 string1, but works well for test string 2. I think this might be a
 bug...

That does seem wrong (specifically, in the first example, the quote goes
before the space between `hi` and `hello`). You should notify Tim Pope,
the author of the plugin. Do you have a GitHub account? If so, post the
bug at https://github.com/tpope/vim-surround/issues .

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: vim: Zoomwin plugin stop working after c-wc-o

[Eric Christopherson]

On Sat, Nov 01, 2014, ping song wrote:
 it's very easy to reproduce. just c-wc-o and then all windows
 won't came back anymore. I know this is expected. but what's the value
 to keep that if we have Zoomwin? the suggestion will be to provide an
 option to also map that to what c-w_o does...

Are you saying that C-wo works but not C-wC-o? That's easy to fix:
put this in your .vimrc:

nmap C-wC-o C-wo

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Strange reaction of gvim to : in a normal mode

[Eric Christopherson]

On Sun, Nov 02, 2014, Gevisz wrote:
 On Sun, 2 Nov 2014 14:51:24 +0200 Gevisz gev...@gmail.com wrote:
 
  I use gvim from xfce4 and sometimes get into a strange
  situation when pressing : while being in a normal mode
  leads not to the command line mode but instead highlights
  the icon Copy to clipboad.
  
  Just now I have noted that in this situation I also cannot
  see the version of my gvim via the Help menu (but saving via
  the the Save current file icon usually works).
 
  The output from the :version command (executed from a newly
  started gvim) is as follows:
  
 skipped
  
  Any ideas how to fix it?
  
  And whom to blame? (Except for myself, of course. :) 
  My first guess that something is wrong with xfce4 here.
 
 I cannot describe how to reproduce this behavior but usually
 it appears after the following steps:
 
 1. I work with gvim and firefox.
 2. After finishing working with gvim, I turn to firefox,
go to a news site and look through all its Twitter
news band that is somehow embedded into its webpage.
On this step I also open new tabs from the news band.
 3. I return to gvim and try to save and close it using
:wq command but it does not work any more as : sends
focus to the Copy to clipboard icon.

It almost sounds to me like there's unusual keyboard mapping going on.
Do you use Vimperator, by chance? (I wouldn't think that would affect
anything outside Firefox, though.)

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trouble using blockwise actions on visual selections in a function/command

[Eric Christopherson]

On Fri, Oct 31, 2014, Charles Campbell wrote:
 Josef Fortier wrote:
 I'm trying to extend a copy and comment action (leveraging one of the 
 numerous smart comment plugins). I've a simple line-wise command and was 
 trying to extend to it work on a visual selection.
 
 It looks like vim is set to work linewise (and only linewise) here. Which is 
 not ideal, as rather then commenting a block all at once, I end up with 
 single line comment - copy repetitions.
 
 Things I've tried:
 
 A command with -range. This is meant to work in a blockwise fashion
 
 A mapping to a function. I have trouble getting the start end end lines. 
 I've tried using ` and ` but these values don't get set (maybe the 
 function is called too soon?).
 
 It seems like there should be a way to manipulate visual blocks in a 
 function, but it's not clear to me. Can someone offer assistance?
 
 You might find the following plugins helpful:
 
   vis.vim (http://www.drchip.org/astronaut/vim/index.html#VIS) : Performs an
 arbitrary Ex command on a visual highlighted block
   NrrwRgn.vim (http://www.vim.org/scripts/script.php?script_id=3075) :
 Narrow Region plugin for Vim
   :he /\%c  regexp for restricting match to a specified column
   :he /\%l   regexp for restricting match to a specified line
 
 Regards,
 Chip Campbell

I remember seeing another plugin that allowed the user to select text in
any visual mode and then treat the selection as if it were another kind
of selection, e.g. originally selecting in linewise mode but then
prepending characters on it as if it were blockwise. Unfortunately I
can't find that plugin, though.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: .vimrc not always used

[Eric Christopherson]

On Thu, Oct 30, 2014, Vlad Ghitulescu wrote:
 Hello!
 
 
 I'm using the current version of MacVim (Sanpshot 73) on an iMac running
 OS X 10.10 Yosemite.
 
 I have in my home-directory the .vimrc-file attached below.
 However the .vimrc is working only when opening first MacVim and then a
 file in a tab. Opening a file via the context-menu or from MacVim via
 the menu File  Open opens the file in a standard MacVim-window (see the
 two attached screenshots).
 
 Do you have an idea?

I'm not sure if this is related, but MacVim has a preferences option (in
the MacVim menu  Preferences  Advanced  Enable Quickstart) that
controls whether .vimrc and ~/.vim/** are reloaded for new windows.

-- 
Eric Christopherson

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Cannot make snippet plugin working...

[Eric Christopherson]

On Mon, Oct 06, 2014, Gevisz wrote:
 Nevertheless, my test snippet that is just intended
 to expand forC-S to for test does not work.

Are you running Vim in a terminal? ^S is special in Unix terminals; by
default it sends a signal that you'd like terminal output to stop
temporarily (to be resumed when you press ^Q). If running in a terminal,
you need to run

stty -ixon

(e.g. in your .bashrc) to make the terminal treat ^S like any other
control-key combination.

OTOH, if you're running gVim, that shouldn't be an issue in the first
place.

 
 The for.spt file is put in both ~/.vim/snippets/c
 and ~/.vim/snippets/global directories. In .vimrc
 is added
 let snippet_use_global=1

I see that the documentation does say to use that, but I think you might
have to put g: before snippet_use_global=1.

 
 Well, it is not critical because I have decided to follow
 the advice of Marc Weber and try ultisnips but I am still
 just curious why this snippet plugin does not work.
 
 By the way, ultisnips is much more complex, so I have
 much more chances to get it not working. ;)

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: problem with menu

[Eric Christopherson]

On Mon, Oct 06, 2014, Charles Campbell wrote:
 Hello!
 
 I just noticed that my gvim menus have disappeared.

What have you changed recently, if anything?

 
 * Huge version with GTK2-GNOME GUI, has +menu, Included patches: 1-452
 * has(menu) gives a 1
 * echo go yields:  abegmr
 
 So, I tried a special .vimrc; I called it simplemenu.vimrc:
 
 set nocp
 menu MenuTest:echo menus workingcr
 
 and then
 
 gvim -u simplemenu.vimrc
 
 Result: no menu.
 
 Any ideas?

Are you running in Ubuntu Unity or GNOME Shell by chance?

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: command-line commands instead of abbreviations?

[Eric Christopherson]

On Sun, Sep 28, 2014, Ben Fritz wrote:
 On Sunday, September 28, 2014 1:03:27 AM UTC-5, gevisz wrote:
  Is it possible to define a command-line command
  that just inserts some text after the current
  cursor position and how to do it in an elegant way?
  
  For, example, so that typing in normal mode :тл will
  insert тру-ля-ля after the current position in text.
  
  P.S. In my case the command name will always be in
   cyrillic, so that not to switch the keyboard
   layout.
 
 Easy solution: use a :normal! command within your command definition, to 
 insert the text with 'a'.
 
 E.g. :command тл normal! aтру-ля-ля

That appears to be an invalid command name, as does the capitalized
variant Тл. Perhaps non-Roman scripts aren't supported as command names?

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Two new Vim books

[Eric Christopherson]

On Thu, Sep 25, 2014, Stephen Oualline wrote:
 Two new Vim books
 
 Free: Vim Tutorial and Reference
   http://www.oualline.com/vim-book.html
 
   Covers almost every Vim command and shows you every significant
   command works.
 
 Pay: Wicked Cool Vim
   
 http://www.amazon.com/Wicked-Cool-Vim-Vi-Improved-ebook/dp/B00LP6MLOG/ref=sr_1_1?ie=UTF8qid=1411695756sr=8-1keywords=wicked+cool+vim
 
   How to do neat things in Vim for those that know the basics.

Thanks, Stephen! The free book at least looks really helpful. Could you
share a table of contents for the Kindle one?

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Select Copy Not Work On Mac

[Eric Christopherson]

On Mon, Sep 15, 2014, huangyingw wrote:
   Hi,
After set clipboard=unnamedplus, this works on Ubuntu, but 
 does not work
 in Mac OS X.

I can confirm this behavior happens in MacVim, which is surprising.
Perhaps we should report it as a bug to b4winckler.

 If I want the select copy works perfectly both on Ubuntu and OS X,
 what should I do?
 I notice that the default vim in OS X is  -xterm_clipboard
 
 mac:MacOS huangyingw$ vi --version|grep clipboard
 -clientserver -clipboard +cmdline_compl +cmdline_hist +cmdline_info
 +comments
  -xterm_clipboard -xterm_save
 
 And the Vim in MacVim is +clipboard, but also -xterm_clipboard
 
 mac:MacOS huangyingw$ ./Vim --version|grep clipboard
 +clipboard   +iconv   +path_extra  +transparency
 +eval+mouse_dec   +startuptime -xterm_clipboard
 
 What's the quickest way to change from  -xterm_clipboard to 
 +xterm_clipboard.
 Or, I really doubt that, is OS X, there is no  xterm_clipboard, for
 it is used in X11 environment, not available in OS X? 

X11 is available in OS X; it's just that relatively few users use it
often. I don't think you need to worry about +xterm_clipboard unless you
actually use a build of Vim that runs under X11. (I do recall that X11
for Mac has options for whether to synchronize the Mac clipboard with
either X11's PRIMARY or X11's CLIPBOARD, which would increase
complications.)

Nevertheless, the source for MacVim is at
https://github.com/b4winckler/macvim ; perhaps with the right configure
switches it can be made to use +xterm_clipboard.

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Select Copy Not Work

[Eric Christopherson]

On Sun, Sep 14, 2014, huangyingw wrote:
   Hi,
   I am trying to enable the select copy to system clipboard.
   My intention is to use “v” to select part to copy, and press 
 “Y” to copy
 to system clipboard.
   Bellowing is my part of my vim script:
 [code]
   nnoremap Y +yy
   clipboard=unnamedplus
 [/code]
   Bellowing is my vim version information:
 [code]
   huangyingw@mini14:~$ vim --version
 VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jan  2 2014 19:39:59)
 Included patches: 1-52
   huangyingw@mini14:~$ vim --version|grep clipboard
 +clipboard   +iconv   +path_extra  +toolbar
 +eval+mouse_dec   +startuptime +xterm_clipboard
 huangyingw@mini14:~$ 
 [/code]

What OS are you running? Is it GUI vim, or terminal? If terminal, are
you running it in tmux or screen?

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Installing 7.4 windows over 7.2 windows

[Eric Christopherson]

On Thu, Sep 11, 2014 at 3:53 PM,  russurquha...@verizon.net wrote:

  Hi,

 I have been very happy using vim 7.2 under windows, but was wondering if i 
 download and install vim 7.4, will that undo all my plugins, customizations, 
 etc. that i have set up currently under 7.2?

 I'd like to try the new one, but don't want to loose the customizations i 
 have?

As long as those customizations are in your vimfiles directory (in
your one profile rather than in C:\Program Files or wherever Vim is
installed), they should stick around. A word of caution, though: I
just uninstalled my copy of 7.4 (the default Windows package provided
by vim.org), and it helpfully asked me if I'd like it to delete my
vimfiles folder. I made sure to tell it no.

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Unable to update Vim past ver 7.4.408

[Eric Christopherson]

On Fri, Aug 29, 2014, Bob Hyam wrote:
 I have been using this script to update Vim for a long time, but noe I cannot 
 upgrade beyond patch 408.
 
 I tried manually from cli but get same result.
 
 
 cd /usr/src/vim
 hg pull
 hg update
 make distclean
 ./configure --enable-rubyinterp=yes --enable-pythoninterp=yes 
 --with-python-config-dir=/usr/lib/python2.6/config --with-features=huge 
 --enable-gui=auto --with-compiledby=Bob_Hyam
 ##cd src  make first
 cd src
 make
 make install
 
 
 
 Any guidance would be greatly appreciated !
 
 Thanks,  Bob H

What happens when you try? What OS are you using?

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Conqueterm blanks some lines

[Eric Christopherson]

On Fri, Aug 22, 2014 at 12:45 PM, Tim Chase v...@tim.thechases.com wrote:
 On 2014-08-22 10:42, John Biederstedt wrote:
 Whenever I use conqueterm (on linux) to ssh to a nexus switch, and
 backspace causes the line to go blank.  Anyone else experience this?

 I think you may have sent this to the wrong mailing list.

Nope; ConqueTerm is a Vim plugin :)


 That said, I'd check what your $TERM settings are on both ends and
 make sure they aren't getting manually set to something wrong.

 -tim

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Treat section of file as entire file

[Eric Christopherson]

On Fri, Aug 01, 2014, Christian Brabandt wrote:
 Hi Paul!
 
 On Do, 31 Jul 2014, Paul wrote:
 
  NrrwRgn and […] don't save the original buffer when I write changes to
  the narrowed region.
 
 For whatever reason you want that, you should refer to the documentation 
 of NrrwRgn. It has an option g:nrrw_rgn_write_on_sync
 

I see g:nrrw_rgn_write_on_sync was just deprecated; its replacement is a
buffer-local hook:

From NarrowRegion.txt:
| A third hook 'b:nrrw_aucmd_written' is provided, when the data is written back
| in the original window. This allows to execute scripts, whenever the data is
| written back in the original window. For example, consider you want to write
| the original buffer whenever the narrowed window is written back to the
| original window. You can therefore set: 
| 
| :let b:nrrw_aucmd_written = ':update'
| 
| This will write the original buffer, whenever it was modified after writing
| the changes from the narrowed window back.

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Vim breaking tmux ?

[Eric Christopherson]

On Sat, Aug 16, 2014, Christopher Whittemore wrote:
 OSX 10.9.4
 
 Not really sure what's going on here, if someone could help me shed some 
 light on the problem it would be much appreciated. 
 
 I recently used homebrew to install tmux, but when using Vim to open files in 
 new panes, terminal's visualizations breaks. [ See attached screen shot ] 
 
 Jumping back into the broken pane causes the text to reload/fix itself. Not 
 really a critical problem, but it's seriously annoying to have to jump 
 through every pane to correct the visualizations every time I open a new file 
 in Vim.
 
 Any suggestions?
 
 Thank you in advance to all who reply!

First, try running tmux and vim with no config options:

tmux -f /dev/null
vim -u NONE

(note that if tmux is already running, it will keep using the config
used by other running sessions; so make sure no tmux is running in order
to start it with /dev/null as a blank config file). See if that fixes
things; if so, we'll hopefully be able to narrow down the problem from
your tmux and vim configs.

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Mapping control-minus and control-pipe

[Eric Christopherson]

On Thu, Aug 7, 2014 at 4:14 AM, Paolo Bolzoni
paolo.bolzoni.br...@gmail.com wrote:
 nnoremap C-\ C-wv
 nnoremap C-_ C-wn

 are close enough, thanks!

 On Wed, Aug 6, 2014 at 11:26 PM, Ben Fritz fritzophre...@gmail.com wrote:
 On Wednesday, August 6, 2014 3:32:03 PM UTC-5, Paolo Bolzoni wrote:
 Dear list,



 I am happy tmux and vim user, but to reduce the mistakes caused

 by muscle memory I would like to setup similar keybindings to the

 two.



 In tmux I use Ctrl-| to split the screen vertically and

 Ctrl-Minus to split horizontally.

I'm curious as to how you mapped those in tmux. They don't have ASCII
character representation, so tmux shouldn't (theoretically) be able to
deal with them at all. Perhaps they map to other ASCII control codes
in your terminal (as is the case for Ben with ^-/^_).




 In vimrc I wrote:



 nnoremap C-Bar C-wv

 nnoremap C-- C-wn



 But it does not work. What is the correct binding?


 See what Vim sees when you enter those keys, and map those instead.

 For example, when I go to insert mode and type CTRL-V to insert the next 
 character literally, then I type CTRL--, I see ^_ which means I should 
 probably map C-_ rather than C--.

 However, I normally get | by pressing SHIFT-\, and CTRL-SHIFT-\ gives me 
 nothing at all in insert mode. Maybe mapping C-\ will work, but possibly 
 CTRL-| is not mappable at all.

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: --remote unknown option argument

[Eric Christopherson]

On Sun, Jul 13, 2014, Mark Volkmann wrote:
 I'm trying to use vim --remote to open a file in vim from a Mac OS X
 terminal window in an existing Vim session running in another terminal
 window. It outputs Unknown option argument: --remote. Is that option not
 supported in non-gui vim on Mac OS X?

Correct -- or rather, it requires compilation with +clientserver;
Apple's bundled Vim is not compiled with that. I'd recommend MacVim,
even if you don't plan on using the GUI.

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Mapping the NERDTree command

[Eric Christopherson]

On Mon, Jun 16, 2014 at 05:06:02AM -0400, Eric Weir wrote:
 
 On Jun 15, 2014, at 9:14 PM, Eric Christopherson echristopher...@gmail.com 
 wrote:
 
  here's no way for Vim to recognize Cmd in the terminal. 
  
  Second, your syntax inside the brackets is wrong. For MacVim, you would use
  
 map A-D-n :NERDTreeToggleCR
 
 Apologies, Eric, and thanks. I should've said i was using MacVim. However, 
 that mapping is not working. 

Does it do anything? Even make a sound? It worked for me.

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Mapping the NERDTree command

[Eric Christopherson]

On Sun, Jun 15, 2014 at 3:20 AM, Eric Weir eew...@bellsouth.net wrote:

 I want to map the NERDTree command to the option-command-n key combination on 
 a Mac keyboard.

 I have this in my .vimrc: map Option-Command-n :NERDTreeToggleCR

 It's not working. What am I doing wrong?

First, that will only work if you're in the MacVim GUI. There's no way
for Vim to recognize Cmd in the terminal. However, at least with
iTerm2, it would be possible to configure the terminal to send a
specific character sequence when you hit that combination of keys;
then you could use that character sequence in a mapping.

Second, your syntax inside the brackets is wrong. For MacVim, you would use

map A-D-n :NERDTreeToggleCR

A-... means alt, which correlates with Opt on a Mac (I believe
M-... for meta would work too). D-... is a MacVim-specific thing
which means the Cmd key. (I'm not sure why D-; maybe because it's
the last letter of command, the first letter already having been
used?)

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ability to undo changes from outside Vim

[Eric Christopherson]

Ah, thanks; that'd be it. undoreload is set by default to 1, and my
file is now over that many lines. I set it to -1 and that made it work.


On Wed, Jun 11, 2014 at 10:27 PM, Ben Fritz fritzophre...@gmail.com wrote:

 On Wednesday, June 11, 2014 5:36:31 PM UTC-5, Eric Christopherson wrote:
  In my vimrc I have
 
set undofile
set undodir=~/.vimundo
  -- thus I am almost always able to undo changes done in Vim even if I
 close a file and reopen it. One other benefit I've enjoyed for a while is
 the behavior where, if I have a file open in Vim, and some program besides
 Vim modifies the file, not only does Vim prompt me about whether I want to
 load the up-to-date version of the file, but even if I do so I can still
 press u to undo the *external* changes. However, today I noticed this isn't
 working anymore on my Windows machine (I will check on my Mac and Linux
 later).
 
 
 
 
  Does anyone know how I can make it behave the old way again?

 Check the help for the 'undoreload' option; perhaps you're hitting the
 limits there.

 Question for the list, :help 'undoreload' says The save only happens when
 this options is negative or when the number of lines is smaller than the
 value of this option.

 Does that mean you can set it to -1 to make it always save without any
 line-number limit?

 --
 --
 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+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Vim and Evil compared. Documentation

[Eric Christopherson]

On Wed, Jun 11, 2014 at 3:13 PM, Rosangela Medeiros da Silva 
rosangelame...@gmail.com wrote:

 Evil automatic documentation is quite good. However, Vim documentation is
 very complete, with examples, and translations to many languages, like
 French and Esperanto. It is trivial to write a lisp function that inserts
 Vim documentation into Evil functions that are placed in the
 evil-commands.el file.

 My question is: Is it illegal to do that, i.e., insert Vim documentation
 into Evil functions, so that Evil users can profit from the effort of Vim
 users?


You're the lawyer here ;)

If you're not going to distribute the pieces of Vim documentation, you can
do anything with it. If you're going to distribute them, e.g. on your web
page (which looks very thorough; good work!), you just need to follow Vim's
license, which is here: 
http://vimdoc.sourceforge.net/htmldoc/uganda.html#license. Basically it's
GPL-compatible (I think version 2 but I'm not sure). Evil is licensed as
GPL3, so there should be little problem (but IANAL).



 In the mean time I am writing a tutorial that I designed for Evil users,
 but can be useful for Vim users too. I am updating it weekly. I will
 appreciate any feedback, corrections, and information about commands that
 work differently in Evil and Vim. The address is

 advocacia.me/en/evil.html

 There is also an evil.org file that can be downloaded from

 advocacia.me/en/evil.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

--- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ability to undo changes from outside Vim

[Eric Christopherson]

In my vimrc I have
  set undofile
  set undodir=~/.vimundo
-- thus I am almost always able to undo changes done in Vim even if I close
a file and reopen it. One other benefit I've enjoyed for a while is the
behavior where, if I have a file open in Vim, and some program besides Vim
modifies the file, not only does Vim prompt me about whether I want to load
the up-to-date version of the file, but even if I do so I can still press u
to undo the *external* changes. However, today I noticed this isn't working
anymore on my Windows machine (I will check on my Mac and Linux later).

Does anyone know how I can make it behave the old way again?

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Migrating from Evil to Vim

[Eric Christopherson]

Hi, Rosangela.


On Sun, Jun 8, 2014 at 4:28 PM, Rosangela Medeiros da Silva 
rosangelame...@gmail.com wrote:

 Hi.
 Excuse me for my poor English and lack of knowledge about computers. I am
 a lawyer. Therefore I have to make a lot of batch text processing:
 pleadings, counselling in e-petions, outline of laws, etc.

 People who sold me the Common Lisp packages for law practice told me that
 the Steel Bank Common Lisp is very fast for text processing, therefore I
 should run the scripts they sold me in this particular brand of Common
 Lisp. They gave me the following explanation about how it works.  In my
 .emacs configuration file there is a small elisp program that install Evil
 and Steel Bank Common Lisp scripting. At the end of this article there is a
 simplified version of my .emacs configuration file and two examples of
 Steel Bank Common Lisp to test them.

 What I would like from the members of this discussion list is the Vim
 equivalent of my .emacs configuration file, so I can run my scripts and
 define new keybindings in Common Lisp.


I guess I'm just wondering why you feel you should switch. Is there
something about Emacs+Evil that isn't working well?

However, since (as far as I can gather from your email) you are just taking
text from Emacs and sending it to an external process (sbcl), this should
be perfectly possible in Vim. If you're using SLIME to achieve some of this
functionality, things become a lot more complicated.


 By the way, I use the C-c p keybinding to change the name of the Common
 Lisp program that I want to run. For instance, if I want to run the
 reverse.lisp program, I type 'reverse.' somewhere on my document:

 reverse.

 Then I press Esc to enter Normal state, place the cursor on the first
 letter of the file name, and press vf.Ctrl-c p and finally d to remove the
 name of the program and exit Visual state.

 The name of the file is removed from the text, and the program I want to
 use is installed in the C-c e keybinding. Now, I write a list and put the
 cursor inside the list and press C-c e to execute the program:

 (badly sing cats)Reversed list:
 (CATS SING BADLY)

 By the way, I use Common Lisp functions in regexps too. That is the reason
 for not using arguments in my functions. An example will make things clear.
 Let us assume that I have a function without argument to convert pinyin to
 Chines ideograms. Let us put this function inside an org-mode SRC block.

 #+BEGIN_SRC emacs-lisp
 (defun fn()
   (cond ((equal (match-string 1) zhong) 中)
 ((equal (match-string 1) hua)  华)
 (t nada)))
 ; :s/\(\[a-z]+\\)/\,(fn)/gc
 #+END_SRC

 After pressing C-c C-c inside the block, I can start converting pinyin to
 Chinese characters. Of course, in the example, there is only two
 characters; since I need hundreds of them, I put the fn function in a file
 and only the code to load it goes into the SRC block.  I tried this in Vim,
 but it refused to accept the function inside the replacement expression. I
 mean, it did not accept \,(fn) in the replacement expression. The reason, I
 suppose is that I did not configure Vim to accept Common Lisp scripts.


As far as I can tell, your fn function is executed as Emacs Lisp rather
than Common Lisp. In any event, though, I would hesitate to use that code
for Chinese, since it can only do a one-to-one mapping of pinyin to hanzi;
your two example words don't even indicate tone, and even with tone
indicated you would have some words that sound the same with different
hanzi.



 That is all. Thank you for helping me. Since Evil is an emulation of Vim,
 I suppose that Vim is vastly superior to Evil. Therefore, I am looking
 forward for receiving the Vim configuration that accept SBCL scripting.


I wouldn't conclude that Vim is *inherently* vastly superior; it's just
that Evil has fewer features at the moment because it hasn't been developed
as long. It is, however, extensible in a way similar to Vim (albeit in a
different scripting language). Again, I wonder if you really need to switch.

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Speed of vim-fugitive in virtualized Windows

[Eric Christopherson]

I use Tim Pope's excellent vim-fugitive for working with Git in Vim. But I
find that when I run it in a Windows 8.1 virtual machine, various
operations are very slow, compared to running it in OS X, Linux, or even
native Windows. I haven't used a lot of its functionality, but one thing
I've noticed in particular that is very slow is :cnext and friends after
loading the revisions to the repository into quickfix with :Glog --. I also
haven't used a lot of Git functionality in Windows, so I don't know if it's
slow in general; but the simple things I do like adding, committing,
branching, getting logs, etc. seem snappy enough.

Does anyone else even experiences this in such environments? I've noticed
slowness in VirtualBox, VMware Fusion, and Parallels (all running on OS X),
but the degree of slowness varies a little between them and between
occasions using the same repository. I haven't done any formal timing, but
my initial impression was that Parallels slowed it down the least; however,
today I'm finding that its behavior is also slow.

And does anyone know what causes this? I know I find that Windows
performance is slower in general in VMs, so it might just be a little
slowness in the MSYS versions of GNU libraries that Git uses, plus a little
slowness in Git, plus a little slowness in Vim, plus a little slowness in
the plugin (which is interpreted, after all); but I'd like to find out
there's something simple that could be done to speed it up.

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Speed of vim-fugitive in virtualized Windows

[Eric Christopherson]

On Sat, May 24, 2014 at 4:50 PM, Eric Christopherson 
echristopher...@gmail.com wrote:

 I haven't done any formal timing, but my initial impression was that
 Parallels slowed it down the least; however, today I'm finding that its
 behavior is also slow.


Correction FYI: VMware Fusion is the one that impacts least on speed of
this particular operation.

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Official Windows build recipe

[Eric Christopherson]

Thanks, but I'm looking for the exact way the official binary is produced
(or as close to it as I can get). I suppose that might be tangential to
fixing the problem I found, however. I guess it would be really great if
the Vim Windows team just released a new binary installer that fixed my bug.

Does this list allow the posting of text attachments?




On Fri, Apr 11, 2014 at 2:12 PM, Marc Weber marco-owe...@gmx.de wrote:

 google: wiki vim build windows eg shows

   http://vim.wikia.com/wiki/Build_Python-enabled_Vim_on_Windows_with_MinGW

 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

 ---
 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+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.