Re: :Termdebug config/startup to hide debugged program window

> No, currently there is no option for it. But it makes sense.
>
> I wonder how best to specify this. I suppose it depends on what you
> want to debug, thus a global flag is not that useful. Some flag on the
> :Termdebug command is probably more useful.

Yes, that would be great.

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

Re: :Termdebug config/startup to hide debugged program window

M Kelly wrote:

> I am using :Termdebug and was wondering if there was a way to remove the:
> 2 #a? "debugged program [active]" line 0
> window/buffer at start up.
> I usually attach to a running process and do not use this window.
> Can I somehow hide it automatically ?

No, currently there is no option for it. But it makes sense.

I wonder how best to specify this. I suppose it depends on what you
want to debug, thus a global flag is not that useful. Some flag on the
:Termdebug command is probably more useful.

--
Linux is just like a wigwam: no Windows, no Gates and an Apache inside.

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

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

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

:Termdebug config/startup to hide debugged program window

Hi,
I am using :Termdebug and was wondering if there was a way to remove the:
2 #a? "debugged program [active]" line 0
window/buffer at start up.
I usually attach to a running process and do not use this window.
Can I somehow hide it automatically ?
thx always for the vim universe,
-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.
For more options, visit https://groups.google.com/d/optout.

How to syntax error highlight missing comma? (advanced regular expressions)

Hi,
Rule: Between "select" and "from" rows every row has to end with comma except one row above from.

CORRECT
select
col1,
col2,
col3,
col4,
col5
from
mytable

Note: There can be several like 100 or more colN rows. Above is simplified sample.

INNCORRECT
select
col1
col2,
col3
col4,
col5
from
mytable

There should be command after col1 and col3.

I have put the "X" bellow to indicate where error highlight mark should appear.
HIGHLIGHT MARK
select
col1X
col2,
col3X
col4,
col5
from
mytable

To see the matched pattern I have turned highlight search and incremental search settings:
:set hlsearch
:set incsearch

Now I have come up with the following regex:
/select\s*\n\_.*\(,\)\@<!\zs\n\ze\_.*\n\s*from

The above regex is almost there, the only problem is, it only marks new-line character after "col3", but I would ALSO like to mark character after "col1" (like above "X" in HIGHLIGHT MARK sample).

But if I add comma after "col3" then new-line after "col1" is marked, which is correct. There got to be some tiny thing that I can't figure it out how to fix.

REQUEST: I would like to have error highlighting for ALL missing commas, not just the last one.

I use the latest Vim 8.1.0490.

EXPLAINING ABOVE REGEX
Let me explain what I have come with so far. Regexp is:
/select\s*\n\_.*\(,\)\@<!\zs\n\ze\_.*\n\s*from

1. There are words "select" and "from" that should searching happen in the first place.
2. \s* there can be zero or more spaces at the end of "select" row
3. \n new line follows
4. \_.* zero or more characters including new lines may follow
5. \(,\)\@<! search where there is missing ","
See: :help \@<!
6. \zs\n\ze only mark new-line character
7. \_.* zero or more characters including new lines
8. \n\s* new line followed by zero or multiple spaces
9. from final word

If you have turned on "hlsearch" and "incsearch" the new line after "col3" is marked, but new-line after "col1" is NOT marked. If I add comma after "col3", then new-line character after "col1" is marked. This both is correct, but I would like to have ALL missing comma marked in the same screen.

Regards

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

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

Re: Paste into a :term window?

