Re: visual mode popup menu ?

Andy, hi

I think it does work if I add the exe normal gv in the popup func.

cool!

thx,

-m

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/bd143494-6e0f-453c-82aa-173306fa258e%40googlegroups.com.

Re: visual mode popup menu ?

Andy, hi again

I was thinking of something like -

    call popup_menu(g:menulist, #{ title: 'MyMenuTitle:', filter: 'MyFilter', callback: 'MyCallback' })

I would highlight some code and then press a key to trigger the popup menu and select some option from that menu,

but when the menu pops I didn't want to lose the visual highlighting.

Perhaps I can do something like exe normal gv as part of the popup ??

I wasn't thinking of vmenu - is that available at the cursor location ?  I will read up on it.

take care,

-m

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/29ce641c-b422-4023-99e5-1bf3eb84aaf0%40googlegroups.com.

Re: I get "Press ENTER or type command to continue" but not when using symlinks.

On Thu, 30 Apr 2020 at 21:21, Christian Brabandt <cblists@256bit.org> wrote:
>
>
> Hi Ottavio,
> can you please test with the latest version? I believe there were some
> patches that fixes such a problem.

I've just compiled from the latest Github sources (8.2.0671), and
unfortunately I have the same problem.

oc@e130:~/vim/vim-8.2.0671$ ./src/vim --version
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Apr 30 2020 22:19:30)
Included patches: 1-671
Compiled by oc@e130
Huge version without GUI. Features included (+) or not (-):
+acl -farsi +mouse_sgr +tag_binary
+arabic +file_in_path -mouse_sysmouse -tag_old_static
+autocmd +find_in_path +mouse_urxvt -tag_any_white
+autochdir +float +mouse_xterm -tcl
-autoservername +folding +multi_byte +termguicolors
-balloon_eval -footer +multi_lang +terminal
+balloon_eval_term +fork() -mzscheme +terminfo
-browse +gettext +netbeans_intg +termresponse
++builtin_terms -hangul_input +num64 +textobjects
+byte_offset +iconv +packages +textprop
+channel +insert_expand +path_extra +timers
+cindent +ipv6 -perl +title
-clientserver +job +persistent_undo -toolbar
-clipboard +jumplist +popupwin +user_commands
+cmdline_compl +keymap +postscript +vartabs
+cmdline_hist +lambda +printer +vertsplit
+cmdline_info +langmap +profile +virtualedit
+comments +libcall -python +visual
+conceal +linebreak -python3 +visualextra
+cryptv +lispindent +quickfix +viminfo
+cscope +listcmds +reltime +vreplace
+cursorbind +localmap +rightleft +wildignore
+cursorshape -lua -ruby +wildmenu
+dialog_con +menu +scrollbind +windows
+diff +mksession +signs +writebackup
+digraphs +modify_fname +smartindent -X11
-dnd +mouse -sound -xfontset
-ebcdic -mouseshape +spell -xim
+emacs_tags +mouse_dec +startuptime -xpm
+eval -mouse_gpm +statusline -xsmp
+ex_extra -mouse_jsbterm -sun_workshop -xterm_clipboard
+extra_search +mouse_netterm +syntax -xterm_save
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
defaults file: "$VIMRUNTIME/defaults.vim"
fall-back for $VIM: "/usr/local/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -g -O2
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc -L/usr/local/lib -Wl,--as-needed -o vim -lm -ltinfo -ldl


--
Ottavio Caruso

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAEJNuHy202EOZz%2Baq8_o41ES9X8Kdsm4WJf-C-FvDaQzGFZePQ%40mail.gmail.com.

Re: I get "Press ENTER or type command to continue" but not when using symlinks.

Hi Ottavio,
can you please test with the latest version? I believe there were some
patches that fixes such a problem.

Thanks,
Christian

On Do, 30 Apr 2020, 'Ottavio Caruso' via vim_use wrote:

> Hi,
>
> this is another "Press ENTER or type command to continue " question,
> but this time it's a bit different and bit bizarre. My vim version at
> the end of this message.
>
> I have a directory with some symbolic links:
>
> $ ls -al docs/man-todo docs/tips
> lrwxrwxrwx 1 oc oc 46 Feb 3 08:27 docs/man-todo ->
> /home/oc/Documents/BSD-Cert/man-todo-final.txt
> lrwxrwxrwx 1 oc oc 56 Apr 30 19:40 docs/tips ->
> /home/oc/Documents/BSD-Cert/fortunes/freebsd-tips-rework
>
> When I launch either of the files (in /home/oc/Documents/BSD-Cert/) with:
>
> vim -u NONE /home/oc/Documents/BSD-Cert/man-todo-final.txt
> or:
> vim -u NONE /home/oc/Documents/BSD-Cert/fortunes/freebsd-tips-rework
>
> I get "Press ENTER or type command to continue" every time I enter ex
> mode, but I never get it when I use:
>
> vim -u NONE /home/oc/docs/man-todo
> or:
> vim -u NONE /home/oc/docs/tips
>
> This doesn't happen at all if I omit the "-u NONE" argument.
>
> The only thing that could explain this is that the original directory
> is on a vfat partitions, whereas the symlinks are on a ext4 partition.
>
> Any clue?
>
> $ vim --version
> VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Apr 3 2020 09:57:11)
> Included patches: 1-303
> Modified by morr@NetBSD.org
> Compiled by oc@e130
> Huge version without GUI. Features included (+) or not (-):
> +acl -farsi -mouse_sysmouse -tag_old_static
> +arabic +file_in_path +mouse_urxvt -tag_any_white
> +autocmd +find_in_path +mouse_xterm -tcl
> +autochdir +float +multi_byte +termguicolors
> -autoservername +folding +multi_lang +terminal
> -balloon_eval -footer -mzscheme +terminfo
> +balloon_eval_term +fork() +netbeans_intg +termresponse
> -browse +gettext +num64 +textobjects
> -builtin_terms -hangul_input +packages +textprop
> +byte_offset +iconv +path_extra +timers
> +channel +insert_expand -perl +title
> +cindent +job +persistent_undo -toolbar
> -clientserver +jumplist +popupwin +user_commands
> -clipboard +keymap +postscript +vartabs
> +cmdline_compl +lambda +printer +vertsplit
> +cmdline_hist +langmap +profile +virtualedit
> +cmdline_info +libcall -python +visual
> +comments +linebreak -python3 +visualextra
> +conceal +lispindent +quickfix +viminfo
> +cryptv +listcmds +reltime +vreplace
> +cscope +localmap +rightleft +wildignore
> +cursorbind -lua -ruby +wildmenu
> +cursorshape +menu +scrollbind +windows
> +dialog_con +mksession +signs +writebackup
> +diff +modify_fname +smartindent -X11
> +digraphs +mouse -sound -xfontset
> -dnd -mouseshape +spell -xim
> -ebcdic +mouse_dec +startuptime -xpm
> +emacs_tags -mouse_gpm +statusline -xsmp
> +eval -mouse_jsbterm -sun_workshop -xterm_clipboard
> +ex_extra +mouse_netterm +syntax -xterm_save
> +extra_search +mouse_sgr +tag_binary
> system vimrc file: "/usr/pkg/etc/vimrc"
> user vimrc file: "$HOME/.vimrc"
> 2nd user vimrc file: "~/.vim/vimrc"
> user exrc file: "$HOME/.exrc"
> defaults file: "$VIMRUNTIME/defaults.vim"
> fall-back for $VIM: "/usr/pkg/share/vim"
> Compilation: cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include
> -I/usr/pkg/include/ncurses -O2 -I/usr/include
> -I/usr/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
> Linking: cc -L/usr/pkg/lib -Wl,-R/usr/pkg/lib -L/usr/local/lib
> -Wl,--as-needed -o vim -lm -lnsl -lncurses -liconv -ldl
>

