On Tuesday, June 6, 2023 at 3:31:29 AM UTC+10 Bram Moolenaar wrote:
I have see some DB errors the last few days. Usually the problem goes
away a bit later, e.g. after an hour. I have no clue what might cause this.
Are you able to ask for help at the hosting service? The problem would
probably
Le 06/06/2023 à 02:58, Gary Johnson a écrit :
if line("$") == 1 && empty(getline(1))
that's nice
if last line is the first one, and first line is empty
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
On 2023-06-06, NBaH wrote:
> Le 05/06/2023 à 17:50, Gary Johnson a écrit :
>
> no file name argument has been given to that :new command, so the
> BufNewFile
> autocommand is not triggered.
>
> this is the most important part of the reason why it doesn't work. :)
>
> thank you for corre
Le 05/06/2023 à 17:50, Gary Johnson a écrit :
no file name argument has been given to that :new command, so the BufNewFile
autocommand is not triggered.
this is the most important part of the reason why it doesn't work. :)
thank you for correcting autocommand.
do you have any (simple) idea a
Christian wrote:
> On Sa, 03 Jun 2023, Lifepillar wrote:
>
> > On 2023-06-02, Bram Moolenaar wrote:
> >
> > > You could try using another browser.
> >
> > I have tried with Safari, Brave, and LibreWolf (~Firefox) on macOS to no
> > avail. I have taken care to disable ad blockers and, afaics,
On 2023-06-05, NBaH wrote:
> hello,
>
> I'm trying to add skeleton to new files having a filetype (eg python)
>
> here's what I've tried :
>
> autocmd BufNewFile if &filetype == "python" 0r ~/.vim/python.skel | normal G |
> let IndentStyle = "python" | endif
One problem with the above is that
hello,
I'm trying to add skeleton to new files having a filetype (eg python)
here's what I've tried :
autocmd BufNewFile if &filetype == "python" 0r ~/.vim/python.skel |
normal G | let IndentStyle = "python" | endif
with no luck when I open a new file like this :
: bel new | set filetype=p
On Sa, 03 Jun 2023, Lifepillar wrote:
> On 2023-06-02, Bram Moolenaar wrote:
>
> > You could try using another browser.
>
> I have tried with Safari, Brave, and LibreWolf (~Firefox) on macOS to no
> avail. I have taken care to disable ad blockers and, afaics, only
> cross-site cookies are blo