On Thursday, October 25, 2018 at 2:33:38 PM UTC-5, Lifepillar wrote:
> On 25/10/2018 17:32, Kelvin Lawrence wrote:
> > I'm enjoying the new :term feature in 8.1
> >
> > I have my code on the left and a job running on the right. The job is a console environment for Groovy. Is there an easy way to copy from the code on the left and paste into the console I have running on the right? I know I cannot turn modifiable on but is there any way to send a paste command to the :term job?
>
> I use code similar to this:
>
> nnoremap <silent> <leader>x :<c-u>call TermSend([getline('.')])<cr>
> vnoremap <silent> <leader>x :<c-u>call TermSend(GetSelection())<cr>
>
> fun! TermSend(lines)
> if empty(get(b:, 'bound_terminal', '')) ||
> \ !bufexists(b:bound_terminal)
> let b:bound_terminal = str2nr(input('Terminal buffer: '))
> endif
> for l:line in a:lines
> call term_sendkeys(b:bound_terminal, l:line . "\r")
> endfor
> call cursor(line('.') + 1, 1) " Move to the next line
> endf
>
> fun! GetSelection()
> if getpos("'>") != [0, 0, 0, 0]
> let [lnum1, col1] = getpos("'<")[1:2]
> let [lnum2, col2] = getpos("'>")[1:2]
> let l:lines = getline(lnum1, lnum2)
> let l:lines[-1] = lines[-1][:col2-(&selection=='inclusive'?1:2)]
> let l:lines[0] = l:lines[0][col1 - 1:]
> return l:lines
> else
> return []
> end
> endf
>
> Then typing \x will send the current line or the current selection to
> a terminal buffer (the first time, you are prompted to choose the
> buffer's number). The function sends one line at a time: it is slower
> than sending the whole text in one swoop, but I have found it to be more
> reliable.
>
> Now, if only there was a simpler way to get the currently selected text…
>
> Enjoy,
> Life.

Thanks for the detailed reply. Very informative,
Cheers
Kelvin

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

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

Re: Paste into a :term window?

Thanks Marcin, this is just what I needed. Not sure how I missed this when reading the help!

Thanks
Kelvin

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

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

Re: Paste into a :term window?

-----BEGIN PGP SIGNATURE-----
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAQBQJb1BwqCRBjqi+J2p/qkgAA5MEH/AxHo1qjFCfg2tKrT/hD
njsuebaEnALZpycHMjiaHsm1IUYa7oDqf3n1hwzSvZfFZSJF2jEtg6cfY5DH
r/Rr/MzdPOacHFiJ+QJoDeFMbEdoAln3wxHbca6rBpnVWFLrSIEFejONpRPe
kJKhaHKznoNdMDVPnUnH6DMP6WzPJD2nKvA+KUZIO/YH7TwR4y6/fmDn53uZ
cVjnSRt/mHNfSU/RA+IxxoG/n8X198c7IRoCss0Dd/DUs/IANaIPbosElWo+
4XzdHQvrwta8424aD0gp1745bjDORy28I0rCYDiiRnTJY1zxJDm8oE3tWCaq
ijA8qwXQHRy0nUPqIjQDXYM=
=ScW5
-----END PGP SIGNATURE-----

Hi,

There's Ctrl-w-" followed by a register name, which puts the register in a terminal. It works only in terminal mode. Check out `:h terminal-typing`.

Best regards,
Marcin

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

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

Re: Paste into a :term window?

On 25/10/2018 17:32, Kelvin Lawrence wrote:
> I'm enjoying the new :term feature in 8.1
>
> I have my code on the left and a job running on the right. The job is a console environment for Groovy. Is there an easy way to copy from the code on the left and paste into the console I have running on the right? I know I cannot turn modifiable on but is there any way to send a paste command to the :term job?

I use code similar to this:

nnoremap <silent> <leader>x :<c-u>call TermSend([getline('.')])<cr>
vnoremap <silent> <leader>x :<c-u>call TermSend(GetSelection())<cr>

fun! TermSend(lines)
if empty(get(b:, 'bound_terminal', '')) ||
\ !bufexists(b:bound_terminal)
let b:bound_terminal = str2nr(input('Terminal buffer: '))
endif
for l:line in a:lines
call term_sendkeys(b:bound_terminal, l:line . "\r")
endfor
call cursor(line('.') + 1, 1) " Move to the next line
endf

fun! GetSelection()
if getpos("'>") != [0, 0, 0, 0]
let [lnum1, col1] = getpos("'<")[1:2]
let [lnum2, col2] = getpos("'>")[1:2]
let l:lines = getline(lnum1, lnum2)
let l:lines[-1] = lines[-1][:col2-(&selection=='inclusive'?1:2)]
let l:lines[0] = l:lines[0][col1 - 1:]
return l:lines
else
return []
end
endf

Then typing \x will send the current line or the current selection to
a terminal buffer (the first time, you are prompted to choose the
buffer's number). The function sends one line at a time: it is slower
than sending the whole text in one swoop, but I have found it to be more
reliable.

Now, if only there was a simpler way to get the currently selected text…

Enjoy,
Life.

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

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

Paste into a :term window?

I'm enjoying the new :term feature in 8.1

I have my code on the left and a job running on the right. The job is a console environment for Groovy. Is there an easy way to copy from the code on the left and paste into the console I have running on the right? I know I cannot turn modifiable on but is there any way to send a paste command to the :term job?

I am using MacVim.

Many thanks in advance
Kelvin

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

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

Re: Showing shell output in GVim's window

Christian Brabandt to Anton Shepelev:

> Just a guess, but is your winpty.dll of the same
> architecture as your Vim (32bit vs 46bit)?

So it seems! When I try to run it manually in my 32-bit
Windows XP, it says it is not a valid Win32 application,
which is very strange, because it came with the 32-bit
distribution of GVim. Is it a packaging error?

--
Please, do not forward replies to my e-mail.

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

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

Re: Showing shell output in GVim's window

On So, 21 Okt 2018, Anton Shepelev wrote:

> With this option, I get:
>
> winpty-agent Createprocess failed:
>
> followed by an invocation of winpty-agent with a pipe name
> and --create-desktop. At the end it says: "err=0xc1". I
> don't know how to copy this error message from GVim's
> window.

Just a guess, but is your winpty.dll of the same architecture as your
Vim (32bit vs 46bit)?

Best,
Christian
--
Wenn ich irre, kann es jeder bemerken, wenn ich lüge, nicht.
-- Goethe, Maximen und Reflektionen, Nr. 225

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

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

Re: Showing shell output in GVim's window

Bram Moolenaar:

> With Vim 8.1 and later, you can use ":set go+=!".

With this option, I get:

winpty-agent Createprocess failed:

followed by an invocation of winpty-agent with a pipe name
and --create-desktop. At the end it says: "err=0xc1". I
don't know how to copy this error message from GVim's
window.

> The problem on MS-Windows is that redirection doesn't work
> properly.

If you meant the redirection of stdin, stdout, and stderr,
then what is the problem? I have recently written a cross-
platform program in Pascal that runs an extermal command
with redirected input and outputs. On Windows, it starts
the external process using CreateProcess(), then enters a
loop where it polls the output handles without blocking with
PeekNamedPipe() and ReadFile(), and writes to the input
handle with WriteFile(). PeekNamedPipe() does work with
anonymous pipes.

--
Please, do not forward replies to my e-mail.

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

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

Re: Cursor stays in command line after echo invoked with pumvisible() == 1

On 21/10/2018 12:59, Lifepillar wrote:
> On 07/09/2018 20:58, Lifepillar wrote:
>> If you run `vim --clean` (I have tried with Vim 8.1.300) and
>> source this:
>>
>> fun! Act()
>>    echo "The cursor gets stuck here ->"
>>    return ''
>> endf
>>
>> " 1. Trigger keyword completion (<c-x><c-n)
>> " 2. Force waiting for the pop-up menu to appear (<c-r>==''<cr>)
>> " 3. Invoke Act() with pumvisible() == 1 (<plug>(Act)
>> fun! Complete()
>>    return "\<c-x>\<c-n>\<c-r>=''\<cr>\<plug>(Act)"
>> endf
>>
>> imap <silent> <expr> <plug>(Act) Act()
>> imap <expr> <tab> Complete()
>>
>> set completeopt=menu
>> set noshowmode
>>
>> then (in the same buffer) type something like `s<tab>`: you should see
>> that the pop-up menu appears, but the cursor stays in the command line
>> until you press another character.
>>
>> Is there a way to avoid that, i.e., to have the cursor stays in the
>> buffer? Tried redraw after echo, but it does not change anything;
>> redraw! leaves the cursor at the bottom-right angle of the menu instead.
>
> Forcing a status line redraw (e.g., let &ro=&ro) fixes the issue (thanks
> to Github user @cwfoo)

That's user @mg979. Sorry.

Life.

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

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

Re: Cursor stays in command line after echo invoked with pumvisible() == 1

On 07/09/2018 20:58, Lifepillar wrote:
> If you run `vim --clean` (I have tried with Vim 8.1.300) and
> source this:
>
> fun! Act()
>   echo "The cursor gets stuck here ->"
>   return ''
> endf
>
> " 1. Trigger keyword completion (<c-x><c-n)
> " 2. Force waiting for the pop-up menu to appear (<c-r>==''<cr>)
> " 3. Invoke Act() with pumvisible() == 1 (<plug>(Act)
> fun! Complete()
>   return "\<c-x>\<c-n>\<c-r>=''\<cr>\<plug>(Act)"
> endf
>
> imap <silent> <expr> <plug>(Act) Act()
> imap <expr> <tab> Complete()
>
> set completeopt=menu
> set noshowmode
>
> then (in the same buffer) type something like `s<tab>`: you should see
> that the pop-up menu appears, but the cursor stays in the command line
> until you press another character.
>
> Is there a way to avoid that, i.e., to have the cursor stays in the
> buffer? Tried redraw after echo, but it does not change anything;
> redraw! leaves the cursor at the bottom-right angle of the menu instead.

Forcing a status line redraw (e.g., let &ro=&ro) fixes the issue (thanks
to Github user @cwfoo). The status line must be visible, though.
The fixed example follows.

Life.

fun! Act()
echo "The cursor won't get stuck here ->"
let &ro=&ro
return ''
endf

fun! Complete()
return "\<c-x>\<c-n>\<c-r>=''\<cr>\<plug>(Act)"
endf

imap <silent> <expr> <plug>(Act) Act()
imap <expr> <tab> Complete()

se cot=menu
set noshowmode
set laststatus=2

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

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

Re: Showing shell output in GVim's window

On Sat, Oct 20, 2018 at 4:24 PM Bram Moolenaar <Bram@moolenaar.net> wrote:
>
>
> Tony wrote:
>
> > On Sat, Oct 20, 2018 at 11:03 AM Bram Moolenaar <Bram@moolenaar.net> wrote:
> > > With Vim 8.1 and later, you can use ":set go+=!".
> > > It doesn't work perfectly, because of how it uses a virtual console.
> >
> > Ah, that's why I get what Anton wants: my vimrc indeed sets the ! flag
> > in 'guioptions'. Of course it means that external commands are run in
> > gvim's "dumb" console (glass teletype) and won't be able to use
> > backward cursor moves as in ncurses.
>
> Since it's now using the built-in terminal emulator, it's a full
> terminal, not "dumb". The problem on MS-Windows is that redirection
> doesn't work properly.

The binary where I tested it was built with -terminal. There (with !
in 'guioptions'), the output of external commands appears in the
command-line area, pushing all windows upwards. It may be different in
a gvim with +terminal — I have one but I only rarely use it. Sorry for
jumping to conclusions.

Here are the configuration parameters for my "usual" Vim:

export CONF_OPT_GUI='--enable-gui=gtk2'
export CONF_OPT_MULTIBYTE='--enable-multibyte'
export CONF_OPT_AUTOSERVE='--enable-autoservername'
export CONF_OPT_FEAT='--with-features=big'
export CONF_OPT_COMPBY='"--with-compiledby=antoine.mechelynck@gmail.com"'

Multibyte and GTK2 but no interpreted language interfaces, no
terminal, and none of the few features normally present in Huge but
not in Big. In addition to this, I set +xterm_save and -tag_old_static
by patching feature.h because AFAIK there are no configure arguments
for them.

Best regards,
Tony.

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

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

Re: Showing shell output in GVim's window

Tony wrote:

> On Sat, Oct 20, 2018 at 11:03 AM Bram Moolenaar <Bram@moolenaar.net> wrote:
> > With Vim 8.1 and later, you can use ":set go+=!".
> > It doesn't work perfectly, because of how it uses a virtual console.
>
> Ah, that's why I get what Anton wants: my vimrc indeed sets the ! flag
> in 'guioptions'. Of course it means that external commands are run in
> gvim's "dumb" console (glass teletype) and won't be able to use
> backward cursor moves as in ncurses.

Since it's now using the built-in terminal emulator, it's a full
terminal, not "dumb". The problem on MS-Windows is that redirection
doesn't work properly.

--
"After a few years of marriage a man can look right at a woman
without seeing her and a woman can see right through a man
without looking at him."
- Helen Rowland

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

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

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

Re: Showing shell output in GVim's window

On Sat, Oct 20, 2018 at 11:03 AM Bram Moolenaar <Bram@moolenaar.net> wrote:
> With Vim 8.1 and later, you can use ":set go+=!".
> It doesn't work perfectly, because of how it uses a virtual console.

Ah, that's why I get what Anton wants: my vimrc indeed sets the ! flag
in 'guioptions'. Of course it means that external commands are run in
gvim's "dumb" console (glass teletype) and won't be able to use
backward cursor moves as in ncurses.

Best regards,
Tony.

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

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

Re: Showing shell output in GVim's window

Anton Shepelev wrote:

> While working with the console version of Vim, the output of
> the ! command is shown in the same terminal window, whereas
> with GVim a new console window pops up. Is it possible to
> configure GVim to show the shell in its own wiindow for a
> more unified experience? With the current behavior, the
> edit-compile-test cycle in GVim is somewhat uncomfortable.

With Vim 8.1 and later, you can use ":set go+=!".
It doesn't work perfectly, because of how it uses a virtual console.

--
"Marriage is a wonderful institution...
but who wants to live in an institution?"
- Groucho Marx

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

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

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

Re: Showing shell output in GVim's window

On Fri, Oct 19, 2018 at 10:58 PM Anton Shepelev <anton.txt@gmail.com> wrote:
>
> Hello, all
>
> While working with the console version of Vim, the output of
> the ! command is shown in the same terminal window, whereas
> with GVim a new console window pops up. Is it possible to
> configure GVim to show the shell in its own wiindow for a
> more unified experience? With the current behavior, the
> edit-compile-test cycle in GVim is somewhat uncomfortable.

This may either be operating-system-dependent, or else depend on some option.
In my Big gvim for Linux64, and with my usual vimrc, the multiline
output of ! external commands appears at the very bottom of the Vim
screen, pushing all windows up, and ends with a |hit-enter-prompt|,
just as if it were a multiline message frm Vim itself.

Best regards,
Tony.

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

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

Showing shell output in GVim's window

Hello, all

While working with the console version of Vim, the output of
the ! command is shown in the same terminal window, whereas
with GVim a new console window pops up. Is it possible to
configure GVim to show the shell in its own wiindow for a
more unified experience? With the current behavior, the
edit-compile-test cycle in GVim is somewhat uncomfortable.

--
Please, do not forward replies to my e-mail.

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

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

Re: gvim and sliding command output animation

On 19.10.2018 20:18, Oliver Knodel wrote:
> After a small test, I can confirm this behavior. Arch Linux, I3 WM no
> compositor. :registers scrolling up line by line. Not very slow, but
> I noticed it.
Thanks for taking time to confirm this. I haven't got around to checking
how other OSes/DEs behave. I was sure it wouldn't be an
environment-specific behaviour.

Hopefully someone can shred some light on why this is happening, and
also why it doesn't happen for :messages, and finally how to remove this
animation.

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

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

Re: gvim and sliding command output animation

Am Donnerstag, 18. Oktober 2018 12:13:21 UTC+2 schrieb Steven Holt:
> On 18.10.2018 11:40, John Little wrote:
> > On Wednesday, October 17, 2018 at 9:28:41 PM UTC+13, Steven Holt
> > wrote:
> >> Any thoughts?
> >
> > I'm sorry I'm not much help. Originally I thought I'd just pop up
> > and ask the obvious questions (version, OS, DE).
> >
> > I simply don't understand your sureness "it's an animation done on
> > purpose".
> It's mainly due to the fact that :messages open instantly while other
> (:cl, etc.) open with a sliding animation.
>
> If it was due to the compositor, GTK version or other global property of
> my system, would not :messages suffer from the same issue as :cl? This
> is my reasoning.
>
> > gvim is a very thin skin on terminal vim, especially for the main
> > text area. Your video plays very quickly for me, I have to play it
> > at half speed to notice anything.
> >
> > I suggest you try a vim GTK2 version. I've fired up a GTK3 vim here
> > and it seems a little slower, but nothing worth your complaint.
> > AFAIK GTK3 adds nothing to vim, though some theming might work
> > differently.
> >
> > You might try changing the font, or some graphics setting of your
> > set-up, like the rendering backend your compositor uses. You didn't
> > mention your DE, that is Gnome, KDE, XFCE, et cetera.
> I've mentioned it. My DE is i3, i3wm.org.
>
> > Conceivably another DE might drive your hardware better.
> >
> > If your eyes are hurting, and you normally use white or light
> > backgrounds, IMO dark backgrounds (preferably black for text) are far
> > easier on the eyes.
> >
> > To make progress on what's actually going on you'd have to start
> > profiling vim, a lot of work with little prospect of achieving
> > anything.
> >
> > Regards, John Little
> >
>
> I see, thanks for your feedback, John.

After a small test, I can confirm this behavior. Arch Linux, I3 WM no compositor. :registers scrolling up line by line. Not very slow, but I noticed it.

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

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

Re: gvim and sliding command output animation

On Thursday, October 18, 2018 at 11:13:21 PM UTC+13, Steven Holt wrote:

> I've mentioned it. My DE is i3, i3wm.org.

Sorry, I saw i3, and without thinking assumed it meant an Intel i3 CPU. It's a very long time since I used a tiling window manager.

Regards, John Little

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

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

Re: gvim and sliding command output animation

On 18.10.2018 11:40, John Little wrote:
> On Wednesday, October 17, 2018 at 9:28:41 PM UTC+13, Steven Holt
> wrote:
>> Any thoughts?
>
> I'm sorry I'm not much help. Originally I thought I'd just pop up
> and ask the obvious questions (version, OS, DE).
>
> I simply don't understand your sureness "it's an animation done on
> purpose".
It's mainly due to the fact that :messages open instantly while other
(:cl, etc.) open with a sliding animation.

If it was due to the compositor, GTK version or other global property of
my system, would not :messages suffer from the same issue as :cl? This
is my reasoning.

> gvim is a very thin skin on terminal vim, especially for the main
> text area. Your video plays very quickly for me, I have to play it
> at half speed to notice anything.
>
> I suggest you try a vim GTK2 version. I've fired up a GTK3 vim here
> and it seems a little slower, but nothing worth your complaint.
> AFAIK GTK3 adds nothing to vim, though some theming might work
> differently.
>
> You might try changing the font, or some graphics setting of your
> set-up, like the rendering backend your compositor uses. You didn't
> mention your DE, that is Gnome, KDE, XFCE, et cetera.
I've mentioned it. My DE is i3, i3wm.org.

> Conceivably another DE might drive your hardware better.
>
> If your eyes are hurting, and you normally use white or light
> backgrounds, IMO dark backgrounds (preferably black for text) are far
> easier on the eyes.
>
> To make progress on what's actually going on you'd have to start
> profiling vim, a lot of work with little prospect of achieving
> anything.
>
> Regards, John Little
>

I see, thanks for your feedback, John.

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

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

Re: gvim and sliding command output animation

On Wednesday, October 17, 2018 at 9:28:41 PM UTC+13, Steven Holt wrote:
> Any thoughts?

I'm sorry I'm not much help. Originally I thought I'd just pop up and ask the obvious questions (version, OS, DE).

I simply don't understand your sureness "it's an animation done on purpose". gvim is a very thin skin on terminal vim, especially for the main text area. Your video plays very quickly for me, I have to play it at half speed to notice anything.

I suggest you try a vim GTK2 version. I've fired up a GTK3 vim here and it seems a little slower, but nothing worth your complaint. AFAIK GTK3 adds nothing to vim, though some theming might work differently.

You might try changing the font, or some graphics setting of your set-up, like the rendering backend your compositor uses. You didn't mention your DE, that is Gnome, KDE, XFCE, et cetera. Conceivably another DE might drive your hardware better.

If your eyes are hurting, and you normally use white or light backgrounds, IMO dark backgrounds (preferably black for text) are far easier on the eyes.

To make progress on what's actually going on you'd have to start profiling vim, a lot of work with little prospect of achieving anything.

Regards, John Little

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

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

Re: gvim and sliding command output animation

I have noticed that output of :messages appears instantly, unlike the
sliding output of :reg, :ls, :cl, etc. etc. I'm puzzled because
:messages seems to be using the same 'more' pager so why this difference?

On 16.10.2018 12:07, Steven Holt wrote:
> On 14.10.2018 13:19, John Little wrote:
>> On Sunday, October 14, 2018 at 9:58:54 PM UTC+13, Steven Holt wrote:
>>> In gvim, the output is sliding line by line from the status line
>>> to the top window edge which takes maybe a second or two ...
>>
>> I don't see this, gvim 8.1.0438 Huge version with GTK2 GUI, on
>> Kubuntu 18.04. :ls on 116 buffers and a vertically maximized gvim is
>> imperceptible. (If I maximize horizontally as well, I get an annoying
>> status line flash ⅓ and ⅔ up, but it's quick.)
> Now that I've recorded a video I see it's also quite quick (less than a
> second) but when I'm in the middle of a work it feels very different.
>
>> So, what OS, DE, and vim version?
> Arch, i3, gvim 8.1. Attached full --version output.
>
> Also attached screen recording of how it works for me (gvim -u NONE -U
> NONE). Near the end of the video when I :cl twice you can clearly see
> that the more prompt is sliding up with several distinct steps. I'm sure
> it's an animation done on purpose, not screen redraw issues because
> other operations such as resizing windows (I did ^w-_ and ^w-r at the
> end of the video) are instant (and because terminal :cl is equally
> instant even if made fullscreen).
>
> Any 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.
For more options, visit https://groups.google.com/d/optout.

breakindent with hardcopy (print)

I just found out about the breakindent feature which is cool. It looks good in the GVim_breakindent.png attachment. However, when I print or ":hardcopy" the file, it doesn't keep maintain these indents (see hardcopy.pdf attachment). Is this true? Can this be a feature that's added some day in the future? Also, the TOhtml doesn't maintain these either.

Thanks,
Bryce

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

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

Re: ***note*** handling a large file

On Monday, October 15, 2018 at 7:43:34 PM UTC+13, Deepak kumar wrote:
> Is there any way to avoid warning "***note*** handling a large file" while opening a large file?

The message comes from the LargeFile.vim plugin, so you could just find from where it's being loaded, and remove it. You could run :scriptnames to see where it came from.

Or, to disable it you could add

let g:loaded_LargeFile = -1

to your .vimrc.

If you want the functionality, but just don't want the message, you could hack the plugin. It's quite simple and short.

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

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

Vim starts with multiple (3) windows

Hello All,

All of sudden, today whenever I wanted to startup a new instance of gVim (does not do it in Vim) I get 3 horizontal windows at once. I don't remember changing any of my settings in sometime. I am running version 8.0.586.

Thanks for your help in advance.

Hilal

Re: _vimrc loading fails

Le mardi 16 octobre 2018 16:09:35 UTC+2, Christian Brabandt a écrit :
> On Di, 16 Okt 2018, Ni Va wrote:
>
> > Found a finish at line 143 of $MYVIMRC in case of python dll where not loaded.
> >
> > Sorry for inconvenience.
>
> Now you know, why a minimum reproducible example is helpful ;)
>
> Best,
> Christian
> --
> Deswegen sind Bücher willkommen, die uns sowohl das neu
> Empirisch-Aufgefundene als die neu beliebten Methoden darlegen.
> -- Goethe, Maximen und Reflektionen, Nr. 952

Yess ! Sorry! Got a real pb to load python dll dynamically on another computer with standalone strategy

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

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

Re: _vimrc loading fails

On Di, 16 Okt 2018, Ni Va wrote:

> Found a finish at line 143 of $MYVIMRC in case of python dll where not loaded.
>
> Sorry for inconvenience.

Now you know, why a minimum reproducible example is helpful ;)

Best,
Christian
--
Deswegen sind Bücher willkommen, die uns sowohl das neu
Empirisch-Aufgefundene als die neu beliebten Methoden darlegen.
-- Goethe, Maximen und Reflektionen, Nr. 952

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

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

Re: _vimrc loading fails

Le mardi 16 octobre 2018 14:01:34 UTC+2, Ni Va a écrit :
> Le mardi 16 octobre 2018 13:15:50 UTC+2, Christian Brabandt a écrit :
> > On Di, 16 Okt 2018, Ni Va wrote:
> >
> > > Moving Vim_x86/_vimrc to Vim_x86/vimrc and same problem colors not loaded.
> >
> > Works for me with your zip file. Are you sure, no other initialization
> > file overwrites your colorscheme? Is nivacolors in the output of
> > :scriptnames?
> >
> > Also, check your runtimepath setting so that the colorscheme will be
> > found.
> >
> > > => echo $HOME returns void string.
> > >
> > > I thought $HOME was set by Vim and not that user had to set it, no ?
> >
> > IIRC, Vim sets it by concatenating $HOMEDRIVE and $HOMEPATH if it is not
> > $HOME does not exist.
> >
> > Best,
> > Christian
>
> 1. Confirm that nivacolors.vim is not listed from command :scriptnames.
>
> 2. I don't think there is other initialization file.
>
> But I use C:\ThirdParty dll loading for ruby python lua etc.. and I wonder if an error catched stop _vimrc complete loading.
>
> 3. $HOMEDRIVE c:\ and $HOMEPATH looks good \Users\foo.bar

Found a finish at line 143 of $MYVIMRC in case of python dll where not loaded.

Sorry for inconvenience.

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

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

Re: _vimrc loading fails

Le mardi 16 octobre 2018 13:15:50 UTC+2, Christian Brabandt a écrit :
> On Di, 16 Okt 2018, Ni Va wrote:
>
> > Moving Vim_x86/_vimrc to Vim_x86/vimrc and same problem colors not loaded.
>
> Works for me with your zip file. Are you sure, no other initialization
> file overwrites your colorscheme? Is nivacolors in the output of
> :scriptnames?
>
> Also, check your runtimepath setting so that the colorscheme will be
> found.
>
> > => echo $HOME returns void string.
> >
> > I thought $HOME was set by Vim and not that user had to set it, no ?
>
> IIRC, Vim sets it by concatenating $HOMEDRIVE and $HOMEPATH if it is not
> $HOME does not exist.
>
> Best,
> Christian

1. Confirm that nivacolors.vim is not listed from command :scriptnames.

2. I don't think there is other initialization file.

But I use C:\ThirdParty dll loading for ruby python lua etc.. and I wonder if an error catched stop _vimrc complete loading.

3. $HOMEDRIVE c:\ and $HOMEPATH looks good \Users\foo.bar

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

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

Re: _vimrc loading fails

On Di, 16 Okt 2018, Ni Va wrote:

> Moving Vim_x86/_vimrc to Vim_x86/vimrc and same problem colors not loaded.

Works for me with your zip file. Are you sure, no other initialization
file overwrites your colorscheme? Is nivacolors in the output of
:scriptnames?

Also, check your runtimepath setting so that the colorscheme will be
found.

> => echo $HOME returns void string.
>
> I thought $HOME was set by Vim and not that user had to set it, no ?

IIRC, Vim sets it by concatenating $HOMEDRIVE and $HOMEPATH if it is not
$HOME does not exist.

Best,
Christian

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

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

Re: _vimrc loading fails

Le mardi 16 octobre 2018 12:26:24 UTC+2, Christian Brabandt a écrit :
> On Di, 16 Okt 2018, Ni Va wrote:
>
> > > BTW: you still did not response to the difference in the runtime path
> > > settings of $HOME.
> >
> > Minimal reproducible example:
> >
> >
> > 1. Download this gvim 32bits build 8.1.479 with HUGE feats
> > From https://drive.google.com/open?id=1PA6uhn-8P_ELc7HquW5zaEpc8yBlgKHt
> > 2. Unzip it on desktop under Windows Seven or 10
> > 3. See if colorscheme nivacolors is loaded and colors like the attached PNG.
>
> Same problem. $HOME is not set correctly. Move your Vim_x86/_vimrc to
> Vim_x86/vimrc and it will be sourced. Note, Vim will load $VIM/vimrc
> (note the missing '_') as system vimrc file.
>
> See the output of `:version` where Vim expects the vimrc file and then
> check carefully your $HOME and $VIM variables if they match what you
> expect.
>
> Best,
> Christian
> --
> Wer mit Gott Freund sein will, muß allein bleiben oder die ganze Welt
> zu seinem Freund machen.
> -- Mahatma Gandhi

Moving Vim_x86/_vimrc to Vim_x86/vimrc and same problem colors not loaded.
=> echo $HOME returns void string.

I thought $HOME was set by Vim and not that user had to set it, no ?

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

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

Re: _vimrc loading fails

On Di, 16 Okt 2018, Ni Va wrote:

> > BTW: you still did not response to the difference in the runtime path
> > settings of $HOME.
>
> Minimal reproducible example:
>
>
> 1. Download this gvim 32bits build 8.1.479 with HUGE feats
> From https://drive.google.com/open?id=1PA6uhn-8P_ELc7HquW5zaEpc8yBlgKHt
> 2. Unzip it on desktop under Windows Seven or 10
> 3. See if colorscheme nivacolors is loaded and colors like the attached PNG.

Same problem. $HOME is not set correctly. Move your Vim_x86/_vimrc to
Vim_x86/vimrc and it will be sourced. Note, Vim will load $VIM/vimrc
(note the missing '_') as system vimrc file.

See the output of `:version` where Vim expects the vimrc file and then
check carefully your $HOME and $VIM variables if they match what you
expect.

Best,
Christian
--
Wer mit Gott Freund sein will, muß allein bleiben oder die ganze Welt
zu seinem Freund machen.
-- Mahatma Gandhi

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

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

Re: _vimrc loading fails

Le mardi 16 octobre 2018 10:59:51 UTC+2, Christian Brabandt a écrit :
> On Di, 16 Okt 2018, Ni Va wrote:
>
> > And _vimrc used in both cases.
>
> As said before, please create a minimal reproducible example. I don't
> think anybody will have fun trying to debug a hundred lines long vimrc.
>
> BTW: you still did not response to the difference in the runtime path
> settings of $HOME.
>
> Best,
> Christian
> --
> Denn niemand ist so alt, daß er nicht glaubte, noch ein Jahr leben zu
> können.
> -- Marcus Tullius Cicero (106-43 v.Chr.)

Minimal reproducible example:


1. Download this gvim 32bits build 8.1.479 with HUGE feats
From https://drive.google.com/open?id=1PA6uhn-8P_ELc7HquW5zaEpc8yBlgKHt
2. Unzip it on desktop under Windows Seven or 10
3. See if colorscheme nivacolors is loaded and colors like the attached PNG.


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

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

Re: gvim and sliding command output animation

VIM - Vi IMproved 8.1 (2018 May 18, compiled Aug 29 2018 20:42:12)
Included patches: 1-333
Compiled by Arch Linux
Huge version with GTK3 GUI. Features included (+) or not (-):
+acl +extra_search +mouse_netterm +tag_old_static
+arabic +farsi +mouse_sgr -tag_any_white
+autocmd +file_in_path -mouse_sysmouse +tcl/dyn
+autochdir +find_in_path +mouse_urxvt +termguicolors
-autoservername +float +mouse_xterm +terminal
+balloon_eval +folding +multi_byte +terminfo
+balloon_eval_term -footer +multi_lang +termresponse
+browse +fork() -mzscheme +textobjects
++builtin_terms +gettext +netbeans_intg +timers
+byte_offset -hangul_input +num64 +title
+channel +iconv +packages +toolbar
+cindent +insert_expand +path_extra +user_commands
+clientserver +job +perl/dyn +vartabs
+clipboard +jumplist +persistent_undo +vertsplit
+cmdline_compl +keymap +postscript +virtualedit
+cmdline_hist +lambda +printer +visual
+cmdline_info +langmap +profile +visualextra
+comments +libcall +python/dyn +viminfo
+conceal +linebreak +python3/dyn +vreplace
+cryptv +lispindent +quickfix +wildignore
+cscope +listcmds +reltime +wildmenu
+cursorbind +localmap +rightleft +windows
+cursorshape +lua/dyn +ruby/dyn +writebackup
+dialog_con_gui +menu +scrollbind +X11
+diff +mksession +signs -xfontset
+digraphs +modify_fname +smartindent +xim
+dnd +mouse +startuptime -xpm
-ebcdic +mouseshape +statusline +xsmp_interact
+emacs_tags +mouse_dec -sun_workshop +xterm_clipboard
+eval +mouse_gpm +syntax -xterm_save
+ex_extra -mouse_jsbterm +tag_binary
system vimrc file: "/etc/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
system gvimrc file: "/etc/gvimrc"
user gvimrc file: "$HOME/.gvimrc"
2nd user gvimrc file: "~/.vim/gvimrc"
defaults file: "$VIMRUNTIME/defaults.vim"
system menu file: "$VIMRUNTIME/menu.vim"
fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/harfbuzz -I/usr/include/uuid -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/libdrm -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -pthread -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc -L. -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -fstack-protector -rdynamic -Wl,-export-dynamic -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.28/core_perl/CORE -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -L/usr/local/lib -Wl,--as-needed -o vim -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lSM -lICE -lXt -lX11 -lXdmcp -lSM -lICE -lm -ltinfo -lelf -lnsl -lacl -lattr -lgpm -ldl -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.28/core_perl/CORE -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -fstack-protector-strong -L/usr/local/lib -L/usr/lib/perl5/5.28/core_perl/CORE -lperl -lpthread -ldl -lm -lcrypt -lutil -lc -L/usr/lib -ltclstub8.6 -ldl -lz -lpthread -lm
On 14.10.2018 13:19, John Little wrote:
> On Sunday, October 14, 2018 at 9:58:54 PM UTC+13, Steven Holt wrote:
>> In gvim, the output is sliding line by line from the status line
>> to the top window edge which takes maybe a second or two ...
>
> I don't see this, gvim 8.1.0438 Huge version with GTK2 GUI, on
> Kubuntu 18.04. :ls on 116 buffers and a vertically maximized gvim is
> imperceptible. (If I maximize horizontally as well, I get an annoying
> status line flash ⅓ and ⅔ up, but it's quick.)
Now that I've recorded a video I see it's also quite quick (less than a
second) but when I'm in the middle of a work it feels very different.

> So, what OS, DE, and vim version?
Arch, i3, gvim 8.1. Attached full --version output.

Also attached screen recording of how it works for me (gvim -u NONE -U
NONE). Near the end of the video when I :cl twice you can clearly see
that the more prompt is sliding up with several distinct steps. I'm sure
it's an animation done on purpose, not screen redraw issues because
other operations such as resizing windows (I did ^w-_ and ^w-r at the
end of the video) are instant (and because terminal :cl is equally
instant even if made fullscreen).

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

Re: _vimrc loading fails

On Di, 16 Okt 2018, Ni Va wrote:

> And _vimrc used in both cases.

As said before, please create a minimal reproducible example. I don't
think anybody will have fun trying to debug a hundred lines long vimrc.

BTW: you still did not response to the difference in the runtime path
settings of $HOME.

Best,
Christian
--
Denn niemand ist so alt, daß er nicht glaubte, noch ein Jahr leben zu
können.
-- Marcus Tullius Cicero (106-43 v.Chr.)

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

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

Re: _vimrc loading fails

Le mardi 16 octobre 2018 09:20:41 UTC+2, Ni Va a écrit :
> Le lundi 15 octobre 2018 15:40:15 UTC+2, Tony Mechelynck a écrit :
> > P.S. In "paste the result" I meant "paste what is then in the clipboard".
> >
> > Best regards,
> > Tony.
>
>
>
> Computer A OK
> VIM - Vi IMproved 8.1 (2018 May 18, compiled Oct 15 2018 10:30:57)
> MS-Windows 32-bit GUI version with OLE support
> Included patches: 1-477
> Compiled by foo.bar@foobar
> Huge version with GUI. Features included (+) or not (-):
> +acl +emacs_tags +mouseshape -tag_any_white
> +arabic +eval +multi_byte -tcl
> +autocmd +ex_extra +multi_lang -termguicolors
> +autochdir +extra_search -mzscheme +terminal
> +autoservername +farsi -netbeans_intg -tgetent
> +balloon_eval +file_in_path +num64 -termresponse
> -balloon_eval_term +find_in_path +ole +textobjects
> +browse +float +packages +timers
> ++builtin_terms +folding +path_extra +title
> +byte_offset -footer -perl +toolbar
> +channel +gettext/dyn +persistent_undo +user_commands
> +cindent -hangul_input -postscript +vartabs
> +clientserver +iconv/dyn +printer +vertsplit
> +clipboard +insert_expand +profile +virtualedit
> +cmdline_compl +job +python/dyn +visual
> +cmdline_hist +jumplist +python3/dyn +visualextra
> +cmdline_info +keymap +quickfix +viminfo
> +comments +lambda +reltime +vreplace
> +conceal +langmap +rightleft -vtp
> +cryptv +libcall +ruby/dyn +wildignore
> -cscope +linebreak +scrollbind +wildmenu
> +cursorbind +lispindent +signs +windows
> +cursorshape +listcmds +smartindent +writebackup
> +dialog_con_gui +localmap +startuptime -xfontset
> +diff +lua/dyn +statusline -xim
> +digraphs +menu -sun_workshop -xpm_w32
> +directx +mksession +syntax -xterm_save
> -dnd +modify_fname +tag_binary
> -ebcdic +mouse +tag_old_static
> system vimrc file: "$VIM\vimrc"
> user vimrc file: "$HOME\_vimrc"
> 2nd user vimrc file: "$HOME\vimfiles\vimrc"
> 3rd user vimrc file: "$VIM\_vimrc"
> user exrc file: "$HOME\_exrc"
> 2nd user exrc file: "$VIM\_exrc"
> system gvimrc file: "$VIM\gvimrc"
> user gvimrc file: "$HOME\_gvimrc"
> 2nd user gvimrc file: "$HOME\vimfiles\gvimrc"
> 3rd user gvimrc file: "$VIM\_gvimrc"
> defaults file: "$VIMRUNTIME\defaults.vim"
> system menu file: "$VIMRUNTIME\menu.vim"
>
>
>
>
> Computer B KO
>
> VIM - Vi IMproved 8.1 (2018 May 18, compiled Oct 15 2018 10:30:57)
> MS-Windows 32-bit GUI version with OLE support
> Included patches: 1-477
> Compiled by foo.bar@foobar
> Huge version with GUI. Features included (+) or not (-):
> +acl +emacs_tags +mouseshape -tag_any_white
> +arabic +eval +multi_byte -tcl
> +autocmd +ex_extra +multi_lang -termguicolors
> +autochdir +extra_search -mzscheme +terminal
> +autoservername +farsi -netbeans_intg -tgetent
> +balloon_eval +file_in_path +num64 -termresponse
> -balloon_eval_term +find_in_path +ole +textobjects
> +browse +float +packages +timers
> ++builtin_terms +folding +path_extra +title
> +byte_offset -footer -perl +toolbar
> +channel +gettext/dyn +persistent_undo +user_commands
> +cindent -hangul_input -postscript +vartabs
> +clientserver +iconv/dyn +printer +vertsplit
> +clipboard +insert_expand +profile +virtualedit
> +cmdline_compl +job +python/dyn +visual
> +cmdline_hist +jumplist +python3/dyn +visualextra
> +cmdline_info +keymap +quickfix +viminfo
> +comments +lambda +reltime +vreplace
> +conceal +langmap +rightleft -vtp
> +cryptv +libcall +ruby/dyn +wildignore
> -cscope +linebreak +scrollbind +wildmenu
> +cursorbind +lispindent +signs +windows
> +cursorshape +listcmds +smartindent +writebackup
> +dialog_con_gui +localmap +startuptime -xfontset
> +diff +lua/dyn +statusline -xim
> +digraphs +menu -sun_workshop -xpm_w32
> +directx +mksession +syntax -xterm_save
> -dnd +modify_fname +tag_binary
> -ebcdic +mouse +tag_old_static
> system vimrc file: "$VIM\vimrc"
> user vimrc file: "$HOME\_vimrc"
> 2nd user vimrc file: "$HOME\vimfiles\vimrc"
> 3rd user vimrc file: "$VIM\_vimrc"
> user exrc file: "$HOME\_exrc"
> 2nd user exrc file: "$VIM\_exrc"
> system gvimrc file: "$VIM\gvimrc"
> user gvimrc file: "$HOME\_gvimrc"
> 2nd user gvimrc file: "$HOME\vimfiles\gvimrc"
> 3rd user gvimrc file: "$VIM\_gvimrc"
> defaults file: "$VIMRUNTIME\defaults.vim"
> system menu file: "$VIMRUNTIME\menu.vim"

And _vimrc used in both cases.

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

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

Re: _vimrc loading fails

Le lundi 15 octobre 2018 15:40:15 UTC+2, Tony Mechelynck a écrit :
> P.S. In "paste the result" I meant "paste what is then in the clipboard".
>
> Best regards,
> Tony.



Computer A OK
VIM - Vi IMproved 8.1 (2018 May 18, compiled Oct 15 2018 10:30:57)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-477
Compiled by foo.bar@foobar
Huge version with GUI. Features included (+) or not (-):
+acl +emacs_tags +mouseshape -tag_any_white
+arabic +eval +multi_byte -tcl
+autocmd +ex_extra +multi_lang -termguicolors
+autochdir +extra_search -mzscheme +terminal
+autoservername +farsi -netbeans_intg -tgetent
+balloon_eval +file_in_path +num64 -termresponse
-balloon_eval_term +find_in_path +ole +textobjects
+browse +float +packages +timers
++builtin_terms +folding +path_extra +title
+byte_offset -footer -perl +toolbar
+channel +gettext/dyn +persistent_undo +user_commands
+cindent -hangul_input -postscript +vartabs
+clientserver +iconv/dyn +printer +vertsplit
+clipboard +insert_expand +profile +virtualedit
+cmdline_compl +job +python/dyn +visual
+cmdline_hist +jumplist +python3/dyn +visualextra
+cmdline_info +keymap +quickfix +viminfo
+comments +lambda +reltime +vreplace
+conceal +langmap +rightleft -vtp
+cryptv +libcall +ruby/dyn +wildignore
-cscope +linebreak +scrollbind +wildmenu
+cursorbind +lispindent +signs +windows
+cursorshape +listcmds +smartindent +writebackup
+dialog_con_gui +localmap +startuptime -xfontset
+diff +lua/dyn +statusline -xim
+digraphs +menu -sun_workshop -xpm_w32
+directx +mksession +syntax -xterm_save
-dnd +modify_fname +tag_binary
-ebcdic +mouse +tag_old_static
system vimrc file: "$VIM\vimrc"
user vimrc file: "$HOME\_vimrc"
2nd user vimrc file: "$HOME\vimfiles\vimrc"
3rd user vimrc file: "$VIM\_vimrc"
user exrc file: "$HOME\_exrc"
2nd user exrc file: "$VIM\_exrc"
system gvimrc file: "$VIM\gvimrc"
user gvimrc file: "$HOME\_gvimrc"
2nd user gvimrc file: "$HOME\vimfiles\gvimrc"
3rd user gvimrc file: "$VIM\_gvimrc"
defaults file: "$VIMRUNTIME\defaults.vim"
system menu file: "$VIMRUNTIME\menu.vim"




Computer B KO

VIM - Vi IMproved 8.1 (2018 May 18, compiled Oct 15 2018 10:30:57)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-477
Compiled by foo.bar@foobar
Huge version with GUI. Features included (+) or not (-):
+acl +emacs_tags +mouseshape -tag_any_white
+arabic +eval +multi_byte -tcl
+autocmd +ex_extra +multi_lang -termguicolors
+autochdir +extra_search -mzscheme +terminal
+autoservername +farsi -netbeans_intg -tgetent
+balloon_eval +file_in_path +num64 -termresponse
-balloon_eval_term +find_in_path +ole +textobjects
+browse +float +packages +timers
++builtin_terms +folding +path_extra +title
+byte_offset -footer -perl +toolbar
+channel +gettext/dyn +persistent_undo +user_commands
+cindent -hangul_input -postscript +vartabs
+clientserver +iconv/dyn +printer +vertsplit
+clipboard +insert_expand +profile +virtualedit
+cmdline_compl +job +python/dyn +visual
+cmdline_hist +jumplist +python3/dyn +visualextra
+cmdline_info +keymap +quickfix +viminfo
+comments +lambda +reltime +vreplace
+conceal +langmap +rightleft -vtp
+cryptv +libcall +ruby/dyn +wildignore
-cscope +linebreak +scrollbind +wildmenu
+cursorbind +lispindent +signs +windows
+cursorshape +listcmds +smartindent +writebackup
+dialog_con_gui +localmap +startuptime -xfontset
+diff +lua/dyn +statusline -xim
+digraphs +menu -sun_workshop -xpm_w32
+directx +mksession +syntax -xterm_save
-dnd +modify_fname +tag_binary
-ebcdic +mouse +tag_old_static
system vimrc file: "$VIM\vimrc"
user vimrc file: "$HOME\_vimrc"
2nd user vimrc file: "$HOME\vimfiles\vimrc"
3rd user vimrc file: "$VIM\_vimrc"
user exrc file: "$HOME\_exrc"
2nd user exrc file: "$VIM\_exrc"
system gvimrc file: "$VIM\gvimrc"
user gvimrc file: "$HOME\_gvimrc"
2nd user gvimrc file: "$HOME\vimfiles\gvimrc"
3rd user gvimrc file: "$VIM\_gvimrc"
defaults file: "$VIMRUNTIME\defaults.vim"
system menu file: "$VIMRUNTIME\menu.vim"

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

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

Re: vim syntax file for grub 2 grub.cfg

Before someone leaps to point this out, note that grub 2 is "bash-like", and the sh.vim syntax is useful, but can be misleading.

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

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

vim syntax file for grub 2 grub.cfg

Has anyone got a syntax file for Grub 2? The syntax/grub.vim is not useful, I presume it is for Grub legacy. vim presently "detects" grub.cfg as a .cfg file, which again is not useful.

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

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

Re: _vimrc loading fails

On Mo, 15 Okt 2018, Ni Va wrote:

> echo $VIM gives D:\Logiciels\Vim
> echo $VIMRUNTIME gives D:\Logiciels\Vim\vim81
>
>
> Computer B (KO) : Windows Seven
>
> echo $VIM gives C:\users\foobar\desktop\Vim_x86\Vim_x86
> echo $VIMRUNTIME gives C:\users\foobar\desktop\Vim_x86\Vim_x86\vim81

So what is about &rtp setting? What about $HOME?


Best,
Christian
--
Warum ist "einsilbig" dreisilbig?

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

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

Re: _vimrc loading fails

P.S. In "paste the result" I meant "paste what is then in the clipboard".

Best regards,
Tony.

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

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

Re: _vimrc loading fails

On Mon, Oct 15, 2018 at 2:43 PM Ni Va <nivaemail@gmail.com> wrote:
>
> Le lundi 15 octobre 2018 14:36:43 UTC+2, Tony Mechelynck a écrit :
> > On Mon, Oct 15, 2018 at 2:29 PM Ni Va <nivaemail@gmail.com> wrote:
> > >
> > > Le lundi 15 octobre 2018 14:07:29 UTC+2, Christian Brabandt a écrit :
> > > > On Mo, 15 Okt 2018, Ni Va wrote:
> > > >
> > > > > but I don't see syntax colors is missing out of this was loaded on
> > > > > initial computer
> > > > > 21: D:/Logiciels/Vim/vim81/syntax/nosyntax.vim
> > > >
> > > > nosyntax.vim will only be visible, if you issue `:syntax off`.
> > > >
> > > >
> > > > Best,
> > > > Christian
> > > > --
> > > > Der Abenteurer ist unentbehrlich, das wird allerdings erst
> > > > erkannt, wenn sich herausstellt, daß er Amerika entdeckt hat.
> > > > -- Ludwig Marcuse (Argumente und Rezepte)
> > >
> > > Ok so I don't understand why in one case $vim/vimfiles/colors/nivacolors.vim are loaded on computer A and in other case it is not.
> > >
> > > This load is called from $MYVIMRC : colors nivacolors.cim
> > >
> > > The only thing I note is difference directory from which gvim is launched.
> > >
> > > Computer A (OK) : D:\Softwares\Vim\vim81\gvim.exe
> > > Computer B (KO) : ~\Desktop\Vim\vim81\gvim.exe
> >
> > Well, unless you unintentionally made a typo, ":colors nivacolors.cim"
> > cannot load nivacolors.vim because the name is different.
> >
> > If it _is_ a typo, the following explanations are possible:
> > - the Vim executable which loads neither nosyntax.vim nor
> > nivacolors.vim was compiled with -syntax (see the output of :version)
> > - or else, it did not execute, respectively, the statements ":syntax
> > off" and ":colorscheme nivacolors". The suffix .vim is not necessary
> > in the command argument.
> >
> > Best regards,
> > Tony.
>
>
>
>
> Computer A (OK) : Windows 10
>
> echo $VIM gives D:\Logiciels\Vim
> echo $VIMRUNTIME gives D:\Logiciels\Vim\vim81
>
>
> Computer B (KO) : Windows Seven
>
> echo $VIM gives C:\users\foobar\desktop\Vim_x86\Vim_x86
> echo $VIM gives C:\users\foobar\desktop\Vim_x86\Vim_x86\vim81
>
>
> Note : Gvim 8.1.468 build on windows 10 with nmake msvc_build HUGE
>
> What kind of informations are missing because I cannot transmit all kind of infos.
>
> Thank you

Well, please do the following in each of the Vim executables separately:

1. :redir @+
2. :version
3. :redir END

4. paste the result into a reply email but do not send it yet. What
interests me are:
(a) the first few lines, analogous to the following but obviously with
some changes, since you're on Windows and I'm on Linux:

VIM - Vi IMproved 8.1 (2018 May 18, compiled Oct 15 2018 01:25:22)
Included patches: 1-477
Compiled by antoine.mechelynck@gmail.com
Big version with GTK2 GUI. Features included (+) or not (-):

(b) whether the list of features below that includes +syntax or -syntax

After having removed the rest (the "uninteresting" parts), you can send it.

Best regards,
Tony.

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

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

Re: _vimrc loading fails

Le lundi 15 octobre 2018 14:35:43 UTC+2, Christian Brabandt a écrit :
> On Mo, 15 Okt 2018, Ni Va wrote:
>
> > Ok so I don't understand why in one case $vim/vimfiles/colors/nivacolors.vim are loaded on computer A and in other case it is not.
> >
> > This load is called from $MYVIMRC : colors nivacolors.cim
> >
> > The only thing I note is difference directory from which gvim is launched.
> >
> > Computer A (OK) : D:\Softwares\Vim\vim81\gvim.exe
> > Computer B (KO) : ~\Desktop\Vim\vim81\gvim.exe
>
> Please provide a minimum reproducible example. My guess is you have $VIM
> or $VIMRUNTIME or your runtime setting setup differently, but you do not
> provide enough information.
>
> Christian

Computer A (OK) : Windows 10

echo $VIM gives D:\Logiciels\Vim
echo $VIMRUNTIME gives D:\Logiciels\Vim\vim81


Computer B (KO) : Windows Seven

echo $VIM gives C:\users\foobar\desktop\Vim_x86\Vim_x86
echo $VIMRUNTIME gives C:\users\foobar\desktop\Vim_x86\Vim_x86\vim81

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

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

Re: _vimrc loading fails

Le lundi 15 octobre 2018 14:36:43 UTC+2, Tony Mechelynck a écrit :
> On Mon, Oct 15, 2018 at 2:29 PM Ni Va <nivaemail@gmail.com> wrote:
> >
> > Le lundi 15 octobre 2018 14:07:29 UTC+2, Christian Brabandt a écrit :
> > > On Mo, 15 Okt 2018, Ni Va wrote:
> > >
> > > > but I don't see syntax colors is missing out of this was loaded on
> > > > initial computer
> > > > 21: D:/Logiciels/Vim/vim81/syntax/nosyntax.vim
> > >
> > > nosyntax.vim will only be visible, if you issue `:syntax off`.
> > >
> > >
> > > Best,
> > > Christian
> > > --
> > > Der Abenteurer ist unentbehrlich, das wird allerdings erst
> > > erkannt, wenn sich herausstellt, daß er Amerika entdeckt hat.
> > > -- Ludwig Marcuse (Argumente und Rezepte)
> >
> > Ok so I don't understand why in one case $vim/vimfiles/colors/nivacolors.vim are loaded on computer A and in other case it is not.
> >
> > This load is called from $MYVIMRC : colors nivacolors.cim
> >
> > The only thing I note is difference directory from which gvim is launched.
> >
> > Computer A (OK) : D:\Softwares\Vim\vim81\gvim.exe
> > Computer B (KO) : ~\Desktop\Vim\vim81\gvim.exe
>
> Well, unless you unintentionally made a typo, ":colors nivacolors.cim"
> cannot load nivacolors.vim because the name is different.
>
> If it _is_ a typo, the following explanations are possible:
> - the Vim executable which loads neither nosyntax.vim nor
> nivacolors.vim was compiled with -syntax (see the output of :version)
> - or else, it did not execute, respectively, the statements ":syntax
> off" and ":colorscheme nivacolors". The suffix .vim is not necessary
> in the command argument.
>
> Best regards,
> Tony.




Computer A (OK) : Windows 10

echo $VIM gives D:\Logiciels\Vim
echo $VIMRUNTIME gives D:\Logiciels\Vim\vim81


Computer B (KO) : Windows Seven

echo $VIM gives C:\users\foobar\desktop\Vim_x86\Vim_x86
echo $VIM gives C:\users\foobar\desktop\Vim_x86\Vim_x86\vim81


Note : Gvim 8.1.468 build on windows 10 with nmake msvc_build HUGE

What kind of informations are missing because I cannot transmit all kind of infos.

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