Mit freundlichen Grüßen
Christian
--
Wenn man einen Zeugen Jehovas mit einem Atheisten kreuzt, dann
kommt jemand raus, der völlig sinnlos bei einem klingelt.
-- Jürgen Becker

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20200430202107.GJ17557%40256bit.org.

I get "Press ENTER or type command to continue" but not when using symlinks.

Hi,

this is another "Press ENTER or type command to continue " question,
but this time it's a bit different and bit bizarre. My vim version at
the end of this message.

I have a directory with some symbolic links:

$ ls -al docs/man-todo docs/tips
lrwxrwxrwx 1 oc oc 46 Feb 3 08:27 docs/man-todo ->
/home/oc/Documents/BSD-Cert/man-todo-final.txt
lrwxrwxrwx 1 oc oc 56 Apr 30 19:40 docs/tips ->
/home/oc/Documents/BSD-Cert/fortunes/freebsd-tips-rework

When I launch either of the files (in /home/oc/Documents/BSD-Cert/) with:

vim -u NONE /home/oc/Documents/BSD-Cert/man-todo-final.txt
or:
vim -u NONE /home/oc/Documents/BSD-Cert/fortunes/freebsd-tips-rework

I get "Press ENTER or type command to continue" every time I enter ex
mode, but I never get it when I use:

vim -u NONE /home/oc/docs/man-todo
or:
vim -u NONE /home/oc/docs/tips

This doesn't happen at all if I omit the "-u NONE" argument.

The only thing that could explain this is that the original directory
is on a vfat partitions, whereas the symlinks are on a ext4 partition.

Any clue?

$ vim --version
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Apr 3 2020 09:57:11)
Included patches: 1-303
Modified by morr@NetBSD.org
Compiled by oc@e130
Huge version without GUI. Features included (+) or not (-):
+acl -farsi -mouse_sysmouse -tag_old_static
+arabic +file_in_path +mouse_urxvt -tag_any_white
+autocmd +find_in_path +mouse_xterm -tcl
+autochdir +float +multi_byte +termguicolors
-autoservername +folding +multi_lang +terminal
-balloon_eval -footer -mzscheme +terminfo
+balloon_eval_term +fork() +netbeans_intg +termresponse
-browse +gettext +num64 +textobjects
-builtin_terms -hangul_input +packages +textprop
+byte_offset +iconv +path_extra +timers
+channel +insert_expand -perl +title
+cindent +job +persistent_undo -toolbar
-clientserver +jumplist +popupwin +user_commands
-clipboard +keymap +postscript +vartabs
+cmdline_compl +lambda +printer +vertsplit
+cmdline_hist +langmap +profile +virtualedit
+cmdline_info +libcall -python +visual
+comments +linebreak -python3 +visualextra
+conceal +lispindent +quickfix +viminfo
+cryptv +listcmds +reltime +vreplace
+cscope +localmap +rightleft +wildignore
+cursorbind -lua -ruby +wildmenu
+cursorshape +menu +scrollbind +windows
+dialog_con +mksession +signs +writebackup
+diff +modify_fname +smartindent -X11
+digraphs +mouse -sound -xfontset
-dnd -mouseshape +spell -xim
-ebcdic +mouse_dec +startuptime -xpm
+emacs_tags -mouse_gpm +statusline -xsmp
+eval -mouse_jsbterm -sun_workshop -xterm_clipboard
+ex_extra +mouse_netterm +syntax -xterm_save
+extra_search +mouse_sgr +tag_binary
system vimrc file: "/usr/pkg/etc/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
defaults file: "$VIMRUNTIME/defaults.vim"
fall-back for $VIM: "/usr/pkg/share/vim"
Compilation: cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include
-I/usr/pkg/include/ncurses -O2 -I/usr/include
-I/usr/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: cc -L/usr/pkg/lib -Wl,-R/usr/pkg/lib -L/usr/local/lib
-Wl,--as-needed -o vim -lm -lnsl -lncurses -liconv -ldl

--
Ottavio Caruso

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAEJNuHzCSQUOcRXX1yC7OvnZp4xd4jY4A1SgpT-w-A_h5AYt0w%40mail.gmail.com.

Re: visual mode popup menu ?

