On 2022-10-06, Arun wrote:
> You could try a hack by calling a function that checks for v:warningmsg and
> reset it, in a "statusline" invoked function. Something like:
>
> ---
> fu! CheckWrap()
> if v:warningmsg =~# "^search hit [BT]"
> "Ring bell
> exe "norm! \"
> endif
Over the years I have grown to hate things that need a lot of configuration
(by me) to work. I think my simplest solution is just to change the
extension I use for PHP classes. One quick shell script to do a
mass-rename, a change to my autoload, and ta-da!
On Thursday, October 6, 2022 at
On Fri, 7 Oct 2022 11:13:27 +0200
Tony Mechelynck wrote:
> There are rare cases (which I won't describe here — if they applied to
> you you would know it, and what to do) where it is worth setting $VIM
> to some nondefault value.
Thanks for the information. The thing is I knew all the things
On Fr, 07 Okt 2022, N V wrote:
> Hi,
>
> I have to compare two files' content with 'windo diffthis'.
> The begin of lines of these files are not significant and have to
> ignore/exclude it from 0 to n column.
>
>
> I would like to know if there is option to Automate this with windo
On Fri, Oct 7, 2022 at 8:38 AM Enan Ajmain <3nan.ajm...@gmail.com> wrote:
>
> On Fri, 7 Oct 2022 08:25:16 +0200
> Christian Brabandt wrote:
>
> > You should not be required to bother :)
>
> I realize that. That's why I didn't know about this variable before. But
> my question is -- sorry for
On Fr, 07 Okt 2022, Enan Ajmain wrote:
> On Fri, 7 Oct 2022 08:25:16 +0200
> Christian Brabandt wrote:
>
> > You should not be required to bother :)
>
> I realize that. That's why I didn't know about this variable before. But
> my question is -- sorry for prying -- is it _intended_ to point
Hi,
I have to compare two files' content with 'windo diffthis'.
The begin of lines of these files are not significant and have to
ignore/exclude it from 0 to n column.
I would like to know if there is option to Automate this with windo
diffthis.
Thank you
Nicolas
--
--
You received
On Fri, 7 Oct 2022 08:25:16 +0200
Christian Brabandt wrote:
> You should not be required to bother :)
I realize that. That's why I didn't know about this variable before. But
my question is -- sorry for prying -- is it _intended_ to point to
installation directory, i.e., the system's vim files?
On Do, 06 Okt 2022, Barry Gold wrote:
> Following your suggestions, I think that this behavior is caused by the
> extension .cl
> I'm using that for PHP classes, but it looks like my current version of vim
> thinks that .cl is for "LISP" files.
>
> Maybe I can override that somehow?
You may
Following your suggestions, I think that this behavior is caused by the
extension .cl
I'm using that for PHP classes, but it looks like my current version of vim
thinks that .cl is for "LISP" files.
Maybe I can override that somehow?
On Thursday, October 6, 2022 at 12:13:57 PM UTC-7 Gary
On Fr, 07 Okt 2022, Enan Ajmain wrote:
> Where should `:h $VIM` point toward? Where vim is installed or where vim
> configurations is situated? By default it points to where vim is
> installed. But the help doc says:
>
> > The environment variable "$VIM" is used to locate various user files
>
11 matches
Mail list logo
