runtime(progress): Use setlocal for expandtab
Commit:
https://github.com/vim/vim/commit/342ae5f8aa612179f9390c21a8129a393a995b1a
Author: Daniel Smith <
dan...@rdnlsmith.com>
Date: Thu Feb 19 16:44:45 2026 +0000
runtime(progress): Use setlocal for expandtab
The Progress syntax file gained `set expandtab` in 4c3f536f4 (updated
for version 7.0d01, 2006-04-11). The Progress language itself doesn't
distinguish between tabs and spaces for indentation, so this seems like
something that should be left to user preference; but the setting is
accompanied by the comment "The Progress editor doesn't cope with tabs
very well", so there may be reason to keep it.
However, using `set` means that any new buffers created after editing a
Progress file will also have `expandtab` turned on, which is likely
contrary to a user's expectations. We should use `setlocal` instead to
avoid this.
closes: #19458
Signed-off-by: Daniel Smith <
dan...@rdnlsmith.com>
Signed-off-by: Christian Brabandt <
c...@256bit.org>
diff --git a/runtime/syntax/progress.vim b/runtime/syntax/progress.vim
index 4b8f61287..deb8199b3 100644
--- a/runtime/syntax/progress.vim
+++ b/runtime/syntax/progress.vim
@@ -9,7 +9,7 @@
" Chris Ruprecht <
chris...@ruprecht.org>
" Mikhail Kuperblum <
mikhai...@whasup.com>
" John Florian <
jflori...@voyager.net>
-" Last Change: Jul 23 2024
+" Last Change: Feb 18 2026
" quit when a syntax file was already loaded
if exists("b:current_syntax")
@@ -22,7 +22,7 @@ set cpo&vim
setlocal iskeyword=@,48-57,_,-,!,#,$,%
" The Progress editor doesn't cope with tabs very well.
-set expandtab
+setlocal expandtab
syn case ignore