Am 27.04.2020 um 02:37 schrieb M Kelly:
> Hi,
>
> Is there a way to be in visual mode with some text highlighted and
> popup a menu and keep the highlighted text during and after the popup
> menu ?
>
> thx, -m

I would think it could make sense for some popup menu entries, but not all ...
how about an example?

You can override specific menu entries.

For what to override, see
:vmenu PopUp
:split +/PopUp/ $VIMRUNTIME/menu.vim

For example, original:
:vnoremenu 1.30 PopUp.&Copy "+y
modified (see vimrc below) (do not modify in-place):
:vnoremenu PopUp.&Copy "+ygv

" ------------------------------------------------
" in the vimrc ... more work for delayed execution
augroup KellyVimrc
augroup END

au! KellyVimrc VimEnter * call s:OverrideMenu()

func! s:OverrideMenu()
vnoremenu PopUp.&Copy "+ygv
" ... more ...
endfunc

"" for reloading ...
"if !has('vim_starting')
" doau <nomodeline> KellyVimrc VimEnter
"endif


--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/5EAAF40C.80905%40yahoo.de.

Re: Help: ctags in vim ?

Kunal Chauhan wrote:
> 1. I have added simple a new function to my source dir and running the
> ctags - R but still at new functions tag is not working.?
>
>
> 2. At each time i opened my source code i need to execute ctags again ?
>
> 3. How Can I use  ctags and cscope while I have already opened my file
> in vim.
>
1: As I understand things, you haven't compiled your code (yet). Simple
syntax errors, typically caught by a compiler, can occasionally cause
problems for ctags.  Assuming that you've gotten rid of your "tags"
folder so that the ctags can successfully generate a "tags" file, try
running ctags on your C files one at a time.  Does that work (ie. tags
are produced)?  Note that each invocation of ctags will wipe out the
previous work, so this is not a suggestion of how to generate all the
tags you want, rather a way to find what files are causing issues for ctags.

2. Only when you feel the need -- ie. when you've installed new
functions, changed functions' argument lists/types, etc.  Of course,
ctags can tag more than just functions -- local typedefs, etc.

3. When in vim, and editing one of your source files, use  :tag
FUNCTIONNAME , for example, with FUNCTIONNAME being one of your
functions' names.  That will exercise your ctags feature (assuming you
have +tag_binary as a feature).
  For cscope, first check that you have +cscope as a feature (vim
--version).  If you do, then read up on  :help cscope.

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/f990da08-a941-496b-446e-331fd4f256b1%40drchip.org.

Re: Help: ctags in vim ?

On 2020-04-29, Kunal Chauhan wrote:
> If we talk about gnu global is it far better than cscope.

It's better at most things; worse at some.

It does a better job than cscope at understanding C++ files. Cscope
apparently understands only C; some C++ constructs confuse it.

There was a bug in cscope some years ago that prevented it from
identifying certain forms of function definitions used by some of my
co-workers. I wrote to the maintainer about it. He tried to fix it
but said that the parser became many times larger and didn't think
the fix was worth that.

Cscope has some features that GNU Global lacks, such as finding
functions that are called by the current function.

GNU Global is almost a drop-in replacement for cscope. There is
a gtags.vim plugin that comes with GNU Global. On Ubuntu, it's
/usr/share/doc/global/examples/gtags.vim.gz. There is also
a tutorial at https://www.gnu.org/software/global/globaldoc_toc.html
that explains how to use GNU Global with Vim, either with or without
the plugin. I recommend reading the tutorial.

> If yes how can i install and use it on my ubuntu machine . 

$ sudo apt install global

In your project directory (wherever you normally execute ctags), to
generate the database:

$ gtags

In vim:

:set csprg=gtags-cscope
:cs add GTAGS

Then use it as you would cscope.

Regards,
Gary

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

---
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20200429182718.GC29220%40phoenix.

Re: Help: ctags in vim ?

If we talk about gnu global is it far better than cscope.

If yes how can i install and use it on my ubuntu machine . 

On 29 Apr 2020 21:10, "Gary Johnson" <garyjohn@spocom.com> wrote:

On 2020-04-29, Kunal Chauhan wrote:
> 1. I have added simple a new function to my source dir and running the ctags -
> R but still at new functions tag is not working.?

I don't know why that is.  Ctags usually "just works" without any
fussing so I don't have much experience fixing ctags problems.
I don't have enough information about your situation to make any
further guesses about what might be wrong.

> 2. At each time i opened my source code i need to execute ctags again ?

No.  You need to execute ctags again only after you have made
a change to your source code.

> 3. How Can I use  ctags and cscope while I have already opened my file in vim.

First, make sure that the working directory of the current vim
window is the directory that should contain your tags and cscope.out
files.  If you started vim in that directory, and you haven't
executed any :cd or :lcd commands, and 'autochdir' is off (the
default), then any window in vim should be using the correct working
directory.  You can check with the following command:

    :pwd

For ctags, simply execute the following command:

    :!ctags -R

For cscope, execute the following two commands:

    :!cscope -b -R
    :cs add

I think those last two commands are right.  I haven't used cscope in
years.  I've been using GNU Global instead, and I have plugins that
do a lot of stuff automatically so that I don't have to think about
it.

You can find out more about Vim's cscope commands here:

    :help cscope

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.

To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20200429153936.GB29220%40phoenix.

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CACEFAc26ZtT039Tn5K0D5Y-idu-Y9B0Jr%3D2hWHRywe9s5LrZGA%40mail.gmail.com.

Re: Help: ctags in vim ?

On 2020-04-29, Kunal Chauhan wrote:
> 1. I have added simple a new function to my source dir and running the ctags -
> R but still at new functions tag is not working.?

I don't know why that is. Ctags usually "just works" without any
fussing so I don't have much experience fixing ctags problems.
I don't have enough information about your situation to make any
further guesses about what might be wrong.

> 2. At each time i opened my source code i need to execute ctags again ?

No. You need to execute ctags again only after you have made
a change to your source code.

> 3. How Can I use  ctags and cscope while I have already opened my file in vim.

