Seems I forgot some details:
- The behavior described is an OS-independent regression from version
9.1.???
- I'm using the latest version of vim/gvim 9.1.1582.
- The behavior is perceived only with help buffers (i.e. ft=help).
- Setting ft=text and modifiable doesn't remedy the problem.
On Tuesd
After
gvim -i NONE -N -u NONE --noplugin -U NONE -c "h number"
I can no longer move away from the buffer with e.g. :bN or :bn.
Doing so returns error E85.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For mor
bandt wrote:
>
> On Fr, 05 Jan 2024, 'hebar...@googlemail.com' via vim_dev wrote:
>
> > Specifying "wildignore" patterns in the initialization file prevent a
> file
> > matched by one of the patterns to be loaded when GVim is called with the
>
Specifying "wildignore" patterns in the initialization file prevent a file
matched by one of the patterns to be loaded when GVim is called with the
"--remote-silent" flag.
GVim: 9.1 [1-4]
OS: Windows 10
default.vim
set wildignore=*.a
Co
ight on this?
>
> Info: I'm using the 9.0.242
>
> On Tuesday, August 23, 2022 at 6:25:51 PM UTC+2 yega...@gmail.com wrote:
>
>> Hi,
>>
>> You need to prefix the command with ":vim9cmd"
>>
>> - Yegappan
>>
>> On Tue, Aug 23, 2022
Tuesday, August 23, 2022 at 6:25:51 PM UTC+2 yegapp...@gmail.com wrote:
> Hi,
>
> You need to prefix the command with ":vim9cmd"
>
> - Yegappan
>
> On Tue, Aug 23, 2022 at 9:18 AM 'hebar...@googlemail.com' via vim_dev
> wrote:
> >
> > The be
The below script, when executed with "so %", gives error "E117: unknown
function III".
Is there any way to remedy this (given that the same script, running as
"vim9script" runs w/o error)?
As a side note: the functions below are part of my .vimrc; so I'm having
trouble flagging the whole file as
Ok, so it's unlike in C...
Thx for the clarification!
On Sunday, August 21, 2022 at 4:31:48 PM UTC+2 Bram Moolenaar wrote:
>
> > The following code gives error E1012:
> >
> > vim9script
> > var str = bufnr()
> >
> > Is this supposed to work? The docs (vim9.txt, line 1497ll) state:
> >
> > >>>
The following code gives error E1012:
vim9script
var str = bufnr()
Is this supposed to work? The docs (vim9.txt, line 1497ll) state:
>>> The syntax of a type cast is: "<" {type} ">".
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text
After adding a line with "o" (on an indented line with "autoindent" on)
then (while being in INSERT mode) using "^O" to enter a NORMAL mode command
the cursor jumps back to the beginning of the line (erasing the indent),
and will not return to the starting position after immediately pressing ESC
Depending on whether I use "--remote-silent" (or not), vim can open a file
(or not)...
k:\bin\vim\gvim.exe 'yyy\(ллл).txt'
opens yyy\(ллл).txt w/o error.
k:\bin\vim\gvim.exe* --remote-silent* 'yyy\(ллл).txt'
doesn't open the file (whose name contains non-ANSI characters) but returns
error (in
Thanks for looking into this!
Although this is a work-around, it helps...
On Tuesday, December 29, 2020 at 5:26:36 PM UTC+1 cbl...@256bit.org wrote:
>
> On Di, 29 Dez 2020, Christian Brabandt wrote:
>
> >
> > On Di, 29 Dez 2020, 'hebar...@googlemail.com' via vim
[[:upper:]]*\{2,}* is not correctly applied, resulting in not finding what
is searched for...
Please refer to the below text fragment:
--
" Version: GVim 8.2.2148
" OS: Windows 7, 64-bit
" Test pattern
05. ПЕСНЯ О ГЕРОЯ
13 matches
Mail list logo
