Hi,
I'm currently working on a theme called Selenized https://github.com/jan-warchol/selenized/
We're using https://github.com/lifepillar/vim-colortemplate to template
our theme.
The issue I'm having is https://github.com/jan-warchol/selenized/pull/71#pullrequestreview-375757756
We cannot seem to get SpellRare to work in Vim, yet it works in NeoVim.
The Vim config is extremely simple:
set t_Co=16
set termguicolors
colorscheme selenized
set spelllang=en_au
setlocal spell spelllang=en_au
set spell
set nu
syntax on
My NeoVim config is the same except that it doesn't have set t_Co=16
because that's not supported.
We want the theme when running in Vim to look the same as it does in
NeoVim.
I included a screenshot:
https://user-images.githubusercontent.com/48640805/76826205-c3640200-6813-11ea-859f-e6c9a3c6e0c4.png
as well as the generated theme:
https://github.com/jan-warchol/selenized/pull/71#discussion_r401316369
I'm hoping someone can give us a hand as we really want to support Vim
too, not just NeoVim.
--
Daniel Gray (dng) 0x41911F722B0F9AE3
https://social.privacytools.io/@dngray
--
--
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/20200401021150.xp3cyb3cmnvkhoaj%40disroot.org.
Tuesday, March 31, 2020
How to avoid autocmd CursorMoved to lag ?
Hi,
-- I use this func to switch filetype when cursor is moving outside/inside embed section:
fun! helper#SwitchFileType() "{{{
if !exists('b:busy')
let b:busy=1
let start = str2nr(search( '^\w\+\s\+<<\s\+EOF', 'n' ))
if start > 0
let end = str2nr(search( '^EOF', 'n' ))
let curpos = getcurpos()[1]
let lang = split(getline(start), '<<')[0]->substitute('\s', '', "g")
if (curpos > start) && (curpos < end)
exe 'set ft='.lang
else
exe 'set ft=vim'
end
"echo 'Filetype switched to ' . &ft
end
unlet b:busy
end
endfun "}}}
autocmd CursorMoved *.vim call helper#SwitchFileType()
autocmd CursorMovedI *.vim call helper#SwitchFileType()
The func is called on event cursormoved and lag cursor effectively moving action.
how to avoid this lag ?
Thank you
--
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/d2d25dc4-1516-41a2-b7fb-14a48f4c69e6%40googlegroups.com.
ccomplete#Complete very slow on large tags file
Hi,
I am using the built-in ccomplete#Complete omnifunc for tags-based
completion. It works pretty well with a small or medium sized project.
But on larger projects like Linux or U-Boot, the tags file is pretty big
(~650k lines/70 for U-Boot and ~4.8 mil lines/630MB for Linux).
On these projects, especially Linux, if I use ccomplete, completion
takes a huge amount of time. And since the completion is synchronous,
vim just freezes up for that time and I have to wait for the completion
results to show up. On Linux the wait times can go more than a minute on
my modest quad core 4th gen i7 and a SATA SSD.
So, I intend to set aside some time and try to speed up the completion
and make it asynchronous. I haven't read or written much vimscript so I
don't expect it to be easy or quick. So before I do that, I'd like to
know if anyone here attempted this before.
If someone did succeed, could you please point me to the optimized
version? If someone tried but failed, could you please let me know where
you had trouble? Is it that the ctags format just not suitable for large
projects? Is there some limitation with vim that makes it impossible? Is
it something else entirely?
--
Regards,
Pratyush Yadav
--
--
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/20200331123725.atdrulma3k74t5m7%40yadavpratyush.com.
I am using the built-in ccomplete#Complete omnifunc for tags-based
completion. It works pretty well with a small or medium sized project.
But on larger projects like Linux or U-Boot, the tags file is pretty big
(~650k lines/70 for U-Boot and ~4.8 mil lines/630MB for Linux).
On these projects, especially Linux, if I use ccomplete, completion
takes a huge amount of time. And since the completion is synchronous,
vim just freezes up for that time and I have to wait for the completion
results to show up. On Linux the wait times can go more than a minute on
my modest quad core 4th gen i7 and a SATA SSD.
So, I intend to set aside some time and try to speed up the completion
and make it asynchronous. I haven't read or written much vimscript so I
don't expect it to be easy or quick. So before I do that, I'd like to
know if anyone here attempted this before.
If someone did succeed, could you please point me to the optimized
version? If someone tried but failed, could you please let me know where
you had trouble? Is it that the ctags format just not suitable for large
projects? Is there some limitation with vim that makes it impossible? Is
it something else entirely?
--
Regards,
Pratyush Yadav
--
--
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/20200331123725.atdrulma3k74t5m7%40yadavpratyush.com.
How to change filtetype when cursor is inside a ruby embbed code section
Hi all,
-- Using this kind of script to embed ruby code, how can I change filetype from vim to ruby when cursor is inside [ << EOF , EOF ] section.
vimscript_func
ruby << EOF
EOF
endfunc
--
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/5968a0ca-5589-4423-80a8-a6f8ff68976a%40googlegroups.com.
Re: detaching instance of a process ran in Vim's command mode
On 31Mar2020 12:40, Manas Gupta <manas18244@iiitd.ac.in> wrote:
>I want to run an instance of Okular for every markdown file using bang
>(!)
>in Vim's command mode (like this :!okular % &). And I leave the Okular
>instance open on the side. But when I make changes in the file and save it,
>Okular also makes the changes in its instance which I don't want.
So this means that Okular monitors the contents of the filename why you
gave it.
If that is true, this means that Okular needs to be given a copy of your
file, not the original (because you want to overwrite the original
without disturbing Okular).
On that basis I would write a script which does 3 things:
- take a copy of the filename handed to it
- dispatches Okular against the copy
- after the instance of Okular exits, remove the copy file
Something like:
#!/bin/sh
set -ue
cmd=$( basename "$0" )
[ $# = 1 ] || { echo "Usage: $cmd filename" >&2; exit 2; }
filename=$1
fbase=$( basename "$filename" )
tmpf=${TMPDIR:-/tmp}/$cmd.$$.$fbase
( okular "$tmpf"
rm "$tmpf"
) >/dev/null &
which makes the copy and runs an asynchronous okular with cleanup.
>I also added & at the end of shell command in hope that it will detach that
>process but that doesn't seem to work as I want.
No, because your problem is stopping Okular watching the file you're
editing, hence the copy above.
The "&" isn't magic - it just says "continue without waiting for this
command to finish".
Cheers,
Cameron Simpson <cs@cskk.id.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20200331083503.GA38509%40cskk.homeip.net.
>I want to run an instance of Okular for every markdown file using bang
>(!)
>in Vim's command mode (like this :!okular % &). And I leave the Okular
>instance open on the side. But when I make changes in the file and save it,
>Okular also makes the changes in its instance which I don't want.
So this means that Okular monitors the contents of the filename why you
gave it.
If that is true, this means that Okular needs to be given a copy of your
file, not the original (because you want to overwrite the original
without disturbing Okular).
On that basis I would write a script which does 3 things:
- take a copy of the filename handed to it
- dispatches Okular against the copy
- after the instance of Okular exits, remove the copy file
Something like:
#!/bin/sh
set -ue
cmd=$( basename "$0" )
[ $# = 1 ] || { echo "Usage: $cmd filename" >&2; exit 2; }
filename=$1
fbase=$( basename "$filename" )
tmpf=${TMPDIR:-/tmp}/$cmd.$$.$fbase
( okular "$tmpf"
rm "$tmpf"
) >/dev/null &
which makes the copy and runs an asynchronous okular with cleanup.
>I also added & at the end of shell command in hope that it will detach that
>process but that doesn't seem to work as I want.
No, because your problem is stopping Okular watching the file you're
editing, hence the copy above.
The "&" isn't magic - it just says "continue without waiting for this
command to finish".
Cheers,
Cameron Simpson <cs@cskk.id.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20200331083503.GA38509%40cskk.homeip.net.
Re: detaching instance of a process ran in Vim's command mode
So the situation is as follows:
-- I want to run an instance of Okular for every markdown file using bang (!) in Vim's command mode (like this :!okular % &). And I leave the Okular instance open on the side. But when I make changes in the file and save it, Okular also makes the changes in its instance which I don't want.
I also added & at the end of shell command in hope that it will detach that process but that doesn't seem to work as I want.
Can someone suggest something?
Thanks
--
Manas
Manas
--
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/CA%2BU-oiwrQUsGtP3vckY5qnRGBWKo8Dg1Y1NXDHKr-B%3D1B%2BiciQ%40mail.gmail.com.
Monday, March 30, 2020
Re: .vimrc problem with "autocmd" section, how to resolve?
Hi,
On Saturday, March 28, 2020 at 8:57:27 PM UTC+1, Nicholas Papadonis wrote:
I debugged this further:This block causes problems with a newer vim:" Return to last edit position when opening files (You want this!)autocmd BufReadPost *\ if line("'\"") > 0 && line("'\"") <= line("$") |\ exe "normal! g`\"" |\ endif
I would check these commands:
:verbose set cpo?
:scriptnames
:verbose autocmd
What do they print out? Might be good to compare their output with the other systems where the problem does not exist. By the way, what is the version of the other (older) vim?
Tom 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/8a723af9-27d9-437c-8f1c-88f8104f5f2b%40googlegroups.com.
Saturday, March 28, 2020
Re: enabling xterm_clipboard support by default
On Sun, Mar 29, 2020 at 12:33 AM Manas Gupta <manas18244@iiitd.ac.in> wrote:
>
> I was wondering what could be the reasoning behind not enabling the xterm_clipboard and clipboard support in native vim installations in different distributions?
> I went through a few forums and threads where I found people find it difficult to copy/paste text into system's clipboard.
> Although I found there is a way, by using skel. But it doesn't seem to be working as expected.
>
> Thanks
> Manas
Every distribution includes and excludes features according to its own
preferences in the various versions of Vim it distributes. By default,
+xterm_clipboard is enabled in Normal, Big and Huge versions — unless
they are configured with the --without-x switch. If you run a
GUI-enabled Vim in an xterm or similar terminal emulator, it ought to
be able to access the clipboard. If your default "vim" executable (as
shown by "which vim" and possibly repeating it to follows the link) is
compiled with -x11, then "gvim -v" ought to start the gvim executable
in console mode. If you compile your own Vim and the proper
development packages are installed, it will be named "vim" with (among
others) a soft link "gvim" pointing to it.
All this is for Unix-like systems: on MS-Windows no executable can
serve both in console mode and in GUI mode.
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/CAJkCKXsFRADqZ%3DuPjDh24hwi8E-S4SdN1x9eOjd3heBG0wkQWg%40mail.gmail.com.
>
> I was wondering what could be the reasoning behind not enabling the xterm_clipboard and clipboard support in native vim installations in different distributions?
> I went through a few forums and threads where I found people find it difficult to copy/paste text into system's clipboard.
> Although I found there is a way, by using skel. But it doesn't seem to be working as expected.
>
> Thanks
> Manas
Every distribution includes and excludes features according to its own
preferences in the various versions of Vim it distributes. By default,
+xterm_clipboard is enabled in Normal, Big and Huge versions — unless
they are configured with the --without-x switch. If you run a
GUI-enabled Vim in an xterm or similar terminal emulator, it ought to
be able to access the clipboard. If your default "vim" executable (as
shown by "which vim" and possibly repeating it to follows the link) is
compiled with -x11, then "gvim -v" ought to start the gvim executable
in console mode. If you compile your own Vim and the proper
development packages are installed, it will be named "vim" with (among
others) a soft link "gvim" pointing to it.
All this is for Unix-like systems: on MS-Windows no executable can
serve both in console mode and in GUI mode.
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/CAJkCKXsFRADqZ%3DuPjDh24hwi8E-S4SdN1x9eOjd3heBG0wkQWg%40mail.gmail.com.
Re: enabling xterm_clipboard support by default
On 3/28/20 3:15 PM, Manas Gupta wrote:
> I was wondering what could be the reasoning behind not enabling the
> xterm_clipboard and clipboard support in native vim installations in
> different distributions?
I can't remember of a distribution that I wasn't able to use X11's
clipboard or primary selection buffer.
> I went through a few forums and threads where I found people find it
> difficult to copy/paste text into system's clipboard.
I'll agree that it's not obvious how to use the clipboard / primary
selection buffer in vim. But then again, this is vim, what is obvious
or intuitive to the new vim user?
> Although I found there is a way, by using skel. But it doesn't seem to
> be working as expected.
What's wrong with using the + (plus) / * (star) registers?
"+p puts the contents of the system clipboard.
"*p puts the contents of the primary selection buffer.
You can easily use other commands using the standard register notation.
--
Grant. . . .
unix || die
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/b4bd01c1-6d50-e77d-7feb-49c38fc79bc2%40spamtrap.tnetconsulting.net.
> I was wondering what could be the reasoning behind not enabling the
> xterm_clipboard and clipboard support in native vim installations in
> different distributions?
I can't remember of a distribution that I wasn't able to use X11's
clipboard or primary selection buffer.
> I went through a few forums and threads where I found people find it
> difficult to copy/paste text into system's clipboard.
I'll agree that it's not obvious how to use the clipboard / primary
selection buffer in vim. But then again, this is vim, what is obvious
or intuitive to the new vim user?
> Although I found there is a way, by using skel. But it doesn't seem to
> be working as expected.
What's wrong with using the + (plus) / * (star) registers?
"+p puts the contents of the system clipboard.
"*p puts the contents of the primary selection buffer.
You can easily use other commands using the standard register notation.
--
Grant. . . .
unix || die
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/b4bd01c1-6d50-e77d-7feb-49c38fc79bc2%40spamtrap.tnetconsulting.net.
Re: enabling xterm_clipboard support by default
I was wondering what could be the reasoning behind not enabling the xterm_clipboard and clipboard support in native vim installations in different distributions?
I went through a few forums and threads where I found people find it difficult to copy/paste text into system's clipboard.
Although I found there is a way, by using skel. But it doesn't seem to be working as expected.
Thanks
Manas
--
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/CA%2BU-oixC4XkCwBORs8GB8GHA6Q75O3goWZO9jNZ%3Db8r4mHGemA%40mail.gmail.com.
Re: .vimrc problem with "autocmd" section, how to resolve?
I debugged this further:
This block causes problems with a newer vim:
" Return to last edit position when opening files (You want this!)
autocmd BufReadPost *
\ if line("'\"") > 0 && line("'\"") <= line("$") |
\ exe "normal! g`\"" |
\ endif
On Mar 28, 2020, at 2:07 PM, Nicholas Papadonis <nick.papadonis.ml@gmail.com> wrote:Hi,I'm trying to start vim using an init file and vim is complaining at startup. The same startup file works on other operating systems with vim.Does anyone know what the cause could be?ThanksThis is the feedback at startup:$ vim--- Autocommands ---vimStartup BufRead*if line("'\"") >= 1 && line("'\"") <= line("$") && &ft !~# 'commit' | exe "normal! g`\"" | endiffiletypedetect BufRead*if !did_filetype() && expand("<amatch>") !~ g:ft_ignore_pat | runtime! scripts.vim | endif*if !did_filetype() && expand("<amatch>") !~ g:ft_ignore_pat && (getline(1) =~ '^#' || getline(2) =~ '^#' || getline(3) =~ '^#'^I|| getline(4) =~ '^#' || getline(5) =~ '^#') | setf FALLBACK conf | endifPress ENTER or type command to continueRemoving this from the .vimrc resolves the issue:> if has ("autocmd")> " Automatically go to last place in file> autocmd BufReadPost *> if line("'\"") > 0 && line ("'\"") <= line("$") | exe "normal g'\"" |> endif>> augroup default> "autocmd BufEnter * set textwidth=72 ai formatoptions=tcqn> augroup END>> " Only turn on C-indenting on C type files> augroup cprog> " Remove all cprog autocommands> " au!> autocmd FileType c,cpp au! default>> " When starting to edit a file:> " For C and C++ files set formatting of comments and set C-indenting on.> " For other files switch it off.> " Don't change the order, it's important that the line with *> " comes first.> "autocmd FileType * set formatoptions=tcql nocindent comments&> "autocmd FileType c,cpp set formatoptions=croql cindent comments=sr:/*,mb:*,el:*/,://> "autocmd FileType c,cpp set textwidth=80 ai formatoptions=tcrql> autocmd FileType c,cpp, set expandtab> augroup END> else> set textwidth=72> endifThe version of vim I'm using:VIM - Vi IMproved 8.1 (2018 May 18, compiled Jul 20 2019 18:44:42)Included patches: 1-1721Modified by OpenIndiana <oi-dev@openindiana.org>Compiled by oi-userland build environmentHuge version without GUI. Features included (+) or not (-):+acl -farsi -mouse_sysmouse -tag_any_white+arabic +file_in_path +mouse_urxvt -tcl+autocmd +find_in_path +mouse_xterm +termguicolors+autochdir +float +multi_byte +terminal-autoservername +folding +multi_lang +terminfo-balloon_eval -footer -mzscheme +termresponse+balloon_eval_term +fork() +netbeans_intg +textobjects-browse +gettext +num64 +textprop++builtin_terms -hangul_input +packages +timers+byte_offset +iconv +path_extra +title+channel +insert_expand +perl/dyn -toolbar+cindent +job +persistent_undo +user_commands-clientserver +jumplist +postscript +vartabs-clipboard +keymap +printer +vertsplit+cmdline_compl +lambda +profile +virtualedit+cmdline_hist +langmap +python/dyn +visual+cmdline_info +libcall +python3/dyn +visualextra+comments +linebreak +quickfix +viminfo+conceal +lispindent +reltime +vreplace+cryptv +listcmds +rightleft +wildignore+cscope +localmap +ruby/dyn +wildmenu+cursorbind +lua/dyn +scrollbind +windows+cursorshape +menu +signs +writebackup+dialog_con +mksession +smartindent -X11+diff +modify_fname -sound -xfontset+digraphs +mouse +spell -xim-dnd -mouseshape +startuptime -xpm-ebcdic +mouse_dec +statusline -xsmp+emacs_tags -mouse_gpm -sun_workshop -xterm_clipboard+eval -mouse_jsbterm +syntax -xterm_save+ex_extra +mouse_netterm +tag_binary+extra_search +mouse_sgr -tag_old_staticsystem vimrc file: "/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/share/vim"Compilation: /usr/gcc/6/bin/gcc -c -I. -Iproto -DHAVE_CONFIG_H -m64 -O3 -std=c99 -D_XOPEN_SOURCE=600 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1Linking: /usr/gcc/6/bin/gcc -L. -fstack-protector-strong -R /usr/perl5/5.24/lib/i86pc-solaris-thread-multi-64/CORE -m64 -o vim -lncurses -lsec -R /usr/perl5/5.24/lib/i86pc-solaris-thread-multi-64/CORE -m64 -fstack-protector-strong -L/usr/perl5/5.24/lib/i86pc-solaris-thread-multi-64/CORE -lsocket -lnsl -lm -lc--
--
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/84425c07-e8fe-47ce-bd10-51803fdafa65%40googlegroups.com.
.vimrc problem with "autocmd" section, how to resolve?
Hi,
I'm trying to start vim using an init file and vim is complaining at startup. The same startup file works on other operating systems with vim.
Does anyone know what the cause could be?
Thanks
This is the feedback at startup:
$ vim
--- Autocommands ---
vimStartup BufRead
*if line("'\"") >= 1 && line("'\"") <= line("$") && &ft !~# 'commit' | exe "normal! g`\"" | endif
filetypedetect BufRead
*if !did_filetype() && expand("<amatch>") !~ g:ft_ignore_pat | runtime! scripts.vim | endif
*if !did_filetype() && expand("<amatch>") !~ g:ft_ignore_pat && (getline(1) =~ '^#' || getline(2) =~ '^#' || getline(3) =~ '^#'^I|| getline(4) =~ '^#' || getline(5) =~ '^#') | setf FALLBACK conf | endif
Press ENTER or type command to continue
Removing this from the .vimrc resolves the issue:
> if has ("autocmd")
> " Automatically go to last place in file
> autocmd BufReadPost *
> if line("'\"") > 0 && line ("'\"") <= line("$") | exe "normal g'\"" |
> endif
>
> augroup default
> "autocmd BufEnter * set textwidth=72 ai formatoptions=tcqn
> augroup END
>
> " Only turn on C-indenting on C type files
> augroup cprog
> " Remove all cprog autocommands
> " au!
> autocmd FileType c,cpp au! default
>
> " When starting to edit a file:
> " For C and C++ files set formatting of comments and set C-indenting on.
> " For other files switch it off.
> " Don't change the order, it's important that the line with *
> " comes first.
> "autocmd FileType * set formatoptions=tcql nocindent comments&
> "autocmd FileType c,cpp set formatoptions=croql cindent comments=sr:/*,mb:*,el:*/,://
> "autocmd FileType c,cpp set textwidth=80 ai formatoptions=tcrql
> autocmd FileType c,cpp, set expandtab
> augroup END
> else
> set textwidth=72
> endif
The version of vim I'm using:
VIM - Vi IMproved 8.1 (2018 May 18, compiled Jul 20 2019 18:44:42)
Included patches: 1-1721
Modified by OpenIndiana <oi-dev@openindiana.org>
Compiled by oi-userland build environment
Huge version without GUI. Features included (+) or not (-):
+acl -farsi -mouse_sysmouse -tag_any_white
+arabic +file_in_path +mouse_urxvt -tcl
+autocmd +find_in_path +mouse_xterm +termguicolors
+autochdir +float +multi_byte +terminal
-autoservername +folding +multi_lang +terminfo
-balloon_eval -footer -mzscheme +termresponse
+balloon_eval_term +fork() +netbeans_intg +textobjects
-browse +gettext +num64 +textprop
++builtin_terms -hangul_input +packages +timers
+byte_offset +iconv +path_extra +title
+channel +insert_expand +perl/dyn -toolbar
+cindent +job +persistent_undo +user_commands
-clientserver +jumplist +postscript +vartabs
-clipboard +keymap +printer +vertsplit
+cmdline_compl +lambda +profile +virtualedit
+cmdline_hist +langmap +python/dyn +visual
+cmdline_info +libcall +python3/dyn +visualextra
+comments +linebreak +quickfix +viminfo
+conceal +lispindent +reltime +vreplace
+cryptv +listcmds +rightleft +wildignore
+cscope +localmap +ruby/dyn +wildmenu
+cursorbind +lua/dyn +scrollbind +windows
+cursorshape +menu +signs +writebackup
+dialog_con +mksession +smartindent -X11
+diff +modify_fname -sound -xfontset
+digraphs +mouse +spell -xim
-dnd -mouseshape +startuptime -xpm
-ebcdic +mouse_dec +statusline -xsmp
+emacs_tags -mouse_gpm -sun_workshop -xterm_clipboard
+eval -mouse_jsbterm +syntax -xterm_save
+ex_extra +mouse_netterm +tag_binary
+extra_search +mouse_sgr -tag_old_static
system vimrc file: "/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/share/vim"
Compilation: /usr/gcc/6/bin/gcc -c -I. -Iproto -DHAVE_CONFIG_H -m64 -O3 -std=c9
9 -D_XOPEN_SOURCE=600 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: /usr/gcc/6/bin/gcc -L. -fstack-protector-strong -R /usr/perl5/5.24/lib/i8
6pc-solaris-thread-multi-64/CORE -m64 -o vim -lncurses -lsec -R /usr/perl5
/5.24/lib/i86pc-solaris-thread-multi-64/CORE -m64 -fstack-protector-strong -L/usr
/perl5/5.24/lib/i86pc-solaris-thread-multi-64/CORE -lsocket -lnsl -lm -lc
--
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/84425c07-e8fe-47ce-bd10-51803fdafa65%40googlegroups.com.
Thursday, March 26, 2020
Re: "Auto Yes" to Warnings On Save (Scriptability)
The problem with using tail, sed, or similar is that they use intermediate files. For the use case I'm describing, I need to be modifying the SAME file (same inode), because I'm trying to change a "live" file that the other process is writing to. Living dangerously, I know.
On Thu, Mar 26, 2020 at 11:30 AM Gary Fritz <garyfritzz@gmail.com> wrote:
Yes, I think tail is a much simpler option. Just be aware you can't do this:--tail -n 25 myfile > myfile... because the "> myfile" opens and truncates the file (throwing away the contents) before the tail command runs.Something like this would work:tail -n 25 myfile > /tmp/tail$$mv /tmp/tail$$ myfile
--
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/1c8d9b61-45b1-4977-a285-59a8a3cc9045%40googlegroups.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/CA%2BpbHuEMDcKzHwQ6xf3_j05WnLVXyMFZ4NpMxCqNwKe9Wt9xPg%40mail.gmail.com.
Re: "Auto Yes" to Warnings On Save (Scriptability)
Yes, I think tail is a much simpler option. Just be aware you can't do this:
-- tail -n 25 myfile > myfile
... because the "> myfile" opens and truncates the file (throwing away the contents) before the tail command runs.
Something like this would work:
tail -n 25 myfile > /tmp/tail$$
mv /tmp/tail$$ myfile
--
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/1c8d9b61-45b1-4977-a285-59a8a3cc9045%40googlegroups.com.
Re: "Auto Yes" to Warnings On Save (Scriptability)
> I am looking for a way to periodically remove the first N lines of a file,
> to implement a "quick and dirty" log file size management scheme.
>
Have you looked at tail and its options? sed would probably also work, but
tail is probably more obvious.
--
--
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/42ea8343e86aae10ba1d834b2dbf6677.squirrel%40webmail.vybenetworks.com.
> to implement a "quick and dirty" log file size management scheme.
>
Have you looked at tail and its options? sed would probably also work, but
tail is probably more obvious.
--
--
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/42ea8343e86aae10ba1d834b2dbf6677.squirrel%40webmail.vybenetworks.com.
Re: Customize vim for YAML
I got an answer from vi.stackexchange.com:
-- * I needed filetype on in .vimrc to get it to recognize the filetype. (Don't think I had that before when it worked!?? And in fact once I had this all working, I deleted the filetype on and it still worked. Go figger.)
* I needed syntax on in .vimrc to get it to highlight syntax. (Also don't think I had this before, but I DO need this one.)
* I did NOT need the first autocommand to source ~/.vim/yaml.vim. Without it, vim sources /usr/share/vim/vim80/syntax/yaml.vim.
* In the remaining autocommand they recommend I use setlocal instead of set, and sts=2 (softtabstop) instead of ts=2 (tabstop).
Works great now!
--
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/1c9a03d1-5063-44de-85bb-1891aa9f860f%40googlegroups.com.
"Auto Yes" to Warnings On Save (Scriptability)
I am looking for a way to periodically remove the first N lines of a file, to implement a "quick and dirty" log file size management scheme.
-- I have found that vi will effectively do this, and (somewhat surprisingly) the logging application seems to be okay with its log file being modified.
I have a vim script (del25.keys) with this command: d25dZZ (delete 25 lines and write/quit).
I run vi like this: vi -n -s del25.keys FILE
The problem I'm running into is that in the corner case that FILE is modified by the logging application at the same instant that vi is doing its processing, vi issues W11 on save (file externally modified). I'm not too concerned about losing one or two log lines occasionally, so I want it to "auto yes" (suppress the warning) to avoid stopping my script.
I've tried a few different mechanisms to address this, including slightly different commands and FileChangedShell, but the warning remains. Is there a way to actually suppress this warning so my script will run without "getting stuck in this corner case? Thanks for your thoughts.
--
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/49d8019d-249d-488c-b948-f08d6df96959%40googlegroups.com.
Wednesday, March 25, 2020
Re: visual select in Co mode ?
Hi,
-- I added:
set clipboard^=autoselectml guioptions+=A
and now I can drag/double click and paste to the command-line.
Would be cool if the highlight colour matched visual but no problem :-)
thanks again always for all your great info and help,
-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/8d94a09c-910f-48dd-b551-8de251a8d9d5%40googlegroups.com.
Re: visual select in Co mode ?
Hi,
Thank you Tony.
-- Thank you Tony.
-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/9e8fbe55-8ab4-4ffb-93f5-1c86a0aec0e8%40googlegroups.com.
Re: visual select in Co mode ?
In command-line mode you can only use modeless selection: indeed at
that time the active cursor is not in any edit window. It works even
in gvim.
See
:help modeless-selection
:help modeless-and-clipboard
Best regards,
Tony.
On Wed, Mar 25, 2020 at 6:08 PM M Kelly <mckelly2833@gmail.com> wrote:
>
> Hi,
>
> My visual selection works great in normal, visual and insert modes, but when I enter command mode via a '/' or ':' then I can no longer select with the mouse the same way.
> It seems as tho I am using x selection (ie like shift+mouse) instead of visual selection.
> I tried changing imaps to lmaps but no difference.
> Is this expected / the way it must be ?
>
> 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/5b965dc6-edb0-4373-9eaf-ce6c9cc5211f%40googlegroups.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/CAJkCKXtVV_1kKyCeyrampb0nn26eOwc9HucwyHP1Eg%2BNK8M4gg%40mail.gmail.com.
that time the active cursor is not in any edit window. It works even
in gvim.
See
:help modeless-selection
:help modeless-and-clipboard
Best regards,
Tony.
On Wed, Mar 25, 2020 at 6:08 PM M Kelly <mckelly2833@gmail.com> wrote:
>
> Hi,
>
> My visual selection works great in normal, visual and insert modes, but when I enter command mode via a '/' or ':' then I can no longer select with the mouse the same way.
> It seems as tho I am using x selection (ie like shift+mouse) instead of visual selection.
> I tried changing imaps to lmaps but no difference.
> Is this expected / the way it must be ?
>
> 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/5b965dc6-edb0-4373-9eaf-ce6c9cc5211f%40googlegroups.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/CAJkCKXtVV_1kKyCeyrampb0nn26eOwc9HucwyHP1Eg%2BNK8M4gg%40mail.gmail.com.
Re: visual select in Co mode ?
Hi,
-- To be clear I do not mean the colour of highlighing anything in the command-line.
I mean highlighing other text above the command-line.
Like for example if you were to enter command-mode with a '/' and then use the mouse to highlight some text above to then paste in the command-line.
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/2c612a6f-a7f2-4240-ab73-a36cff7f41f8%40googlegroups.com.
Re: visual select in Co mode ?
Hi,
-- What colour would the highlighting be when in command-mode ?
It is not the same as hi Visual setting.
It is not the same as hi Visual setting.
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/eafa1016-b83c-4eaf-a365-11e9bc80140a%40googlegroups.com.
visual select in Co mode ?
Hi,
-- My visual selection works great in normal, visual and insert modes, but when I enter command mode via a '/' or ':' then I can no longer select with the mouse the same way.
It seems as tho I am using x selection (ie like shift+mouse) instead of visual selection.
I tried changing imaps to lmaps but no difference.
Is this expected / the way it must be ?
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/5b965dc6-edb0-4373-9eaf-ce6c9cc5211f%40googlegroups.com.
Re: Customize vim for YAML
I discovered vim -V, which dumps out a running commentary about what it's doing as it comes up. On the second page I see this:
-- Executing BufRead Auto commands for "*.yml"
autocommand so ~/.vim/yaml.vim
chdir(/home/ansible/.vim)
fchdir() to previous dir
line 0: sourcing "/home/ansible/.vim/yaml.vim"
finished sourcing /home/ansible/.vim/yaml.vim
(That was for a non-root user, but root is the same.)
So it's definitely sourcing the yaml.vim file. That means the .vimrc file must have been sourced. So why don't I see the settings from .vimrc (set ai ts=2 sw=2 et number)? And since it sourced the yaml.vim file, why isn't it highlighting syntax?? Especially since this used to work for non-root users!?
--
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/4a543968-4ee2-4fde-8c5b-f3cc67582ac0%40googlegroups.com.
Tuesday, March 24, 2020
Customize vim for YAML
I'm doing some Ansible work (on RHEL 8), so I want the YAML configs for vim. I have a yaml.vim file containing the syntax/etc, and a ~/.vimrc file:
-- autocmd BufNewFile,BufRead *.yaml,*.yml so ~/.vim/yaml.vim
autocmd FileType yaml,yml set ai ts=2 sw=2 et number
While logged in as user ansible, that worked just peachy. But then I copied the same files to the same places under ~ (root), and when I was root (via su or su -), vim was clueless about yaml.
I tried changing the ~root/.vim/yaml.vim in .vimrc to ~root/.vim/yaml.vim -- no joy.
With some digging I discovered that vi doesn't read .vimrc when you're root but vim does!!?? But vim didn't work either.
Out of exasperation I tried rebooting my Linux server. Now it doesn't work for user ansible either!!??
I tried :source ~/.vimrc and it kinda worked. That picked up the .vimrc settings but not the syntax-highlight stuff in yaml.vim, even if I did a :e! to force it to re-read the file and see the file suffix. But that only worked for root!? And only a few times. Now it doesn't work. :source ~/.vim/yaml.vim doesn't do anything either.
Help?
--
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/3c40a249-9481-4532-a283-4b13ad49d9df%40googlegroups.com.
Side-effects of <2-LeftMouse> of Vim with manpager in Terminal.app
I have recently found the manpager plugin, and am using it (it is cool!). One problem is that it does not map double-click, like the help file. So I added in my .vimrc:
au FileType man nmap <buffer> <2-leftmouse> <C-]>
Then, to my bewilderment, I found it worked, but caused unwanted terminal (non-Vim) selection (from top-left to the cursor position). More investigation showed this happened only with the macOS Terminal app, but not iTerm2, or a Linux gnome-terminal. Before I dismissed it as a Terminal bug, double-click in a help file worked very well in the macOS terminal...
Best regards,
Yongwei
--
Yongwei Wu
URL: http://wyw.dcweb.cn/
URL: http://wyw.dcweb.cn/
--
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/CADs46iddfF8mQU0%2Be74wPeyKar1noc5q1p5cTXmB3u0Cf%2BZVFA%40mail.gmail.com.
Sunday, March 22, 2020
Re: getting the full path of arguments in command completion=file
On 2020-03-22, Martin Alaçam wrote:
> command! -nargs=* -complete=file Loader call Test(<f-args>)
>
> How would I get the <f-args> to be full paths to the arguments (file names)?
> I am guessing it has to be done in the command, and not in the function being
> called (Test)?
Here's one way to do it. Replace "echo path" by your actual
processing of each file.
function! Test(...)
for file in a:000
let path = fnamemodify(file, ":p")
echo path
endfor
endfunction
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/20200322221328.GA25471%40phoenix.
> command! -nargs=* -complete=file Loader call Test(<f-args>)
>
> How would I get the <f-args> to be full paths to the arguments (file names)?
> I am guessing it has to be done in the command, and not in the function being
> called (Test)?
Here's one way to do it. Replace "echo path" by your actual
processing of each file.
function! Test(...)
for file in a:000
let path = fnamemodify(file, ":p")
echo path
endfor
endfunction
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/20200322221328.GA25471%40phoenix.
Re: getting the full path of arguments in command completion=file
Ah, it works from within the function too, that is smart. And the nicer solution. Thanks!
On Sun, Mar 22, 2020 at 11:15 PM Gary Johnson <garyjohn@spocom.com> wrote:
On 2020-03-22, Martin Alaçam wrote:
> command! -nargs=* -complete=file Loader call Test(<f-args>)
>
> How would I get the <f-args> to be full paths to the arguments (file names)?
> I am guessing it has to be done in the command, and not in the function being
> called (Test)?
Here's one way to do it. Replace "echo path" by your actual
processing of each file.
function! Test(...)
for file in a:000
let path = fnamemodify(file, ":p")
echo path
endfor
endfunction
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/20200322221328.GA25471%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/CAHvr%2BSVCScYzWUJd1tPXgL-YnUVJ-enBhCXyfZ9qSkhGp7trNg%40mail.gmail.com.
Re: getting the full path of arguments in command completion=file
Found it:
command! -nargs=* -complete=file Loader for f in [<f-args>] | call Test(fnamemodify(f, ":p")) | endfor
command! -nargs=* -complete=file Loader for f in [<f-args>] | call Test(fnamemodify(f, ":p")) | endfor
On Sun, Mar 22, 2020 at 9:41 PM Martin Alaçam <martinalacam@gmail.com> wrote:
Hello,
command! -nargs=* -complete=file Loader call Test(<f-args>)
How would I get the <f-args> to be full paths to the arguments (file names)?
I am guessing it has to be done in the command, and not in the function being called (Test)?
Thanks in advance,
Martin
--
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/CAHvr%2BSU3mb7cCwFdjSd1QO-EiszAuwVivxVhjRoCWtz%3DAtxL6w%40mail.gmail.com.
getting the full path of arguments in command completion=file
Hello,
command! -nargs=* -complete=file Loader call Test(<f-args>)
How would I get the <f-args> to be full paths to the arguments (file names)?
I am guessing it has to be done in the command, and not in the function being called (Test)?
Thanks in advance,
Martin
-- command! -nargs=* -complete=file Loader call Test(<f-args>)
How would I get the <f-args> to be full paths to the arguments (file names)?
I am guessing it has to be done in the command, and not in the function being called (Test)?
Thanks in advance,
Martin
--
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/CAHvr%2BSUFQvVPn4Ur_iUeZqZfLuWj65FEDv%3DZ-OTFBX2ZDFwXbQ%40mail.gmail.com.
Re: Lose highlighting when Index.wiki is loaded from Dropbox
Hi Eric,
I too use vimwiki located in a grive folder, with no issues. In the hope it's some help, below, are the only settings I seem to have in my .vimrc relating to vimwiki.
Kind regards,
Ryan
Enter code here...
let g:vimwiki_list = [{
\ 'path': '$HOME/google-drive/vimwiki',
\ 'template_path': '$HOME/google-drive/vimwiki/templates',
\ 'template_default': 'default',
\ 'template_ext': '.html'}]
On Saturday, 21 March 2020 16:33:51 UTC, Eric Weir wrote:
I have put my Vim files, including my Vimwiki files, in a Dropbox folder. I would like to be able to access them from both MacOS (MacVim) and iOS (iVim). However, when I open the Vimwiki index file ("index.wiki") in either app the highlighting of links that enables navigation among Vimwiki files is lost. What happened? How do I restore it?
Thanks
------------------------------------------------------------ ----------------------------
Eric Weir
Decatur, GA USA
eew...@bellsouth.net
"Imagining the other is a powerful antidote to fanaticism and hatred."
- Amos Oz
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/6e70da95-6a36-48ba-8619-f39f818fc4a6%40googlegroups.com.
Saturday, March 21, 2020
Lose highlighting when Index.wiki is loaded from Dropbox
I have put my Vim files, including my Vimwiki files, in a Dropbox folder. I would like to be able to access them from both MacOS (MacVim) and iOS (iVim). However, when I open the Vimwiki index file ("index.wiki") in either app the highlighting of links that enables navigation among Vimwiki files is lost. What happened? How do I restore it?
Thanks
----------------------------------------------------------------------------------------
Eric Weir
Decatur, GA USA
eeweir@bellsouth.net
"Imagining the other is a powerful antidote to fanaticism and hatred."
- Amos Oz
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/151F76D8-C912-42B8-845E-FC0846C1BC92%40bellsouth.net.
Thanks
----------------------------------------------------------------------------------------
Eric Weir
Decatur, GA USA
eeweir@bellsouth.net
"Imagining the other is a powerful antidote to fanaticism and hatred."
- Amos Oz
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/151F76D8-C912-42B8-845E-FC0846C1BC92%40bellsouth.net.
Tuesday, March 17, 2020
Re: Making a tarball
> On Mar 16, 2020, at 1:59 PM, arocker@vex.net <arocker@Vex.Net> wrote:
>
>> To make (or unpack) a tarball in general: at the shell prompt
>> man tar
>
> Just to amplify that a bit, with $ representing the shell prompt:
>
> to create a tarball:
> $ tar -cvzf name_of_archive_to_create directory_to_send
>
> That will show you the files in "directory_to_send" being wrapped up. If
> it's only one file at a time, just give the filename. Use a relative path,
> not an absolute one, so you can restore anywhere you want.
>
> To unpack, cd into the directory you want to use, and execute
> $ tar -xzvf name_of_archive_to create
>
> If you don't want to see all the filenames, omit the "v" option. The "f"
> option must be the last thing before the filename.
Thanks.
Per my response to Tony, iOS does not provide a shell natively. There are apps, e.g., iSH, that will do so. And one, i.e., iZip, that may provide an even simpler solution, at least for one whose be away from Vim and Unix for a while.
------------------------------------------------------------------------------------------
Eric Weir
Decatur, GA USA
eeweir@bellsouth.net
"(I)t is important that awake people be awake... the darkness around us is deep."
- William Stafford
--
--
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/00E5FD95-7F0D-4425-9D4B-F04D069A0953%40bellsouth.net.
>
>> To make (or unpack) a tarball in general: at the shell prompt
>> man tar
>
> Just to amplify that a bit, with $ representing the shell prompt:
>
> to create a tarball:
> $ tar -cvzf name_of_archive_to_create directory_to_send
>
> That will show you the files in "directory_to_send" being wrapped up. If
> it's only one file at a time, just give the filename. Use a relative path,
> not an absolute one, so you can restore anywhere you want.
>
> To unpack, cd into the directory you want to use, and execute
> $ tar -xzvf name_of_archive_to create
>
> If you don't want to see all the filenames, omit the "v" option. The "f"
> option must be the last thing before the filename.
Thanks.
Per my response to Tony, iOS does not provide a shell natively. There are apps, e.g., iSH, that will do so. And one, i.e., iZip, that may provide an even simpler solution, at least for one whose be away from Vim and Unix for a while.
------------------------------------------------------------------------------------------
Eric Weir
Decatur, GA USA
eeweir@bellsouth.net
"(I)t is important that awake people be awake... the darkness around us is deep."
- William Stafford
--
--
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/00E5FD95-7F0D-4425-9D4B-F04D069A0953%40bellsouth.net.
Re: Making a tarball
> On Mar 16, 2020, at 11:46 AM, Tony Mechelynck <antoine.mechelynck@gmail.com> wrote:
>
> On Mon, Mar 16, 2020 at 3:35 PM Eric Weir <eeweir@bellsouth.net> wrote:
>>
>>
>> Been away from Vim for a while. Skills rusty. I've got iVim running on my iPad. I'd like to put my files in the cloud—Dropbox or iCloud—so they can be accessed from MacVim on my MacBook.
>>
>> Tarball has been suggested as the best way to move files from my iVim documents folder. Haven't a clue how to go about it. I've always found Vim help difficult to navigate, and often to understand. References to it appreciated. Even more references to other sources.
>
> For particular packages: type from within Vim
> :help pi_vimball.txt
>
> To make (or unpack) a tarball in general: at the shell prompt
> man tar
Thanks, Tony.
iOS does not natively provide a terminal or shell—I had to do a web search for the differences, if any, between them; still not sure I understand; pretty sure it's not important; for me, that is. Additional web searching informs me that there are iOS apps that make it possible. This one provides a decently robust Unix emulation. <https://osxdaily.com/2018/12/11/ish-linux-shell-ios/>
As I've been away from Vim for a good while, and even longer from Unix, there is another app, iZip, that might be an easier solution for me. <https://apps.apple.com/us/app/izip-zip-unzip-unrar-tool/id413971331>
------------------------------------------------------------------------------------------
Eric Weir
Decatur, GA USA
eeweir@bellsouth.net
"Look deep into nature, you will understand everything better."
- Albert Einstein
--
--
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/338D5FCD-02AF-4E20-A482-5B4B96F3FC9F%40bellsouth.net.
>
> On Mon, Mar 16, 2020 at 3:35 PM Eric Weir <eeweir@bellsouth.net> wrote:
>>
>>
>> Been away from Vim for a while. Skills rusty. I've got iVim running on my iPad. I'd like to put my files in the cloud—Dropbox or iCloud—so they can be accessed from MacVim on my MacBook.
>>
>> Tarball has been suggested as the best way to move files from my iVim documents folder. Haven't a clue how to go about it. I've always found Vim help difficult to navigate, and often to understand. References to it appreciated. Even more references to other sources.
>
> For particular packages: type from within Vim
> :help pi_vimball.txt
>
> To make (or unpack) a tarball in general: at the shell prompt
> man tar
Thanks, Tony.
iOS does not natively provide a terminal or shell—I had to do a web search for the differences, if any, between them; still not sure I understand; pretty sure it's not important; for me, that is. Additional web searching informs me that there are iOS apps that make it possible. This one provides a decently robust Unix emulation. <https://osxdaily.com/2018/12/11/ish-linux-shell-ios/>
As I've been away from Vim for a good while, and even longer from Unix, there is another app, iZip, that might be an easier solution for me. <https://apps.apple.com/us/app/izip-zip-unzip-unrar-tool/id413971331>
------------------------------------------------------------------------------------------
Eric Weir
Decatur, GA USA
eeweir@bellsouth.net
"Look deep into nature, you will understand everything better."
- Albert Einstein
--
--
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/338D5FCD-02AF-4E20-A482-5B4B96F3FC9F%40bellsouth.net.
Re: [EXTERNAL] Re: Mouse not working last 20% of screen
> Punch 80 times octal 07777 in binary mode in each of them, throw away
> the cards but keep the confetti, and use them ne next time weddings
> will be permitted.
>
>
Seriously, don't do that. Punched card chads are sharp and hard enough to
cause eye injuries.
--
--
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/057622ec486d682288e721797ad6ac39.squirrel%40webmail.vybenetworks.com.
> the cards but keep the confetti, and use them ne next time weddings
> will be permitted.
>
>
Seriously, don't do that. Punched card chads are sharp and hard enough to
cause eye injuries.
--
--
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/057622ec486d682288e721797ad6ac39.squirrel%40webmail.vybenetworks.com.
Re: Mouse not working last 20% of screen
On Tue, Mar 17, 2020 at 6:57 AM Benjamin Esham <usenet@esham.io> wrote:
>
> Tony Mechelynck wrote:
>
> > On Mon, Mar 16, 2020 at 6:04 PM Tony Mechelynck
> > <antoine.mechelynck@gmail.com> wrote:
> >
> >> Update: manually setting ttymouse=sgr in konsole 18.12.3 makes it
> >> work, even though it only admits to xterm equivalent version 115,
> >> which would normally mean ttymouse=xterm2.
> >>
> >> Best rgards,
> >> Tony.
> >
> > OK, I'll add the following to my vimrc, but it is a hack, and not
> > guaranteed to work:
> >
> > au TermResponse *
> > \ if &ttym == 'xterm2' | set ttym=sgr | endif
> >
> > Best regards,
> > Tony.
>
> I don't suppose your terminal emulator sets $TERM_PROGRAM? (As far as I've
> been able to tell, this environment variable is a macOS-ism, but if you can
> use it it seems like it might solve your problem neatly.)
>
> Benjamin
No it doesn't. "set | less" at the bash prompt lists (among others)
all environment variables in alphabetical order, and the only one
whose name starts with T is TERM=xterm-256color
In a "real" xterm there are two of them, namely TERM=xterm and
TS1=$'\E7\E]2;%s@%s:%s\a\E]1;%s\a\E8' ; in a non-X console (e.g.
Ctrl-Alt-F2) it's just TERM=linux ; and in gnome-terminal (which I
rarely use) v:termresponse is ^[[>1;5002;0c ("xterm version 5002", no
kidding) and Vim, seeing that, sets ttymouse=sgr with no user
intervention (even if started with -u DEFAULTS).
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%2BciODQEmn7iA6MnvYsOfseJD52WpoUF_8ySKAc0gTow%40mail.gmail.com.
>
> Tony Mechelynck wrote:
>
> > On Mon, Mar 16, 2020 at 6:04 PM Tony Mechelynck
> > <antoine.mechelynck@gmail.com> wrote:
> >
> >> Update: manually setting ttymouse=sgr in konsole 18.12.3 makes it
> >> work, even though it only admits to xterm equivalent version 115,
> >> which would normally mean ttymouse=xterm2.
> >>
> >> Best rgards,
> >> Tony.
> >
> > OK, I'll add the following to my vimrc, but it is a hack, and not
> > guaranteed to work:
> >
> > au TermResponse *
> > \ if &ttym == 'xterm2' | set ttym=sgr | endif
> >
> > Best regards,
> > Tony.
>
> I don't suppose your terminal emulator sets $TERM_PROGRAM? (As far as I've
> been able to tell, this environment variable is a macOS-ism, but if you can
> use it it seems like it might solve your problem neatly.)
>
> Benjamin
No it doesn't. "set | less" at the bash prompt lists (among others)
all environment variables in alphabetical order, and the only one
whose name starts with T is TERM=xterm-256color
In a "real" xterm there are two of them, namely TERM=xterm and
TS1=$'\E7\E]2;%s@%s:%s\a\E]1;%s\a\E8' ; in a non-X console (e.g.
Ctrl-Alt-F2) it's just TERM=linux ; and in gnome-terminal (which I
rarely use) v:termresponse is ^[[>1;5002;0c ("xterm version 5002", no
kidding) and Vim, seeing that, sets ttymouse=sgr with no user
intervention (even if started with -u DEFAULTS).
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%2BciODQEmn7iA6MnvYsOfseJD52WpoUF_8ySKAc0gTow%40mail.gmail.com.
Monday, March 16, 2020
Re: Mouse not working last 20% of screen
Tony Mechelynck wrote:
> On Mon, Mar 16, 2020 at 6:04 PM Tony Mechelynck
> <antoine.mechelynck@gmail.com> wrote:
>
>> Update: manually setting ttymouse=sgr in konsole 18.12.3 makes it
>> work, even though it only admits to xterm equivalent version 115,
>> which would normally mean ttymouse=xterm2.
>>
>> Best rgards,
>> Tony.
>
> OK, I'll add the following to my vimrc, but it is a hack, and not
> guaranteed to work:
>
> au TermResponse *
> \ if &ttym == 'xterm2' | set ttym=sgr | endif
>
> Best regards,
> Tony.
I don't suppose your terminal emulator sets $TERM_PROGRAM? (As far as I've
been able to tell, this environment variable is a macOS-ism, but if you can
use it it seems like it might solve your problem neatly.)
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/k7v6dhl4.f29ttp%40bdesham.net.
> On Mon, Mar 16, 2020 at 6:04 PM Tony Mechelynck
> <antoine.mechelynck@gmail.com> wrote:
>
>> Update: manually setting ttymouse=sgr in konsole 18.12.3 makes it
>> work, even though it only admits to xterm equivalent version 115,
>> which would normally mean ttymouse=xterm2.
>>
>> Best rgards,
>> Tony.
>
> OK, I'll add the following to my vimrc, but it is a hack, and not
> guaranteed to work:
>
> au TermResponse *
> \ if &ttym == 'xterm2' | set ttym=sgr | endif
>
> Best regards,
> Tony.
I don't suppose your terminal emulator sets $TERM_PROGRAM? (As far as I've
been able to tell, this environment variable is a macOS-ism, but if you can
use it it seems like it might solve your problem neatly.)
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/k7v6dhl4.f29ttp%40bdesham.net.
XQuery indentation and syntax file
Hi,
This seems to be a quite old vim file for XQuery.
https://github.com/jeroenp/vim-xquery-syntax
This is also very old and seems to be buggy.
https://github.com/vim-scripts/XQuery-indentomnicompleteftplugin/blob/master/ftplugin/xquery.vim
Are there updated XQuery indentation and syntax files to be used? Thanks.
PS. The original message was burried under a wrong thread. So I resend
this message.
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CABrM6wmgv%3Dd-KCn7uXX1Qxbw5kYyaMxQRU%3DESoTvV_Lx7FYnWA%40mail.gmail.com.
This seems to be a quite old vim file for XQuery.
https://github.com/jeroenp/vim-xquery-syntax
This is also very old and seems to be buggy.
https://github.com/vim-scripts/XQuery-indentomnicompleteftplugin/blob/master/ftplugin/xquery.vim
Are there updated XQuery indentation and syntax files to be used? Thanks.
PS. The original message was burried under a wrong thread. So I resend
this message.
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CABrM6wmgv%3Dd-KCn7uXX1Qxbw5kYyaMxQRU%3DESoTvV_Lx7FYnWA%40mail.gmail.com.
XQuery indentation and syntax file
Hi,
This seems to be a quite old vim file for XQuery.
https://github.com/jeroenp/vim-xquery-syntax
This is also very old and seems to be buggy.
https://github.com/vim-scripts/XQuery-indentomnicompleteftplugin/blob/master/ftplugin/xquery.vim
Are there updated XQuery indentation and syntax files to be used? Thanks.
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CABrM6wk73u1fRvLbDMpogDJ7FvMNME4iqhcXxfvGRa1Yr%3DYomA%40mail.gmail.com.
This seems to be a quite old vim file for XQuery.
https://github.com/jeroenp/vim-xquery-syntax
This is also very old and seems to be buggy.
https://github.com/vim-scripts/XQuery-indentomnicompleteftplugin/blob/master/ftplugin/xquery.vim
Are there updated XQuery indentation and syntax files to be used? Thanks.
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CABrM6wk73u1fRvLbDMpogDJ7FvMNME4iqhcXxfvGRa1Yr%3DYomA%40mail.gmail.com.
Re: Using non-greedy quantifiers with substitute()
Thank you so much- I had no idea about single quote strings.
On Mon, Mar 16, 2020 at 6:32 PM John Little <john.b.little@gmail.com> wrote:
--You've used a double-quote string, which processes backslash characters, for the pattern. Either double the backslash, or use a single-quote string:echo substitute("#|\nmulti-line comment\n|#",'#|.\{-}|#',"","g")HTH, and 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/ac338094-581e-4b28-9598-7da9a0160b40%40googlegroups.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/CAGyWG1tQDmYLzzKYuPpfLkO8zdq3K_jvJ%3Dhwe3kXDrbAkQGHBw%40mail.gmail.com.
Re: Using non-greedy quantifiers with substitute()
You've used a double-quote string, which processes backslash characters, for the pattern. Either double the backslash, or use a single-quote string:
echo substitute("#|\nmulti-line comment\n|#",'#|.\{-}|#',"","g")
HTH, and 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/ac338094-581e-4b28-9598-7da9a0160b40%40googlegroups.com.
Subscribe to:
Posts (Atom)