First, make sure that the working directory of the current vim
window is the directory that should contain your tags and cscope.out
files. If you started vim in that directory, and you haven't
executed any :cd or :lcd commands, and 'autochdir' is off (the
default), then any window in vim should be using the correct working
directory. You can check with the following command:

:pwd

For ctags, simply execute the following command:

:!ctags -R

For cscope, execute the following two commands:

:!cscope -b -R
:cs add

I think those last two commands are right. I haven't used cscope in
years. I've been using GNU Global instead, and I have plugins that
do a lot of stuff automatically so that I don't have to think about
it.

You can find out more about Vim's cscope commands here:

:help cscope

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20200429153936.GB29220%40phoenix.

Re: Help: ctags in vim ?

1. I have added simple a new function to my source dir and running the ctags - R but still at new functions tag is not working.?

2. At each time i opened my source code i need to execute ctags again ?

3. How Can I use  ctags and cscope while I have already opened my file in vim.

On 28 Apr 2020 11:19 p.m., "Gary Johnson" <garyjohn@spocom.com> wrote:

On 2020-04-28, Kunal Chauhan wrote:
> Hi Team,
>
> below is my ctags related question in vim :
>
> Q1: I added new functions to some code repo and run the below command
>      For generating the ctags I used "ctags -R * " at vim but it is not
> working.
>     still I did not compile my code yet.

The asterisk (*) is not necessary.  You can execute just

    $ ctags -R

> Q2: Also my tags folder is not showing by date update in current source
> directory.

The tags do not go into a folder; they go into a regular file.  If
you have a folder named tags, you will need to either rename that
folder or tell ctags and vim to use a different name for the tags
file.

If you are executing "ctags -R *" or "ctags -R" within vim, try
executing it outside of vim, at the shell prompt.  That may let you
see any warnings more easily.

> Q3: is ctags require the compilation of code for navigation.

No, ctags does not require that the code be compiled.

However, some programs generate C source files from files written in
other languages, such as YACC.  You may need to compile your code
before ctags will find symbols defined in generated files.

Regards,
Gary

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

---
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20200428174824.GA29220%40phoenix.

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CACEFAc1MoK3Ysh%3Dg0pZzYwgjD4RZmAjHZ%3DBtMqrN%2Bz9jHo2G2A%40mail.gmail.com.

Fsync failed

Back in 2008, a topic https://groups.google.com/d/msg/vim_use/mJCoXui54To/tx7N6FBfU-EJ suggested that the person get a bigger hard disk after an "Fsync failed" error -- even though there was probably enough disk space.

I had the same problem on my laptop running Windows 7 SP1. I was trying to save a file on an external hard drive (F:). I'd recently had a weird error where the Audacity sound editor couldn't open one of its ".au" files... and I also couldn't copy that file using Windows Explorer. That made me suspect disk errors.

I opened Windows Explorer, chose Properties, choose the Tools tab, and clicked on "Error checking". First I only checked the box "Automatically fix file system errors". Then I decided to re-run the check with "Scan for and attempt recovery of bad sectors". That found some problems, but re-running vim still gave the error. So, because vim was making its temporary files on the C: system drive, I did the same checks on the C: drive. It found more problems.

After all of these checks, vim is able to save files again.

By the way, I don't have the latest version of vim (which I'm using in a Cygwin terminal window). But if the latest version doesn't give more info than just "Fsync failed" -- for instance, errno information (translated into English or other spoken languages, not just the errno number) -- that would be nice!

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/ba1560de-25f6-4f3a-b65b-1c18d1bfd3f8%40googlegroups.com.

Re: Help can anybody tell me my search string background color need to be change

On 2020-04-28 18:22, Kunal Chauhan wrote:
> , I have tried just with : hi Search ctermbg=LightBlue" it works as
> initially I tried with verbose command
> but I have puted in my .vimrc it is only showing yellow background
> and white text as I search by "/text" in vim

I suspect your vimrc sets your colorscheme after you explicitly set

:hi Search …

That means that your setting gets overridden by your colorscheme.

This is why I recommended forking your favorite color-scheme into,
say, ~/.vim/colors/kunal.vim and then making the modifications there.
Then you can change your vimrc to have

colorscheme kunal

for whatever colors you prefer.

-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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20200428152937.21e82af1%40bigbox.attlocal.net.

Re: Help: ctags in vim ?

On 2020-04-28, Kunal Chauhan wrote:
> Hi Team,
>
> below is my ctags related question in vim :
>
> Q1: I added new functions to some code repo and run the below command
>      For generating the ctags I used "ctags -R * " at vim but it is not
> working.
>     still I did not compile my code yet.

The asterisk (*) is not necessary. You can execute just

$ ctags -R

> Q2: Also my tags folder is not showing by date update in current source
> directory.

The tags do not go into a folder; they go into a regular file. If
you have a folder named tags, you will need to either rename that
folder or tell ctags and vim to use a different name for the tags
file.

If you are executing "ctags -R *" or "ctags -R" within vim, try
executing it outside of vim, at the shell prompt. That may let you
see any warnings more easily.

> Q3: is ctags require the compilation of code for navigation.

No, ctags does not require that the code be compiled.

However, some programs generate C source files from files written in
other languages, such as YACC. You may need to compile your code
before ctags will find symbols defined in generated files.

Regards,
Gary

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

---
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20200428174824.GA29220%40phoenix.

Help: ctags in vim ?

Hi Team,

below is my ctags related question in vim :

Q1: I added new functions to some code repo and run the below command

     For generating the ctags I used "ctags -R * " at vim but it is not working.

    still I did not compile my code yet.

Q2: Also my tags folder is not showing by date update in current source directory.

Q3: is ctags require the compilation of code for navigation.

Thanks

Kunal

--

Thanks with Regards!

Kunal Chauhan

Mob:09813614826

Mob:08860397903

E-mail:atkunalchauhan@gmail.com

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

---
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CACEFAc1JN4o_%3DoSE-GLXGWwKhECRQzo1MM3O_fJRx2TL9t2Vsg%40mail.gmail.com.

Re: Help can anybody tell me my search string background color need to be change

Hi 

