Monday, November 30, 2015

Re: Go to Japanese character

On Thursday, November 19, 2015 at 1:38:00 PM UTC-8, bob beckett wrote:
> I have created a Japanese-English vocabulary list for my personal use.
>
> Oftentimes I want to go to the first non-ASCII character in a line.
>
> Can anyone suggest a way to accomplish this? Maybe a remapping?
>
> Thanks

Ben

Your suggestion works perfectly. Thanks a lot.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How can I join in a group that can communicate immediately like msn?

On 2015年11月14日 23時48分, imlegendlzz@gmail.com wrote:
>I hope that I can communicate with foreigner friend immediately, so I want to join a tech group like Vim.

Join #vim on freenode.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Sunday, November 29, 2015

Re: A vimdiff light colorscheme for a wide range of file color-coding types

On Saturday, November 28, 2015 at 6:35:01 AM UTC-6, Philip Rhoades wrote:
>
> Any suggestions? Should I just start from scratch and build my own?
>

I've never found a colorscheme that I like 100% out of the box.

But you don't need to build your own. Find one that's pretty close to what you want and tweak it as you find issues.

It can help to view the highlight group under the cursor to see what needs tweaking: http://vim.wikia.com/wiki/Identify_the_syntax_highlighting_group_used_at_the_cursor

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Open fold above current line in diff mode

On Saturday, November 28, 2015 at 3:56:25 PM UTC-6, Bram Moolenaar wrote:
> Ben Fritz wrote:
>
> > Diff mode folds huge swaths of a file a lot of the time. So when I
> > want to view some context around a diff, it is very inconvenient to
> > place the cursor on the fold and use zo, because then the spot I was
> > looking at jumps off-screen.
> >
> > So I can do :-1foldopen with my cursor *below* the fold to keep the
> > part of interest right where I want it.
> >
> > But, this doesn't open the fold in both sides of the diff, unlike when I use zo.
> >
> > Is there a better way to show more context in a diff for a *specific*
> > change. I don't want to use zr to unfold *everything*, just the one
> > fold above the current change.
>
> What I usually do: "0b". This means: go to start of the line and back
> one word, thus ending up at the end of the last line in the fold and
> opending that fold. This requires "hor" in 'foldopen'.

Ah, good suggestion! I'll try training myself to do that.

>
> > Also, is this the intended behavior of :foldopen, that it doesn't act
> > on both sides of a diff?
>
> No, the folds in diff mode should be in sync.
>

Good to know. I'll try to see if I can reproduce without my plugins and mappings and such tomorrow.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Saturday, November 28, 2015

Re: Open fold above current line in diff mode

Ben Fritz wrote:

> Diff mode folds huge swaths of a file a lot of the time. So when I
> want to view some context around a diff, it is very inconvenient to
> place the cursor on the fold and use zo, because then the spot I was
> looking at jumps off-screen.
>
> So I can do :-1foldopen with my cursor *below* the fold to keep the
> part of interest right where I want it.
>
> But, this doesn't open the fold in both sides of the diff, unlike when I use zo.
>
> Is there a better way to show more context in a diff for a *specific*
> change. I don't want to use zr to unfold *everything*, just the one
> fold above the current change.

What I usually do: "0b". This means: go to start of the line and back
one word, thus ending up at the end of the last line in the fold and
opending that fold. This requires "hor" in 'foldopen'.

> Also, is this the intended behavior of :foldopen, that it doesn't act
> on both sides of a diff?

No, the folds in diff mode should be in sync.

--
hundred-and-one symptoms of being an internet addict:
148. You find it easier to dial-up the National Weather Service
Weather/your_town/now.html than to simply look out the window.

/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Go to Japanese character

On Mon, Nov 23, 2015 at 10:45 AM, bob beckett <sealbeam01@gmail.com> wrote:
On Thursday, November 19, 2015 at 1:38:00 PM UTC-8, bob beckett wrote:
> I have created a Japanese-English vocabulary list for my personal use.
>
> Oftentimes I want to go to the first non-ASCII character in a line.
>
> Can anyone suggest a way to accomplish this? Maybe a remapping?
>
> Thanks

Sorry it took so long to reply.

Thank you for your suggestion. Unfortunately, it finds all non-ASCII characters in the entire file, and it does not move the cursor to the first Japanese (i.e. non-ASCII) character in the current line.

What I envisioned was some kind of modification of the f(ind) command. But I can't figure it out.

The third parameter to the search function (`:h search()`) is the last line on which to consider a match, and it begins its search at the current cursor position.  So, the following should do what you want:

" ;; = jump to the first non-ASCII char past the cursor on the current line
nn <silent> ;; :cal search('[^\x20-\x7e]', '', line('.'))<CR>

" same thing, but slightly different concept of "ASCII char"
nn <silent> ;; :cal search('[^\x00-\xFF]', '', line('.'))<CR>

It also has the advantage of not messing with the `@/` register (hence no need for `:nohls`).

-- 
Best,
Ben

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: A vimdiff light colorscheme for a wide range of file color-coding types



2015-11-28 15:34 GMT+03:00 Philip Rhoades <phil@pricom.com.au>:
People,

For years I have struggled and spent dozens of hours to find a colorscheme that looks good with simple vim editing for a range of file types eg

  .txt
  .sh
  .xml
  .c
  .rb
  .java
  .rs

etc - that ALSO looks good and READABLE in vimdiff . .

I have tried dozens of schemes and I am about to systematically work my way through hundreds but it would be nice if I can find a colorscheme where someone has already solved the problem:

​Can you list what you remember out of these dozens? Preferably with the comments on why you did not like them: this is needed to avoid (if you have already tested the colorscheme) or receive (if you have not) various "obvious" advices like solarized (which has light variant). Some people may also think that what you consider unreadable is perfectly readable and this will protect you from advices from them.

I personally use wombat256-mod, but this is dark and not light colorscheme.​

 

- I want a normal white background for lines that are the same

and

- readable color combinations where lines / text are different eg yellow is hopeless, purple is unreadable on a coloured background etc

Any suggestions?  Should I just start from scratch and build my own?

Thanks,

Phil.
--
Philip Rhoades

PO Box 896
Cowra  NSW  2794
Australia
E-mail:  phil@pricom.com.au

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

--- You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

A vimdiff light colorscheme for a wide range of file color-coding types

People,

For years I have struggled and spent dozens of hours to find a
colorscheme that looks good with simple vim editing for a range of file
types eg

.txt
.sh
.xml
.c
.rb
.java
.rs

etc - that ALSO looks good and READABLE in vimdiff . .

I have tried dozens of schemes and I am about to systematically work my
way through hundreds but it would be nice if I can find a colorscheme
where someone has already solved the problem:

- I want a normal white background for lines that are the same

and

- readable color combinations where lines / text are different eg yellow
is hopeless, purple is unreadable on a coloured background etc

Any suggestions? Should I just start from scratch and build my own?

Thanks,

Phil.
--
Philip Rhoades

