Tony Mechelynck said on Wed, 14 Jun 2023 10:03:44 +0200
>
>I think Tim's answer is right. Now for a bit of explanation, as found
>in the help for 'runtimepath' (in my gvim and with my 'guifont' this
>uses about two screenfuls of help text):
Thanks Tony! I wish somebody had told me about :h
Bram Moolenaar said on Wed, 14 Jun 2023 11:24:47 +0100
>Suggestion: Use "setlocal" instead of "set" to avoid affecting other
>files. You only want to apply these options locally.
Done! Thanks Bram.
SteveT
Steve Litt
Autumn 2022 featured book: Thriving in Tough Times
On 2023-06-14 16:44, Steve Litt wrote:
> >??? $VIMRUNTIME/ and its subdirectories contain scripts coming from the
[snip
> Oh oh. See following command line session:
>
> ==
> [slitt@mydesk .vim]$ echo $VIMRUNTIME
>
> [slitt@mydesk .vim]$ echo $VIM
>
Tim Chase said on Tue, 13 Jun 2023 20:37:10 -0500
>On 2023-06-13 21:18, Steve Litt wrote:
>> Using grep, I found there are no files whose names contain the string
>> "pascal" in any case in the ~/.vim directory (I'm using Void Linux).
>>
>
>I suspect your frustration is being caused by
On Wed, Jun 14, 2023 at 3:18 AM Steve Litt wrote:
>
> Vim handles formatting for most computer languages wonderfully. But not
> Pascal. My writing of Pascal programs is slowed horribly by Vim's
> bizarre formatting.
>
> Using grep, I found there are no files whose names contain the string
>
> Tim Chase said on Tue, 13 Jun 2023 20:37:10 -0500
>
> >On 2023-06-13 21:18, Steve Litt wrote:
> >> Using grep, I found there are no files whose names contain the string
> >> "pascal" in any case in the ~/.vim directory (I'm using Void Linux).
> >>
> >
> >I suspect your frustration is being