, I have tried just with  : hi Search ctermbg=LightBlue" it works as initially I tried with verbose command

but  I have puted in my .vimrc it is only showing yellow background and white text as I search by "/text" in vim 

On Tue, Apr 28, 2020 at 12:56 AM Tim Chase <vim@tim.thechases.com> wrote:

On 2020-04-27 10:57, Gary Johnson wrote:
> The Search highlight setting that Tim gave you should have
> set the foreground to black.  It does for me.

...modulo my fat-fingered typo:

  guifgi=black

should have been

  guifg=black

-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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20200427142613.4cbadfe7%40bigbox.attlocal.net.

--

Thanks with Regards!

Kunal Chauhan

Mob:09813614826

Mob:08860397903

E-mail:atkunalchauhan@gmail.com

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

---
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CACEFAc12kkLHoT8BTYGiThBnj%2BOzS%3DLLUzA82HgEvxO78Wkbfw%40mail.gmail.com.

Re: Help can anybody tell me my search string background color need to be change

`Hi 

, I have tried just with  : hi Search ctermbg=LightBlue" it works as initially I tried with verbose command

but  I have puted in my .vimrc it is only showing yellow background and white text as I search by "/text" in vim 

On Tue, Apr 28, 2020 at 12:56 AM Tim Chase <vim@tim.thechases.com> wrote:

On 2020-04-27 10:57, Gary Johnson wrote:
> The Search highlight setting that Tim gave you should have
> set the foreground to black.  It does for me.

...modulo my fat-fingered typo:

  guifgi=black

should have been

  guifg=black

-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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20200427142613.4cbadfe7%40bigbox.attlocal.net.

--

Thanks with Regards!

Kunal Chauhan

Mob:09813614826

Mob:08860397903

E-mail:atkunalchauhan@gmail.com

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

---
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CACEFAc36TuNG7%2BsWc1SkKDQjFj677ig%2BXLNR2VrwMhi_roiFnA%40mail.gmail.com.

Re: Help can anybody tell me my search string background color need to be change

On 2020-04-27 10:57, Gary Johnson wrote:
> The Search highlight setting that Tim gave you should have
> set the foreground to black. It does for me.

...modulo my fat-fingered typo:

guifgi=black

should have been

guifg=black

-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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20200427142613.4cbadfe7%40bigbox.attlocal.net.

Re: Help can anybody tell me my search string background color need to be change

On 2020-04-27, Kunal Chauhan wrote:
> Also I have noticed right now "verbose set hlsearch" is working when
> separately opening file but when I use cscope -R and from there I entered in
> file there it is not working ?

I would think that once you set 'hlsearch', it would stay set until
you explicitly changed it. Perhaps some plugin is setting it to
off. If you add the question mark (?) to that command as I wrote
a moment ago, you should see what set 'hlsearch' to off. So, after
you execute your cscope command, execute

:verbose set hlsearch?

with the question mark included. That should tell you what set
'hlsearch' to off.

Regards,
Gary

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

---
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20200427180454.GF28061%40phoenix.

Re: Help can anybody tell me my search string background color need to be change

On 2020-04-27, Kunal Chauhan wrote:

> On Mon, Apr 27, 2020 at 8:50 PM Gary Johnson wrote:
>
> On 2020-04-27, Kunal Chauhan wrote:
> > Hi  tim,
> >
> > It is not working for me. 
> > this is giving error "hi Search term=reverse ctermbg=yellow ctermfg=black
> guibg
> > =yellow guifgi=black  " iillegal argument last one argument I corrected 
> > but still it is not working no change on my vim editor.
> >  1.I am using mobax term and under which I am using vim.
> > 2. my vim background color is black and foreground text is white.
> > 3. I search the text , then cursor come on text found and then press
> shift +* 
> > but it did not highligh the whole word only first character is
> highlighted.
>
> What is your 'hlsearch' setting?
>
>     :verbose set hlsearch?
>
> It defaults to off but must be on for highlighting to be applied to
> highlight the entire text of a search match.  See
>
>     :help 'hlsearch'
>
> HTH,
> Gary

(I took the liberty of reformatting your post from top-posting to
bottom-posting style so that I could read it more easily.)

> 1. when I do :verbose set hlsearch  , it gives or highlight all
> the string with background to yellow and foreground white is all
> search strings.

The command I wrote included the question mark (?) at the end.

:verbose set hlsearch?

That command will tell you the current setting of 'hlsearch' and
where it was last set.

I don't understand why the foreground of your search highlighting is
white. The Search highlight setting that Tim gave you should have
set the foreground to black. It does for me.

> 2. help hlsearch // what to see in it ,i am not able to get points
> from help ?

I just added that for reference, so that you could read more about
the 'hlsearch' option if you wanted to.

I don't completely understand the problem. What do want to see when
you search and what are you seeing instead? Also, what are the
results of these commands:

:hi Search
:version

Regards,
Gary

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

---
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20200427175717.GE28061%40phoenix.

Re: Help can anybody tell me my search string background color need to be change

Also I have noticed right now "verbose set hlsearch" is working when separately opening file but when I use cscope -R and from there I entered in file there it is not working ?

On Mon, Apr 27, 2020 at 9:42 PM Kunal Chauhan <atkunalchauhan@gmail.com> wrote:

1. when I do :verbose set hlsearch  , it gives or highlight all the string with background to yellow and foreground white is all search strings.

2. help hlsearch // what to see in it ,i am not able to get points from help ?

On Mon, Apr 27, 2020 at 8:50 PM Gary Johnson <garyjohn@spocom.com> wrote:

On 2020-04-27, Kunal Chauhan wrote:
> Hi  tim,
>
> It is not working for me. 
> this is giving error "hi Search term=reverse ctermbg=yellow ctermfg=black guibg
> =yellow guifgi=black  " iillegal argument last one argument I corrected 
> but still it is not working no change on my vim editor.
>  1.I am using mobax term and under which I am using vim.
> 2. my vim background color is black and foreground text is white.
> 3. I search the text , then cursor come on text found and then press shift +* 
> but it did not highligh the whole word only first character is highlighted.

What is your 'hlsearch' setting?

    :verbose set hlsearch?

It defaults to off but must be on for highlighting to be applied to
highlight the entire text of a search match.  See

    :help 'hlsearch'

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20200427151936.GD28061%40phoenix.

--

Thanks with Regards!

Kunal Chauhan

Mob:09813614826

Mob:08860397903

E-mail:atkunalchauhan@gmail.com

--

Thanks with Regards!

Kunal Chauhan

Mob:09813614826

Mob:08860397903

E-mail:atkunalchauhan@gmail.com

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

---
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CACEFAc10i0dijASLsTRiU2udJKSuSDN1RMfsMnHgVLCPvPqeaQ%40mail.gmail.com.

Re: Help can anybody tell me my search string background color need to be change

1. when I do :verbose set hlsearch  , it gives or highlight all the string with background to yellow and foreground white is all search strings.

2. help hlsearch // what to see in it ,i am not able to get points from help ?

On Mon, Apr 27, 2020 at 8:50 PM Gary Johnson <garyjohn@spocom.com> wrote:

On 2020-04-27, Kunal Chauhan wrote:
> Hi  tim,
>
> It is not working for me. 
> this is giving error "hi Search term=reverse ctermbg=yellow ctermfg=black guibg
> =yellow guifgi=black  " iillegal argument last one argument I corrected 
> but still it is not working no change on my vim editor.
>  1.I am using mobax term and under which I am using vim.
> 2. my vim background color is black and foreground text is white.
> 3. I search the text , then cursor come on text found and then press shift +* 
> but it did not highligh the whole word only first character is highlighted.

What is your 'hlsearch' setting?

    :verbose set hlsearch?

It defaults to off but must be on for highlighting to be applied to
highlight the entire text of a search match.  See

    :help 'hlsearch'

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20200427151936.GD28061%40phoenix.

--

Thanks with Regards!

Kunal Chauhan

Mob:09813614826

Mob:08860397903

E-mail:atkunalchauhan@gmail.com

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

---
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CACEFAc1cQ2cttYYwkRftnzc_LenHenMR5rfS36Xu-5smM%3Dmghw%40mail.gmail.com.

Re: Help can anybody tell me my search string background color need to be change

On 2020-04-27, Kunal Chauhan wrote:
> Hi  tim,
>
> It is not working for me. 
> this is giving error "hi Search term=reverse ctermbg=yellow ctermfg=black guibg
> =yellow guifgi=black  " iillegal argument last one argument I corrected 
> but still it is not working no change on my vim editor.
>  1.I am using mobax term and under which I am using vim.
> 2. my vim background color is black and foreground text is white.
> 3. I search the text , then cursor come on text found and then press shift +* 
> but it did not highligh the whole word only first character is highlighted.

What is your 'hlsearch' setting?

:verbose set hlsearch?

It defaults to off but must be on for highlighting to be applied to
highlight the entire text of a search match. See

:help 'hlsearch'

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20200427151936.GD28061%40phoenix.

Re: Help can anybody tell me my search string background color need to be change

On Mon, Apr 27, 2020 at 3:15 PM Kunal Chauhan <atkunalchauhan@gmail.com> wrote:
>
> Hi tim,
>
> It is not working for me.
> this is giving error "hi Search term=reverse ctermbg=yellow ctermfg=black guibg=yellow guifgi=black " iillegal argument last one argument I corrected
> but still it is not working no change on my vim editor.
> 1.I am using mobax term and under which I am using vim.
> 2. my vim background color is black and foreground text is white.
> 3. I search the text , then cursor come on text found and then press shift +* but it did not highligh the whole word only first character is highlighted.

There are two highlight settings which might be involved: one (Search)
for all matches for the latest pattern, and another one (IncSearch)
for the next match for the pattern you are typing between hitting / or
? and the corresponding <Enter>. To see how they are set on your Vim,
and where (if anywhere) those settings were defined, use

:verbose exe "hi Search" | hi IncSearch

When I do this after starting "vim -u DEFAULTS", the answer (in Vim 8.2.646) is

Search xxx term=reverse ctermbg=11 guibg=Yellow
IncSearch xxx term=reverse cterm=reverse gui=reverse

With my usual vimrc and my homemade colorscheme the answer in gvim is

Search xxx term=reverse ctermfg=0 ctermbg=14 guibg=Yellow
Last set from ~/.vim/colors/almost-default.vim line 22
IncSearch xxx term=reverse cterm=reverse gui=reverse
Last set from ~/.vim/colors/almost-default.vim line 22

In both cases both search-related highlights are set the way I want them to be.

See also
:help :colorscheme
:view $VIMRUNTIME/colors/README.txt
:help :highlight (which is two long sections, numbered 13 and
14 in that helpfile)

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAJkCKXs-YdZr2xU5QvYGw5gFXHTFPrARk7rqEXQW_CNTxG5tfA%40mail.gmail.com.

Re: Help can anybody tell me my search string background color need to be change

Hi  tim,

It is not working for me. 

this is giving error "hi Search term=reverse ctermbg=yellow ctermfg=black guibg=yellow guifgi=black  " iillegal argument last one argument I corrected 

but still it is not working no change on my vim editor.

 1.I am using mobax term and under which I am using vim.

2. my vim background color is black and foreground text is white.

3. I search the text , then cursor come on text found and then press shift +*  but it did not highligh the whole word only first character is highlighted.

On Mon, Apr 27, 2020 at 5:47 PM Tim Chase <vim@tim.thechases.com> wrote:

On 2020-04-27 04:00, Kunal Chauhan wrote:
> I search text and then press shift * but the string is not properly
> highlighted the background color I want to change.

I'm not sure which colorscheme you're using, but I created my own
(based on an existing one) and set the colors I wanted in it. So you
would have something like

  hi Search term=reverse ctermbg=yellow ctermfg=black guibg=yellow guifgi=black

adjusting your colors as you see fit (I believe the default is
black-on-yellow).

-tim

--

Thanks with Regards!

Kunal Chauhan

Mob:09813614826

Mob:08860397903

E-mail:atkunalchauhan@gmail.com

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

---
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CACEFAc0BO40hJ2K2LXPvDA8uUBQ41hxENpwaMFK%2B_y6aMkUZuw%40mail.gmail.com.

Re: Help can anybody tell me my search string background color need to be change

On 2020-04-27 04:00, Kunal Chauhan wrote:
> I search text and then press shift * but the string is not properly
> highlighted the background color I want to change.

I'm not sure which colorscheme you're using, but I created my own
(based on an existing one) and set the colors I wanted in it. So you
would have something like

hi Search term=reverse ctermbg=yellow ctermfg=black guibg=yellow guifgi=black

adjusting your colors as you see fit (I believe the default is
black-on-yellow).

-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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20200427071712.0253336c%40bigbox.attlocal.net.

Help can anybody tell me my search string background color need to be change

hi team,

I search text and then press shift * but the string is not properly highlighted the background color I want to change.

Thanks

kunal 

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/85dafc60-c0f1-464a-b342-5eaec9c2baf1%40googlegroups.com.

help: vim search highlight color change

Hi team,

please help me to change the color of the search sting as i press shift *

--

Thanks with Regards!

Kunal Chauhan

Mob:09813614826

Mob:08860397903

E-mail:atkunalchauhan@gmail.com

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

---
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CACEFAc1cAZoCgdqp943dRQnf7GDaji9E3YeTHm_ezbAsD4JT7w%40mail.gmail.com.

visual mode popup menu ?

Hi,

Is there a way to be in visual mode with some text highlighted and popup a menu and keep the highlighted text during and after the popup menu ?

thx,

-m

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/2c64134b-229e-421d-b1c9-0aef4a40bd6e%40googlegroups.com.

Re: Override a plugin setting in ftplugin/ directory?

On Sun, Apr 26, 2020 at 10:20:10AM -0700, DwigtArmyOfChampions wrote:
>I don't personally care for noignorecase, so I would like to override that particular setting with "set ignorecase". How do I do that? If I run :scriptnames on a Drupal file, I see that this file gets executed much later than my .vimrc file, so I don't think I can use .vimrc for this. While I could edit the actual ftplugin/drupal.vim file itself, that creates an inconsistency between the original version and my version, so if the original programmer releases an updated version, I will have to make this same change all over again. What is the correct way to fix this?

Put it in ~/.vim/after/ftplugin/php.vim (or drupal.vim, if that's how that plugin works). Files in the after directory get sourced later. See :help after-directory.

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20200426181554.GA22923%40rainslide.net.

Re: Format of persistent history undofiles

Brian Lew wrote:

> I was wondering if there is any documentation about the format of the
> persistent history undofiles generated when the undofile option is set.
>
> I am looking to read them in programmatically (outside of vim) and noticed
> that they are in a binary format.
>
> Any information would be greatly appreciated!

There is no documentation other than the source code.

The format is private to Vim, it's not supposed to be used in any other
way. However, since existing undo files must be readable by future
versions of Vim, they can be expected to be backwards compatible.

--
hundred-and-one symptoms of being an internet addict:
26. You check your mail. It says "no new messages." So you check it again.

/// 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202004261741.03QHff6X005313%40masaka.moolenaar.net.

Override a plugin setting in ftplugin/ directory?

I'm using Vim 7. I downloaded and enabled a plugin that enhances syntax for drupal files. In the ftplugin/drupal.vim file of the plugin, I see the following code:

if &ft =~ '\<php\>'

setl no ignorecase

endif


I don't personally care for noignorecase, so I would like to override that particular setting with "set ignorecase". How do I do that? If I run :scriptnames on a Drupal file, I see that this file gets executed much later than my .vimrc file, so I don't think I can use .vimrc for this. While I could edit the actual ftplugin/drupal.vim file itself, that creates an inconsistency between the original version and my version, so if the original programmer releases an updated version, I will have to make this same change all over again. What is the correct way to fix this?

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/d4e64d8b-b3a0-453d-a5a0-271b2d20733a%40googlegroups.com.

Re: installing vim plug on linux

Matthew Pritchard wrote:

> Hello i am wanting to install vim plug on linux. I understand that vim
> plug installs to the autoload directory but I am unsure what this is
> exaclty. When I enter vim --version in terminal it shows that my vimrc
> file is in the following directory. [...] Is one of these the autoload
> directory? If not where is the autoload directory. If not where is it? Do
> I have to create it? How?

Between this mailing list and comp.editors this is your fourth post asking
this same question. Have you followed the suggestions that I and others have
posted for you? If so, what were the results?

(It's considered rude to post the same question again and again, especially
if other people are posting responses and you're ignoring them. It clutters
the list/group and makes it difficult for anyone with the same question to
find an answer. If someone's suggestion doesn't work for you, reply to their
post and describe what you did and what happened.)

Benjamin

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/k9g74smu.nisv8a%40bdesham.net.

Re: installing vim plug on linux

On 2020-04-25, Matthew Pritchard wrote:
> Hello i am wanting to install vim plug on linux. I understand that vim plug
> installs to the autoload directory but I am unsure what this is exaclty.
> When I enter vim --version in terminal it shows that my vimrc file is in the
> following directory.
>  
> system vimrc file: "$VIM/vimrc"
>  user vimrc file: "$HOME/.vimrc"
>  2nd user vimrc file: "~/.vim/vimrc"
>  user exrc file: "$HOME/.exrc"
>   defaults file: "$VIMRUNTIME/defaults.vim"
>   fall-back for $VIM: "/usr/share/vim"
>
> Is one of these the autoload directory? If not where is the autoload directory.
> If not where is it? Do I have to create it? How?

The autoload directory into which you should install a plugin is
~/.vim/autoload. You can create it with this command, executed at
your shell prompt:

$ mkdir -p ~/.vim/autoload

Remember never to install your own files into any directory under
$VIMRUNTIME as you may lose them when you update Vim.

Regards,
Gary

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

---
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20200425223407.GA28061%40phoenix.

Format of persistent history undofiles

Hi All,

I was wondering if there is any documentation about the format of the persistent history undofiles generated when the undofile option is set.

I am looking to read them in programmatically (outside of vim) and noticed that they are in a binary format.

Any information would be greatly appreciated!

Thanks!

Brian

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/b19175d1-ddf4-40b7-8632-a64fea6eaa2e%40googlegroups.com.

installing vim plug on linux

Hello i am wanting to install vim plug on linux. I understand that vim plug installs to the autoload directory but I am unsure what this is exaclty.

When I enter vim --version in terminal it shows that my vimrc file is in the following directory.

 

system vimrc file: "$VIM/vimrc"
 user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
 user exrc file: "$HOME/.exrc"
  defaults file: "$VIMRUNTIME/defaults.vim"
  fall-back for $VIM: "/usr/share/vim"

Is one of these the autoload directory? If not where is the autoload directory. If not where is it? Do I have to create it? How?

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

---
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/27285e0d-bacc-4af3-b397-ad36ead47f2f%40googlegroups.com.

Vim: Windows clipboard paste

Hi

 

I'm new to this group, so hope I get things right.

 

I have been in the habit of using right click to insert text from the clipboard. I am almost invariably in a DOS window.

 

It turns out that certain characters (some, maybe all) \x80-\x9f get translated on the fly to escape sequences. If the attempt is to input the clipboard material this fails at the first escape sequence.

 

It turns out that Vim has an alternative "*P which seems to work (delivering the codes with the high bit set rather than the escape sequences). The right click works in the GUI Vim.

 

I also built myself a getclip, which outputs the clipboard material to STDOUT, which can be piped or redirected.

 

regards – Chris Willis

Re: Changing the scope of 'diff' to something more granular?

On 2020-04-25 15:08, Paul wrote:
> On Fri, Apr 24, 2020 at 04:09:48PM -0500, Tim Chase wrote:
> >While this is functional (and less bad within a tmux session), is
> >it possible to narrow the scope of a :vimdiff to a vim-tab so that
> >I can have a single vim session with multiple file-diff pairs
> >within?
>
> Unless I'm misunderstanding, why don't you open the new diff pair
> in a new tab?

Well dang. That does work. I misread/misunderstood the text at

:help 'diff'

which says that the setting is "local to window". In my
(mis-conceived) tests, opening a new vim window (:sp) from a diff'ed
window resulted in a windo that had 'diff' set, leading me to
(mis-)understand "window" as a vim-session not a vim-window. Had I
properly tested, I would have noticed that after a ":sp" on a diffed
window, I could then

:set nodiff

on one of those and it was in fact scoped to a vim-window not a
vim-session.

Reading up at ":help start-vimdiff" it does indeed say that "Diffs
are local to the current tab page" which is exactly what I wanted
and just failed to find/understand.

Thanks for setting me straight!

-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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20200425094128.5a09da0c%40bigbox.attlocal.net.

Re: Changing the scope of 'diff' to something more granular?

On Fri, Apr 24, 2020 at 04:09:48PM -0500, Tim Chase wrote:
>While this is functional (and less bad within a tmux session), is it
>possible to narrow the scope of a :vimdiff to a vim-tab so that I can
>have a single vim session with multiple file-diff pairs within?

Unless I'm misunderstanding, why don't you open the new diff pair in a new tab?

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20200425140812.GA10298%40rainslide.net.

Changing the scope of 'diff' to something more granular?

I have a couple files that changed and can diff any pair of them with

$ vim old-a.txt new-a.txt

which works as expected. However, if I try to diff old-a/new-a and
also try to :diffsplit old-b/new-b, it compares *all* of those files.
Which is also expected. So currently I need to launch each diff in
its own session of vim.

shell1$ vim old-a.txt new-a.txt
...
shell2$ vim old-b.txt new-b.txt

While this is functional (and less bad within a tmux session), is it
possible to narrow the scope of a :vimdiff to a vim-tab so that I can
have a single vim session with multiple file-diff pairs within?

Mostly it's nice to have things like `gd`, `gD`, jump to places that
show the diffs in the destination as well.

Thanks for any ideas,

-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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20200424160948.3af20ea3%40bigbox.attlocal.net.

Re: VIM crash with YouCompleteMe plugin

On Friday, April 24, 2020 at 2:50:14 PM UTC+5:30, Marius Gedminas wrote:

On Thu, Apr 23, 2020 at 04:21:30AM -0700, BBV wrote:
> I tried to compile python-3.8.2 myself and it seems to take me ahead with the
> previous issue.  I don't see any vim crash anymore. Thanks a lot for your help!
>
> However, the YouCompleteMe plugin still doesn't work. When I open vim, it shows
> an error at the bottom:
> YouCompleteMe unavailable: /remote/cwh3/common/installations/local/lib/
> python3.8/lib-dynload/_socket.cpython-38-x86_64-linux-gnu.so: undefined symbol:
> PyFloat_Type

This usually means an inconsistency between the different builds of
software you built at different times.

E.g. have you rebuilt vim against your newly built python?

The fix is to clean the bad builds and build them from scratch, once
you've identified where the bad builds are.

Let's narrow this down again:

I really appreciate your intent to help!

 

- do you see this with vim --clean +'py3 import socket'
- do you see this with python3.8 -c 'import socket'

This should let you decide if the problem is with your vim build, or
with your Python build.

I did some similar experiments based on suggestion I got at an online gitter room for YouCompleteMe from the maintainers itself. I did rebuild Vim, but the issue still occurred. So, after a bit of googling, I found someone suggesting just to have following done before building Vim (https://github.com/ycm-core/YouCompleteMe/issues/3580#issuecomment-589933447):
     $ export LDFLAGS="-rdynamic"

This made it work!

Then, I still saw some issue in starting YCM server, which was due to LD_LIBRARY_PATH not having path to locally installed Python3 libraries.

Now, it works fine. I am using 'clangd-completer' for semantic completion within Vim and the one packaged with YCM didn't work, so I used a different one (which luckily I already had available).

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/c573ba0e-f708-4e30-b308-9acf3e7c4fdb%40googlegroups.com.