PO Box 896
Cowra NSW 2794
Australia
E-mail: phil@pricom.com.au

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] pyclewn release 2.2

Pyclewn 2.2 has been released at http://pyclewn.sourceforge.net/

Pyclewn is a Python program that allows the use of Vim as a front end to the GNU debugger gdb and the Python debugger pdb.

This release fixes the following bugs:

* Print the return value when the inferior stops after 'finish'.

* Fix Pyclewn failure to start when gdb is configured with ``enable-targets=all``.

* File name completion is now available before gdb has been started. This fixes a regression introduced in 2.1 by the full gdb completion feature.

* Hitting <CR> in the breakpoints window now splits the first window of the current tab loaded with a non-clewn buffer.

* Prevent pip using wheel to install pyclewn on Python 2.7.

--
Xavier

Les Chemins de Lokoti: http://lokoti.alwaysdata.net

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Friday, November 27, 2015

Re: How yank some text to more than one register?



2015-11-27 2:30 GMT+03:00 Tony Mechelynck <antoine.mechelynck@gmail.com>:
On Thu, Nov 26, 2015 at 9:49 AM, Roman <roma.ovc@gmail.com> wrote:
> Hi, is any way to put yanked text with one keystroke, to more than one register? Something like vnoremap y "+y && "ny
> Thank you for the answer.
>


If you can use mappings you can do anything. Maybe something like

    :vnoremap <F5> "+y:let @n = @+<CR>

​Using :let for copying registers may do copying incorrectly: it is never possible to copy blockwise selection using :let and it is never possible to correctly copy text with zero bytes inside. One needs to use

    :call setreg('n', getreg('+', 1, 1), getregtype('+')​)

 

or

    :vnoremap <F5> "+ygv"+n

See
    :help :let-@
    :help expr-register
for the former, and
    :help gv
for the latter.

I would rather not map onto y which is the standard (and IMHO very
useful) yank keybinding, and by default yanks to the default "
register (sometimes called "the unnamed register" though its name is
the double quote).

Best regards,
Tony.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Thursday, November 26, 2015

Re: How yank some text to more than one register?

пятница, 27 ноября 2015 г., 5:30:57 UTC+6 пользователь Tony Mechelynck написал:
> On Thu, Nov 26, 2015 at 9:49 AM, Roman <roma.ovc@gmail.com> wrote:
> > Hi, is any way to put yanked text with one keystroke, to more than one register? Something like vnoremap y "+y && "ny
> > Thank you for the answer.
> >
>
>
> If you can use mappings you can do anything. Maybe something like
>
> :vnoremap <F5> "+y:let @n = @+<CR>
>
> or
>
> :vnoremap <F5> "+ygv"+n
>
> See
> :help :let-@
> :help expr-register
> for the former, and
> :help gv
> for the latter.
>
> I would rather not map onto y which is the standard (and IMHO very
> useful) yank keybinding, and by default yanks to the default "
> register (sometimes called "the unnamed register" though its name is
> the double quote).
>
> Best regards,
> Tony.

Thank you Tony! I will grok it :)

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How yank some text to more than one register?

On Thu, Nov 26, 2015 at 9:49 AM, Roman <roma.ovc@gmail.com> wrote:
> Hi, is any way to put yanked text with one keystroke, to more than one register? Something like vnoremap y "+y && "ny
> Thank you for the answer.
>


If you can use mappings you can do anything. Maybe something like

:vnoremap <F5> "+y:let @n = @+<CR>

or

:vnoremap <F5> "+ygv"+n

See
:help :let-@
:help expr-register
for the former, and
:help gv
for the latter.

I would rather not map onto y which is the standard (and IMHO very
useful) yank keybinding, and by default yanks to the default "
register (sometimes called "the unnamed register" though its name is
the double quote).

Best regards,
Tony.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How yank some text to more than one register?

Hi, is any way to put yanked text with one keystroke, to more than one register? Something like vnoremap y "+y && "ny
Thank you for the answer.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Wednesday, November 25, 2015

Re: "+y in vim put all stuff to "* not to "+

On Wed, Nov 25, 2015 at 5:30 PM, Random832 <random832@fastmail.com> wrote:
> On 2015-11-25, Roman <roma.ovc@gmail.com> wrote:
>> Why vnoremap <C-Insert> "+y in vim visual mode puts all stuff to "* not to "+
>> But "+y in vim working fine. In gvim all working fine.
>
> As I understand it, only x11 gvim makes a distinction between "* and "+. In
> win32, these both refer to the clipboard. In non-GUI vim, neither of them
> exist, and your data is actually in "" (and doing "+p or "*p will both paste
> from "").
>
They both exist in any x11-aware Vim provided that it has contact with
the X server: for instance, in a Vim executable compiled to serve as
either (console) vim and (GUI) gvim on Linux, and running in an xterm
or similar terminal window. It is even possible to compile Vim with
has("x11") but without has("gui"). On Windows, vim.exe and gvim.exe
are different executables, but there both "* and "+ refer to the
Windows clipboard, which is accessible even in Console mode IIRC.

Best regards,
Tony.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: "+y in vim put all stuff to "* not to "+

On 2015-11-25, Roman <roma.ovc@gmail.com> wrote:
> Why vnoremap <C-Insert> "+y in vim visual mode puts all stuff to "* not to "+
> But "+y in vim working fine. In gvim all working fine.

As I understand it, only x11 gvim makes a distinction between "* and "+. In
win32, these both refer to the clipboard. In non-GUI vim, neither of them
exist, and your data is actually in "" (and doing "+p or "*p will both paste
from "").

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: "+y in vim put all stuff to "* not to "+

среда, 25 ноября 2015 г., 13:50:37 UTC+6 пользователь Roman написал:
> Have a nice day to everyone! I have a question:
> Why vnoremap <C-Insert> "+y in vim visual mode puts all stuff to "* not to "+
> But "+y in vim working fine. In gvim all working fine.
> linux gentoo + rxvt-unicode
> clipboard=autoselect,exclude:cons\|linux
> Thank you for answer!

As I found 'send to "+' work only with:
set clipboard=unnamedplus
vnoremap y "+y

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Tuesday, November 24, 2015

"+y in vim put all stuff to "* not to "+

Have a nice day to everyone! I have a question:
Why vnoremap <C-Insert> "+y in vim visual mode puts all stuff to "* not to "+
But "+y in vim working fine. In gvim all working fine.
linux gentoo + rxvt-unicode
clipboard=autoselect,exclude:cons\|linux
Thank you for answer!

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Open fold above current line in diff mode

Diff mode folds huge swaths of a file a lot of the time. So when I want to view some context around a diff, it is very inconvenient to place the cursor on the fold and use zo, because then the spot I was looking at jumps off-screen.

So I can do :-1foldopen with my cursor *below* the fold to keep the part of interest right where I want it.

But, this doesn't open the fold in both sides of the diff, unlike when I use zo.

Is there a better way to show more context in a diff for a *specific* change. I don't want to use zr to unfold *everything*, just the one fold above the current change.

Also, is this the intended behavior of :foldopen, that it doesn't act on both sides of a diff?

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Monday, November 23, 2015

Re: Go to Japanese character

On Mon, Nov 23, 2015 at 8:24 PM, Charles E Campbell
<drchip@campbellfamily.biz> wrote:
> bob beckett wrote:
>> On Thursday, November 19, 2015 at 1:38:00 PM UTC-8, bob beckett wrote:
>>> I have created a Japanese-English vocabulary list for my personal use.
>>>
>>> Oftentimes I want to go to the first non-ASCII character in a line.
>>>
>>> Can anyone suggest a way to accomplish this? Maybe a remapping?
>>>
>>> Thanks
>> Sorry it took so long to reply.
>>
>> Thank you for your suggestion. Unfortunately, it finds all non-ASCII characters in the entire file, and it does not move the cursor to the first Japanese (i.e. non-ASCII) character in the current line.
>>
>> What I envisioned was some kind of modification of the f(ind) command. But I can't figure it out.
>>
> Modify Bob's suggestion: /^[^ -~] (ie. line beginning with non-ascii)
>
> Or, if you're using utf-8:
>
> /^[\u30A0-\u319f] for katakana
> /^[\u3040-\u309f] for hiragana
> [^[\u3040-\u319f] for either katakana or hiragana (since they're
> right next to one another in the utf-8 glyph table)
>
> Regards,
> Chip Campbell

However, due to a limitation in Vim search (just slightly above 256
characters IIRC) it is not possible to search for just any character
anywhere in the whole kanji range — except by the above-mentioned
"anything but" method, which may give false positives. It is even
possible (if you use UTF-8) to exclude the whole of Latin1 (not just
7-bit us-ascii) by searching on
/^[^\x01-\xff]
Or without the ^ outside the [ ] to find non-Latin1 characters even
when not at the start of a line. But you can't exclude much more than
that due to that Vim limitation.

Best regards,
Tony.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Go to Japanese character

bob beckett wrote:
> On Thursday, November 19, 2015 at 1:38:00 PM UTC-8, bob beckett wrote:
>> I have created a Japanese-English vocabulary list for my personal use.
>>
>> Oftentimes I want to go to the first non-ASCII character in a line.
>>
>> Can anyone suggest a way to accomplish this? Maybe a remapping?
>>
>> Thanks
> Sorry it took so long to reply.
>
> Thank you for your suggestion. Unfortunately, it finds all non-ASCII characters in the entire file, and it does not move the cursor to the first Japanese (i.e. non-ASCII) character in the current line.
>
> What I envisioned was some kind of modification of the f(ind) command. But I can't figure it out.
>
Modify Bob's suggestion: /^[^ -~] (ie. line beginning with non-ascii)

Or, if you're using utf-8:

/^[\u30A0-\u319f] for katakana
/^[\u3040-\u309f] for hiragana
[^[\u3040-\u319f] for either katakana or hiragana (since they're
right next to one another in the utf-8 glyph table)

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

Re: Go to Japanese character

On 2015-11-23, bob beckett <sealbeam01@gmail.com> wrote:
> Thank you for your suggestion. Unfortunately, it finds all non-ASCII
> characters in the entire file, and it does not move the cursor to the first
> Japanese (i.e. non-ASCII) character in the current line.

And does what with them, highlights them? Also, It should move the cursor to
the next Japanese character after the cursor, whether it is on the current line
or not. If the highlighting is the only problem, you can run :nohls to clear
it.

Since even the original command was long enough that you would probably want to
put it in a mapping, this can easily be added:

nnoremap f<C-x> /[^ -~]<CR>:nohls<CR>

Obviously if there are none on the current line after the cursor it won't act
exactly like 'f', but it's not clear why you are trying to do this in that
case.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Go to Japanese character

On Thursday, November 19, 2015 at 1:38:00 PM UTC-8, bob beckett wrote:
> I have created a Japanese-English vocabulary list for my personal use.
>
> Oftentimes I want to go to the first non-ASCII character in a line.
>
> Can anyone suggest a way to accomplish this? Maybe a remapping?
>
> Thanks

Sorry it took so long to reply.

Thank you for your suggestion. Unfortunately, it finds all non-ASCII characters in the entire file, and it does not move the cursor to the first Japanese (i.e. non-ASCII) character in the current line.

What I envisioned was some kind of modification of the f(ind) command. But I can't figure it out.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Sunday, November 22, 2015

Re: Question about highlighting all matches of a local variable within a C/C++ subroutine

On Sunday, November 22, 2015 at 4:18:17 PM UTC-5, Richard Mitchell wrote:
> On Sunday, November 22, 2015 at 2:09:13 PM UTC-5, Richard Mitchell wrote:
> > On Sunday, November 22, 2015 at 11:13:41 AM UTC-5, DrChip wrote:
> > > Richard Mitchell wrote:
> >
> > > > I had trouble getting this to work.
> > > >
> > > > The first issue was SaveWinPosn was not defined. I found it in cecutil.vba, but I don't see this being mentioned as a prerequisite.
> > > >
> > > > Currently it doesn't seem to do anything, but hitting 'n' produces:
> > > >
> > > > E486: Pattern not found: \%(\%>0l\%<34l\)&MYSTRING
> > > >
> > > > (where MYSTRING is what was being searched for and does exist in the current C function).
> > > > It looks like 34 is the line after what may be considered the first block as enclosed by {}, but not the block the cursor is currently sitting.
> > > >
> > > > Is there more magic needed or is my environment conflicting?
> > > >
> > > Sorry about the SaveWinPosn problem -- funcsrch was on the wrong list so
> > > it didn't have cecutil.vim bundled with it. My website's version of
> > > funcsrch now has cecutil bundled with it.
> > >
> > > Do the normal mode commands [[ and ][ go to the beginning and ending of
> > > the function your cursor is in? Its possible that your style of coding
> > > prevents vim's method of recognizing beginning-ending of functions from
> > > working, and FuncSrch uses that.
> > >
> > > Regards,
> > > Charles Campbell
> >
> > I started using vi around 30+ years ago and considered myself reasonably competent (as a user), but I did not know about those two mode commands.
> >
> > ][ takes me to the end of the current function, or the next function if already at the end
> > [] takes me to the end of the previous function
> > ]] takes me to the end of the file
> > [[ takes me to the beginning of the file
> >
> > so no, they don't work exactly as you describe, at least [[ does't. I tried vim -u NONE file.c and still got the same behavior. If I have changed the default behavior, it is only because I've loaded someone's plugin with said side-effect. I use vim, I don't write stuff for vim. Obviously I'm prone to getting sucked into "that looks neat, lets try it!" or we wouldn't be having this discussion.
> >
> > Thanks,
> > Richard
>
> I see now, [[ works for:
>
> void func()
> {
> blah;
> }
>
> but not:
>
> void func() {
> blah;
> }
>
> so it is my coding style that breaks this use.

This map fixes it:

:map [[ ][%

All of my functions end with the } in the first column, so ][ takes the cursor to it. % then moves the cursor to the matching {

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Question about highlighting all matches of a local variable within a C/C++ subroutine

On Sunday, November 22, 2015 at 2:09:13 PM UTC-5, Richard Mitchell wrote:
> On Sunday, November 22, 2015 at 11:13:41 AM UTC-5, DrChip wrote:
> > Richard Mitchell wrote:
>
> > > I had trouble getting this to work.
> > >
> > > The first issue was SaveWinPosn was not defined. I found it in cecutil.vba, but I don't see this being mentioned as a prerequisite.
> > >
> > > Currently it doesn't seem to do anything, but hitting 'n' produces:
> > >
> > > E486: Pattern not found: \%(\%>0l\%<34l\)&MYSTRING
> > >
> > > (where MYSTRING is what was being searched for and does exist in the current C function).
> > > It looks like 34 is the line after what may be considered the first block as enclosed by {}, but not the block the cursor is currently sitting.
> > >
> > > Is there more magic needed or is my environment conflicting?
> > >
> > Sorry about the SaveWinPosn problem -- funcsrch was on the wrong list so
> > it didn't have cecutil.vim bundled with it. My website's version of
> > funcsrch now has cecutil bundled with it.
> >
> > Do the normal mode commands [[ and ][ go to the beginning and ending of
> > the function your cursor is in? Its possible that your style of coding
> > prevents vim's method of recognizing beginning-ending of functions from
> > working, and FuncSrch uses that.
> >
> > Regards,
> > Charles Campbell
>
> I started using vi around 30+ years ago and considered myself reasonably competent (as a user), but I did not know about those two mode commands.
>
> ][ takes me to the end of the current function, or the next function if already at the end
> [] takes me to the end of the previous function
> ]] takes me to the end of the file
> [[ takes me to the beginning of the file
>
> so no, they don't work exactly as you describe, at least [[ does't. I tried vim -u NONE file.c and still got the same behavior. If I have changed the default behavior, it is only because I've loaded someone's plugin with said side-effect. I use vim, I don't write stuff for vim. Obviously I'm prone to getting sucked into "that looks neat, lets try it!" or we wouldn't be having this discussion.
>
> Thanks,
> Richard

I see now, [[ works for:

void func()
{
blah;
}

but not:

void func() {
blah;
}

so it is my coding style that breaks this 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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Question about highlighting all matches of a local variable within a C/C++ subroutine

On Sunday, November 22, 2015 at 11:13:41 AM UTC-5, DrChip wrote:
> Richard Mitchell wrote:

> > I had trouble getting this to work.
> >
> > The first issue was SaveWinPosn was not defined. I found it in cecutil.vba, but I don't see this being mentioned as a prerequisite.
> >
> > Currently it doesn't seem to do anything, but hitting 'n' produces:
> >
> > E486: Pattern not found: \%(\%>0l\%<34l\)&MYSTRING
> >
> > (where MYSTRING is what was being searched for and does exist in the current C function).
> > It looks like 34 is the line after what may be considered the first block as enclosed by {}, but not the block the cursor is currently sitting.
> >
> > Is there more magic needed or is my environment conflicting?
> >
> Sorry about the SaveWinPosn problem -- funcsrch was on the wrong list so
> it didn't have cecutil.vim bundled with it. My website's version of
> funcsrch now has cecutil bundled with it.
>
> Do the normal mode commands [[ and ][ go to the beginning and ending of
> the function your cursor is in? Its possible that your style of coding
> prevents vim's method of recognizing beginning-ending of functions from
> working, and FuncSrch uses that.
>
> Regards,
> Charles Campbell

I started using vi around 30+ years ago and considered myself reasonably competent (as a user), but I did not know about those two mode commands.

][ takes me to the end of the current function, or the next function if already at the end
[] takes me to the end of the previous function
]] takes me to the end of the file
[[ takes me to the beginning of the file

so no, they don't work exactly as you describe, at least [[ does't. I tried vim -u NONE file.c and still got the same behavior. If I have changed the default behavior, it is only because I've loaded someone's plugin with said side-effect. I use vim, I don't write stuff for vim. Obviously I'm prone to getting sucked into "that looks neat, lets try it!" or we wouldn't be having this discussion.

Thanks,
Richard

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Question about highlighting all matches of a local variable within a C/C++ subroutine

Richard Mitchell wrote:
> On Saturday, November 21, 2015 at 6:41:12 PM UTC-5, DrChip wrote:
>> John Fishburn wrote:
>>> I know that
>>> .set hlsearch
>>> will highlight all matches of search patterns.
>>>
>>> My question is, can this highlighting be done only for occurrences of a local variable within a C/C++ subroutine? E.g. highlight all occurrences of 'i' that are local to a subroutine but not those outside.
>>>
>> Try funcsrch (get it from
>> http://www.drchip.org/astronaut/vim/index.html#FUNCSRCH)
>>
>> To do what you want:
>>
>> :set hls
>> :FS \<varname\>
>>
>> Regards,
>> Chip Campbell
> I had trouble getting this to work.
>
> The first issue was SaveWinPosn was not defined. I found it in cecutil.vba, but I don't see this being mentioned as a prerequisite.
>
> Currently it doesn't seem to do anything, but hitting 'n' produces:
>
> E486: Pattern not found: \%(\%>0l\%<34l\)&MYSTRING
>
> (where MYSTRING is what was being searched for and does exist in the current C function).
> It looks like 34 is the line after what may be considered the first block as enclosed by {}, but not the block the cursor is currently sitting.
>
> Is there more magic needed or is my environment conflicting?
>
Sorry about the SaveWinPosn problem -- funcsrch was on the wrong list so
it didn't have cecutil.vim bundled with it. My website's version of
funcsrch now has cecutil bundled with it.

Do the normal mode commands [[ and ][ go to the beginning and ending of
the function your cursor is in? Its possible that your style of coding
prevents vim's method of recognizing beginning-ending of functions from
working, and FuncSrch uses that.

Regards,
Charles Campbell

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: C indentation problem for functions with many parameters (one parameter per line)

Peng Yu wrote:

> Hi, The following is the indentation results of some C code in vim. Is
> there a way to fix this problem?
>
> void f(
> int a
> , int a
> , int a
> , int a
> , int a
> , int a
> , int a
> , int a
> , int a
> , int a
> , int a
> , int a
> , int a
> , int a
> , int a
> , int a
> , int a
> , int a
> , int a
> , int a
> , int a
> , int a
> )

set cino+=)30

--
hundred-and-one symptoms of being an internet addict:
125. You begin to wonder how often it REALLY is necessary to get up
and shower or bathe.

/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Question about highlighting all matches of a local variable within a C/C++ subroutine

On Saturday, November 21, 2015 at 6:41:12 PM UTC-5, DrChip wrote:
> John Fishburn wrote:
> > I know that
> > .set hlsearch
> > will highlight all matches of search patterns.
> >
> > My question is, can this highlighting be done only for occurrences of a local variable within a C/C++ subroutine? E.g. highlight all occurrences of 'i' that are local to a subroutine but not those outside.
> >
> Try funcsrch (get it from
> http://www.drchip.org/astronaut/vim/index.html#FUNCSRCH)
>
> To do what you want:
>
> :set hls
> :FS \<varname\>
>
> Regards,
> Chip Campbell

I had trouble getting this to work.

The first issue was SaveWinPosn was not defined. I found it in cecutil.vba, but I don't see this being mentioned as a prerequisite.

Currently it doesn't seem to do anything, but hitting 'n' produces:

E486: Pattern not found: \%(\%>0l\%<34l\)&MYSTRING

(where MYSTRING is what was being searched for and does exist in the current C function).
It looks like 34 is the line after what may be considered the first block as enclosed by {}, but not the block the cursor is currently sitting.

Is there more magic needed or is my environment conflicting?

Thanks!

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Saturday, November 21, 2015

Re: Question about language specific mappings

On Sat, Nov 21, 2015 at 2:50 PM, BPJ <bpj@melroch.se> wrote:
> Den 2015-11-20 kl. 20:20, skrev Tony Mechelynck:
>> These options can be toggled by hitting Ctrl-^ but since that
>> keystroke is hard to find on my Belgian AZERTY keyboard I use the
>> following, which works also in Normal mode:
>>
>> set ims=-1
>> map <F8> :let &l:imi = ! &l:imi<CR>
>> map! <F8> <C-^>
>
> I guess this is some trick to make `<F8>` do two things at once, but I
> haven't managed to understand what `map!` does through reading the help. I
> suspect this can simplify my keymap switching setup but I want to understand
> how it works!
> (Sorry, I haven't used Vim for the prerequisite two decades yet! :-)

:map (with no exclamation mark) is for all the modes where letters
mean functions, movements, etc.: Normal, Visual and Operator-pending.
Also Select mode which is somewhat arbitrarily treated as a submode of
Visual. It might have been more correct to write :nmap instead of :map
above.

:map! is for all the modes where letters are letters which get
inserted: Insert and Command-line. Search (i.e. after / or ?) is
regarded as a submode of Command-line, and Replace is a submode of
Insert. Here :map! is correct since we want the same mapping to be
used in all variations of both Insert and Command-line modes.

I haven't been using Vim for 20 years either. Only 12 years or so, but
intensively, and near the begin I ran the vimtutor which is a quite
good "driving school" for Vim (and nowadays there even exists a
gvimtutor, which didn't yet exist then). After these 12 years (how
fast time passes!) I already feel as if I'd been using it all my life,
it's become easier than using a ballpoint pen.


Best regards,
Tony.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Question about highlighting all matches of a local variable within a C/C++ subroutine

John Fishburn wrote:
> I know that
> .set hlsearch
> will highlight all matches of search patterns.
>
> My question is, can this highlighting be done only for occurrences of a local variable within a C/C++ subroutine? E.g. highlight all occurrences of 'i' that are local to a subroutine but not those outside.
>
Try funcsrch (get it from
http://www.drchip.org/astronaut/vim/index.html#FUNCSRCH)

To do what you want:

:set hls
:FS \<varname\>

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

C indentation problem for functions with many parameters (one parameter per line)

Hi, The following is the indentation results of some C code in vim. Is
there a way to fix this problem?

void f(
int a
, int a
, int a
, int a
, int a
, int a
, int a
, int a
, int a
, int a
, int a
, int a
, int a
, int a
, int a
, int a
, int a
, int a
, int a
, int a
, int a
, int a
)

--
Regards,
Peng

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Question about highlighting all matches of a local variable within a C/C++ subroutine

I know that
.set hlsearch
will highlight all matches of search patterns.

My question is, can this highlighting be done only for occurrences of a local variable within a C/C++ subroutine? E.g. highlight all occurrences of 'i' that are local to a subroutine but not those outside.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Question about language specific mappings

Den 2015-11-20 kl. 20:20, skrev Tony Mechelynck:
> These options can be toggled by hitting Ctrl-^ but since that
> keystroke is hard to find on my Belgian AZERTY keyboard I use the
> following, which works also in Normal mode:
>
> set ims=-1
> map <F8> :let &l:imi = ! &l:imi<CR>
> map! <F8> <C-^>

I guess this is some trick to make `<F8>` do two things at once,
but I haven't managed to understand what `map!` does through
reading the help. I suspect this can simplify my keymap switching
setup but I want to understand how it works!
(Sorry, I haven't used Vim for the prerequisite two decades yet! :-)

Den 2015-11-20 kl. 23:07, skrev Tony Mechelynck:
> On Fri, Nov 20, 2015 at 10:45 PM, Dmitri Vereshchagin
> <dmitri.vereshchagin@gmail.com> wrote:
>> * Tony Mechelynck <antoine.mechelynck@gmail.com> [2015-11-20 23:54]:
>>> N° № U+2116 NUMERO SIGN
>>
>> Thank you. It is very clever. I suppose you use AZERTY keyboard
>> layout. I have ЙЦУКЕН (JCUKEN) keyboard and there is no simple way to
>> input degree sign. So I stick with digraph.
>>
>> --
>> Dmitri Vereshchagin
>
> Yes, my keyboard is a Belgian AZERTY. Remapping "No", wouldn't work,
> at least with my keymap, where it would clash with "Но", a syllable
> commonly found at the beginning of Russian words, or even as a word in
> itself. Maybe there is another character, or character group, which is
> practically never used? On my Belgian keyboard I might use µ or ù but
> not knowing what special characters there are on your JCUKEN keyboard
> I might suggest ъъ because the hard sign is rare (since the 1917
> spelling reform) and though it does happen in Russian text it is never
> doubled.

I have found a solution to such problems which I use in my
keymaps: I designate one or more characters as 'sigils' on
'digraphs', so that I can type that character plus any two
characters to get a special character without worrying about what
the other two characters mean without that sigil/prefix. The
price is that I'll have to hit two keys to type the sigil
character(s) literally. A useful character for that is `&` which
isn't used very often in prose. Thus I have mappings like:


&No № U+2116 NUMERO SIGN
&et & U+0026 AMPERSAND

I'm also in the habit of assigning one ASCII punctuation character
as a prefix for any ASCII character including itself to type a
literal ASCII character. That way I can quickly type an English
word or letter without switching keymaps. That's especially
useful with my IPA (phonetics) keymap where all unadorned [a-z]
characters are unmapped but unadorned [A-Z] map to various special
characters. Sometimes ASCII capitals are used as cover symbols,
e.g. C for "any consonant", which I then can type as `"C` while
`C` alone maps to `ç`. For some odd reason I've chosen the ASCII
double-quote for the literal which in retrospect was a bad choice
since outside the phonetics context `"` isn't exactly an uncommon
character, but it has become ingrained now.

Another useful trick is to use those punctuation characters which
don't normally occur before letters (which have the Unicode
property Terminal_Punctuation) as prefixes

! U+0021 EXCLAMATION MARK
, U+002C COMMA
. U+002E FULL STOP
: U+003A COLON
; U+003B SEMICOLON
? U+003F QUESTION MARK

then you very seldom need to use a prefix to type those characters
literally (in non-program text that is!), and you can use the
doubled character to type the character itself:

!! ! U+0021 EXCLAMATION MARK
,, , U+002C COMMA
.. . U+002E FULL STOP
:: : U+003A COLON
;; ; U+003B SEMICOLON
?? ? U+003F QUESTION MARK

Here is a keymap which uses sigils extensively, perhaps even
excessively. It lets me type all non-decomposing Unicode letters
with the 'Latin' property, plus a bunch of combining marks and
modifier letters, everything a comparative philologist needs and
then some. Notably all ASCII punctuation characters except the
doublequote are mapped to combining diacritics; the actual
punctuation characters must be typed as `"!` etc., which hardly
bothers me any more. Look in the Changelog entry for 8 October
2015 for a description of the system.

<http://git.io/v4p66>

> sometimes when 'imi' is set wrong (0=Latin instead of
> 1=Cyrillic) it happens that I type three or four words before I look
> at the screen and see that they have all been taken literally as Latin
> script.

I usually do the opposite: forgetting to switch back to Latin, so
that I type several English/Swedish words in Greek characters or
with interspersed IPA characters: Ιτ'σ αλλ Γρεεκ το με!
(Indo-European comparative philologists for some reason
transliterate everything except Greek!)

FWIW I have several custom mappings to switch on/between different
keymaps and one to switch off. The `<C-^>` is hard to type on my
keyboard also.
In fact I have a dictionary in .vimrc mapping one-letter
identifiers to keymap names, and a function to setup mappings for
them, like `<F-11>g` for Greek. The dictionary is a global
variable and I have a command to add an entry and rerun the
mapping function.

/bpj

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Friday, November 20, 2015

highlighting matching patterns in C/C++ programs

Is it possible to simultaneously highlight all occurrences of an identifier in a C subroutine? E.g. I want to highlight all occurrences of the variable 'i' in a subroutine, but not occurrences outside the routine.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Question about language specific mappings

On 2015-11-20, Dmitri Vereshchagin <dmitri.vereshchagin@gmail.com> wrote:
> * Tony Mechelynck <antoine.mechelynck@gmail.com> [2015-11-20 23:54]:
>> N° № U+2116 NUMERO SIGN
>
> Thank you. It is very clever. I suppose you use AZERTY keyboard
> layout. I have ЙЦУКЕН (JCUKEN) keyboard and there is no simple way to
> input degree sign. So I stick with digraph.

Speaking of digraphs, both # and № have (Ctrl-K) digraphs: Nb and N0,
respectively. That may be simpler than trying to alter keymaps.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Question about language specific mappings

On Fri, Nov 20, 2015 at 10:45 PM, Dmitri Vereshchagin
<dmitri.vereshchagin@gmail.com> wrote:
> * Tony Mechelynck <antoine.mechelynck@gmail.com> [2015-11-20 23:54]:
>> N° № U+2116 NUMERO SIGN
>
> Thank you. It is very clever. I suppose you use AZERTY keyboard
> layout. I have ЙЦУКЕН (JCUKEN) keyboard and there is no simple way to
> input degree sign. So I stick with digraph.
>
> --
> Dmitri Vereshchagin

Yes, my keyboard is a Belgian AZERTY. Remapping "No", wouldn't work,
at least with my keymap, where it would clash with "Но", a syllable
commonly found at the beginning of Russian words, or even as a word in
itself. Maybe there is another character, or character group, which is
practically never used? On my Belgian keyboard I might use µ or ù but
not knowing what special characters there are on your JCUKEN keyboard
I might suggest ъъ because the hard sign is rare (since the 1917
spelling reform) and though it does happen in Russian text it is never
doubled.

Best regards,
Tony.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Question about language specific mappings

* Tony Mechelynck <antoine.mechelynck@gmail.com> [2015-11-20 23:54]:
> N° № U+2116 NUMERO SIGN

Thank you. It is very clever. I suppose you use AZERTY keyboard
layout. I have ЙЦУКЕН (JCUKEN) keyboard and there is no simple way to
input degree sign. So I stick with digraph.

--
Dmitri Vereshchagin

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Question about language specific mappings

* 'Andy Wokula' via vim_use <vim_use@googlegroups.com> [2015-11-20 20:16]:
> Apparently the keymap script is sourced after ftplugin and syntax scripts,
> and after BufEnter. I think I'd go with
>
> " ~/.vim/after/ftplugin/markdown.vim
> augroup MarkdownKeymapFix
> au! InsertEnter <buffer> lunmap <buffer> #|au! MarkdownKeymapFix
> augroup End

Thank you for clarification and working solution.

--
Dmitri Vereshchagin

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Question about language specific mappings

On Fri, Nov 20, 2015 at 9:23 PM, Dmitri Vereshchagin
<dmitri.vereshchagin@gmail.com> wrote:
> Thank you Tony. But the question is how to disable one particular
> mapping provided by keymap script.
>
> The problem is that keymap I am using maps number sign `#' to numero
> sign `№'. The former is much more useful for me and the latter I can
> input using digraph. So I would like to disable only this particular
> mapping from entire keymap.
>
> I guess that there is always possibility to copy keymap script to
> ~/.vim/keymap and edit it. But is there any other ways to do what
> I want?
>
> --
> Dmitri Vereshchagin

In that case, I think Andy's autocommand might work; but I would copy
the keymap script to ~/.vim/keymap, give it another name, change its
b:keymap_name setting accordingly, and give that particular keymapping
another {lhs}, maybe N° (capital N followed by the degree sign). The
downside of this particular {lhs} is that you won't see a capital N
(or whatever it is lmapped to) appear until after a timeout, a cursor
move, or after you follow it by either a character other than °, or by
going out of Insert mode. In my own "russian-phonetic" keymap I have
this exact mapping, as set by the following line:

N° № U+2116 NUMERO SIGN

and I hardly even notice that when I hit the N key (to get a Cyrillic
Н 'en') the Н doesn't appear immediately. Maybe I type too fast for
that: sometimes when 'imi' is set wrong (0=Latin instead of
1=Cyrillic) it happens that I type three or four words before I look
at the screen and see that they have all been taken literally as Latin
script. (I am currently slowly compiling a Russian-French dictionary,
and that kind of text of course requires constant switching between
alphabets.)


Best regards,
Tony.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Question about language specific mappings

Thank you Tony. But the question is how to disable one particular
mapping provided by keymap script.

The problem is that keymap I am using maps number sign `#' to numero
sign `№'. The former is much more useful for me and the latter I can
input using digraph. So I would like to disable only this particular
mapping from entire keymap.

I guess that there is always possibility to copy keymap script to
~/.vim/keymap and edit it. But is there any other ways to do what
I want?

--
Dmitri Vereshchagin

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Question about language specific mappings

On Thu, Nov 19, 2015 at 11:23 PM, Dmitri Vereshchagin
<dmitri.vereshchagin@gmail.com> wrote:
> More precisely question is about unmapping. I am using keymap to edit
> texts in Russian. In my vimrc I have
>
> set keymap=russian-jcukenwin
> set iminsert=0
> set imsearch=-1
>
> When langmap mappings are enabled it translates `#' to `№' as expected.
> It is not very useful in markdown files. So I put
>
> lunmap <buffer> #
>
> in ~/.vim/after/ftplugin/markdown.vim. Then strange things begin to
> happen. When I open markdown document from running vim it shouts
>
> E31: No such mapping
>
> and points on that line. But after that mapping exists. When I start
> to edit markdown from command line everything is fine.
>
> Using autocommand instead of script in "after" directory leads to the
> same.
>
> The exact question is how to properly unmap this kind of mapping?
> Thanks for any help.
>
> --
> Dmitri Vereshchagin


Language-mappings (and keymaps) are disabled in Insert mode when the
local option 'iminsert' is set to 0. In search mode, it depends on
'imsearch' (also buffer-local) which when set to -1 falls back to
'iminsert' or when set to 0 disables search-mode language-mappings
(and keymaps).

These options can be toggled by hitting Ctrl-^ but since that
keystroke is hard to find on my Belgian AZERTY keyboard I use the
following, which works also in Normal mode:

set ims=-1
map <F8> :let &l:imi = ! &l:imi<CR>
map! <F8> <C-^>

I also use different values for the Cursor and lCursor highlight
groups, so the cursor tells me by its colour whether keymaps are
enabled; and my custom statusline includes a %k item so I know which
keymap (if any) is enabled in which window.

See
:help 'iminsert'
:help 'imsearch'
:help i_CTRL-^
:help c_CTRL-^
:help 'guicursor'
:help lCursor
:help 'statusline'


Best regards,
Tony.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Bulk] Question about language specific mappings

Am 19.11.2015 um 23:23 schrieb Dmitri Vereshchagin:
> More precisely question is about unmapping. I am using keymap to edit
> texts in Russian. In my vimrc I have
>
> set keymap=russian-jcukenwin
> set iminsert=0
> set imsearch=-1
>
> When langmap mappings are enabled it translates `#' to `№' as expected.
> It is not very useful in markdown files. So I put
>
> lunmap <buffer> #
>
> in ~/.vim/after/ftplugin/markdown.vim. Then strange things begin to
> happen. When I open markdown document from running vim it shouts
>
> E31: No such mapping
>
> and points on that line. But after that mapping exists. When I start
> to edit markdown from command line everything is fine.
>
> Using autocommand instead of script in "after" directory leads to the
> same.
>
> The exact question is how to properly unmap this kind of mapping?
> Thanks for any help.

Apparently the keymap script is sourced after ftplugin and syntax scripts,
and after BufEnter. I think I'd go with

" ~/.vim/after/ftplugin/markdown.vim
augroup MarkdownKeymapFix
au! InsertEnter <buffer> lunmap <buffer> #|au! MarkdownKeymapFix
augroup End

--
Andy

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Thursday, November 19, 2015

Re: Go to Japanese character

Hi bob,

On Thursday, 2015-11-19 11:20:26 -0800, bob beckett wrote:

> Oftentimes I want to go to the first non-ASCII character in a line.

/[^ -~]

Searches for a character not in the range from 0x20 space to 0x7E tilde.
Assuming you don't use control characters or 0x7F delete ;-)

Eike

--
OpenPGP/GnuPG encrypted mail preferred in all private communication.
Key "ID" 0x65632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A
Better use 64-bit 0x6A6CD5B765632D3A here is why: https://evil32.com/
Care about Free Software, support the FSFE https://fsfe.org/support/?erack
Use LibreOffice! https://www.libreoffice.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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Question about language specific mappings

More precisely question is about unmapping. I am using keymap to edit
texts in Russian. In my vimrc I have

set keymap=russian-jcukenwin
set iminsert=0
set imsearch=-1

When langmap mappings are enabled it translates `#' to `№' as expected.
It is not very useful in markdown files. So I put

lunmap <buffer> #

in ~/.vim/after/ftplugin/markdown.vim. Then strange things begin to
happen. When I open markdown document from running vim it shouts

E31: No such mapping

and points on that line. But after that mapping exists. When I start
to edit markdown from command line everything is fine.

Using autocommand instead of script in "after" directory leads to the
same.

The exact question is how to properly unmap this kind of mapping?
Thanks for any help.

--
Dmitri Vereshchagin

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Go to Japanese character

I have created a Japanese-English vocabulary list for my personal use.

Oftentimes I want to go to the first non-ASCII character in a line.

Can anyone suggest a way to accomplish this? Maybe a remapping?

Thanks

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Wednesday, November 18, 2015

Re: vim: register * and + missing in ubuntu1404 server

I said:
> ... gpm mouse support ... you still don't get a separate "* and "+

Random832 wrote:>
> Why not? gpm has a selection and can be used to paste between virtual
> consoles or in non-gpm apps. Does it not expose it to applications?

I imagine it does, but no-one has taken the trouble. gpm isn't very active.

Regards, John Little

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: vim: register * and + missing in ubuntu1404 server

John Little <John.B.Little@gmail.com> writes:
> Maybe you're thinking of gpm mouse support. Install the package gpm,
> and with set mouse=a in your .vimrc, a middle click does a paste, but
> from the unnamed register; you still don't get a separate "* and "+
> AFAICS.

Why not? gpm has a selection and can be used to paste between virtual
consoles or in non-gpm apps. Does it not expose it to applications?

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: vim: register * and + missing in ubuntu1404 server

On Wednesday, November 18, 2015 at 5:15:31 PM UTC+13, ping wrote:
...
> I recently switch from ubuntu desktop to ubuntu server , both are 14.04.
> and I couldn't find the register * and +.
...
> although I'm a console vim user...

vim on unices uses X for the clipboard and selection. If no X server is found, I think the * and + become synonyms for the unnamed register, and not shown in the :registers display.

Maybe you're thinking of gpm mouse support. Install the package gpm, and with
set mouse=a in your .vimrc, a middle click does a paste, but from the unnamed register; you still don't get a separate "* and "+ AFAICS. If you want to copy outside of vim then paste in it,
set mouse=
or
set mouse=nvc
then in insert mode vim won't see the middle click, and you'll get gpm's selection pasted.

For completeness, if there is an X server running on the machine where you're using the console, you can

export DISPLAY=:0

to get vim to use it, but the default setting for the 'clipboard' option includes "exclude:cons\|linux" which explicitly turns that off.

HTH, John

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Disable all autointending a part of the simplest one

Yes, the problem was I had to activate filetype indent for some
plugin and I never disabled it, so the value of indentexpr was
changed.

Thanks a lot!

On Tue, Nov 17, 2015 at 5:55 PM, Gary Johnson <garyjohn@spocom.com> wrote:
> On 2015-11-17, Paolo Bolzoni wrote:
>> Dear list,
>>
>> I would like to disable all the "smart" auto indenting. I just want
>> the cursor to align to the previous line non space character. I will
>> press tab or << to fix in the case it is wrong.
>>
>> I set this lines from the wiki in the ~/.vimrc, but it is not enough.
>>
>> set autoindent
>> set nocindent
>> set nosmartindent
>> set indentexpr=
>>
>> What should I check? Am I missing some other settings?
>
> If you have filetype detection enabled (e.g., by "filetype on"),
> filetype indent plugins may set some of those automatically. Try
> putting this in your ~/.vimrc as well:
>
> filetype indent off
>
> See
>
> :help :filetype-indent-off
>
> HTH,
> Gary
>
> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Tuesday, November 17, 2015

vim: register * and + missing in ubuntu1404 server

experts:

I recently switch from ubuntu desktop to ubuntu server , both are 14.04.
and I couldn't find the register * and +.
this seems happened twice (whenever I change a system) and looks quite annoying.
I couldn't find a working solution.

I have all necessary vim modules/apps installed.

ping@ubuntu47-3:~$ dpkg -l | grep vim
ii  vim                                       2:7.4.052-1ubuntu3                                  amd64        Vi IMproved - enhanced vi editor
ii  vim-common                                2:7.4.052-1ubuntu3                                  amd64        Vi IMproved - Common files
ii  vim-gnome                                 2:7.4.052-1ubuntu3                                  amd64        Vi IMproved - enhanced vi editor - with GNOME2 GUI
ii  vim-gtk                                   2:7.4.052-1ubuntu3                                  amd64        Vi IMproved - enhanced vi editor - with GTK2 GUI
ii  vim-gui-common                            2:7.4.052-1ubuntu3                                  all          Vi IMproved - Common GUI files
ii  vim-runtime                               2:7.4.052-1ubuntu3                                  all          Vi IMproved - Runtime files
ii  vim-tiny                                  2:7.4.052-1ubuntu3                                  amd64        Vi IMproved - enhanced vi editor - compact version


my current vim version:

VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jan  2 2014 19:39:47)
Included patches: 1-52
Compiled by buildd@
Huge version with GTK2-GNOME GUI.  Features included (+) or not (-):
+acl             +cmdline_compl   +diff            +find_in_path    +keymap          +modify_fname    +mouse_xterm     +profile         -sniff           +termresponse    +vreplace        -xterm_save
+arabic          +cmdline_hist    +digraphs        +float           +langmap         +mouse           +multi_byte      +python          +startuptime     +textobjects     +wildignore      +xpm
+autocmd         +cmdline_info    +dnd             +folding         +libcall         +mouseshape      +multi_lang      -python3         +statusline      +title           +wildmenu
+balloon_eval    +comments        -ebcdic          -footer          +linebreak       +mouse_dec       -mzscheme        +quickfix        -sun_workshop    +toolbar         +windows
+browse          +conceal         +emacs_tags      +fork()          +lispindent      +mouse_gpm       +netbeans_intg   +reltime         +syntax          +user_commands   +writebackup
++builtin_terms  +cryptv          +eval            +gettext         +listcmds        -mouse_jsbterm   +path_extra      +rightleft       +tag_binary      +vertsplit       +X11
+byte_offset     +cscope          +ex_extra        -hangul_input    +localmap        +mouse_netterm   +perl            +ruby            +tag_old_static  +virtualedit     -xfontset
+cindent         +cursorbind      +extra_search    +iconv           +lua             +mouse_sgr       +persistent_undo +scrollbind      -tag_any_white   +visual          +xim
+clientserver    +cursorshape     +farsi           +insert_expand   +menu            -mouse_sysmouse  +postscript      +signs           +tcl             +visualextra     +xsmp_interact
+clipboard       +dialog_con_gui  +file_in_path    +jumplist        +mksession       +mouse_urxvt     +printer         +smartindent     +terminfo        +viminfo         +xterm_clipboard
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
  system gvimrc file: "$VIM/gvimrc"
    user gvimrc file: "$HOME/.gvimrc"
2nd user gvimrc file: "~/.vim/gvimrc"
    system menu file: "$VIMRUNTIME/menu.vim"
  fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK  -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-  
pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/       
libpng12 -I/usr/include/harfbuzz   -pthread -DORBIT2=1 -D_REENTRANT -I/usr/include/libgnomeui-2.0 -I/usr/include/libart-2.0 -I/usr/include/gconf/2 -I/usr/include/gnome-keyring-1 -I/usr/include/libgnome-2. 
0 -I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/gtk-2.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/x86_64-linux-gnu/gnome-vfs-2.0/include -I/   
usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/orbit-2.0 -I/usr/include/libbonobo-2.0 -I/usr/include/ 
bonobo-activation-2.0 -I/usr/include/libxml2 -I/usr/include/pango-1.0 -I/usr/include/gail-1.0 -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/atk-1.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/   
include -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/libpng12     -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -          
U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1     -I/usr/include/tcl8.6  -D_REENTRANT=1  -D_THREAD_SAFE=1  -D_LARGEFILE64_SOURCE=1
Linking: gcc   -L. -Wl,-Bsymbolic-functions -Wl,-z,relro -rdynamic -Wl,-export-dynamic -Wl,-E  -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -o vim   -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2. 
0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfontconfig -lgobject-2.0 -lglib-2.0 -lfreetype     -lgnomeui-2 -lSM -lICE -lbonoboui-2 -lgnomevfs-2 -lgnomecanvas-2 -lgnome-2 -     
lpopt -lbonobo-2 -lbonobo-activation -lORBit-2 -lart_lgpl_2 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfontconfig -lfreetype -   
lgconf-2 -lgthread-2.0 -lgmodule-2.0 -lgobject-2.0 -lglib-2.0   -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE  -lm -ltinfo -lnsl  -lselinux  -lacl -lattr -lgpm -ldl  -L/usr/lib -llua5.2 -Wl,-E  -fstack-  
protector -L/usr/local/lib  -L/usr/lib/perl/5.18/CORE -lperl -ldl -lm -lpthread -lcrypt -L/usr/lib/python2.7/config-x86_64-linux-gnu -lpython2.7 -lpthread -ldl -lutil -lm -Xlinker -export-dynamic -Wl,-O1 -
Wl,-Bsymbolic-functions  -L/usr/lib/x86_64-linux-gnu -ltcl8.6 -ldl -lz -lpthread -lieee -lm -lruby-1.9.1 -lpthread -lrt -ldl -lcrypt -lm  -L/usr/lib


there is one thing I found tricky:

initially I am with "Huge version without GUI". even after I install vim-gnome and vim-gui-common it is still not change.

eventually I tried to uninstall the vim and vim-gnome and reinstall again, then I got current "Huge version with GUI" version.

that actually resolved one another issue "E319: Sorry, the command is not available in this version". but the register * and + simply doesn't appear!

although I'm a console vim user, I could have this feature available in my old system and it is important.

please shed some light of why this happened and how to solve this. my guess is I still miss some ubuntu modules since I'm now on a "server" instead of "desktop" version.

regards
ping


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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.