| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rather than setting g:is_posix and working around core syntax/sh.vim's
ideas about Korn and POSIX shells, forego sh.vim's efforts to guess what
shell the system /bin/sh is entirely. It's irrelevant to me anyway,
since I'll often be writing shell scripts to run on an entirely
different system.
Instead, if we have a #!/bin/sh shebang reflected in the b:is_sh
variable set by core filetype.vim, and we don't have any other
buffer-level indication of what shell this is, assume it's POSIX,
because I very rarely write Bourne.
Then, after the syntax file is loaded, clear away all but one of the
resulting b:is_* variables.
I have a feeling this is going to end with me re-implementing this
syntax file, possibly as separate sh.vim, bash.vim, and ksh.vim files.
|
| |
|
|
|
|
| |
This was unintentionally committed in e36efd4. The correct name of the
variable is b:is_ksh. b:is_kornshell_proper was a rejected first
revision of the name.
|
| |
|
|
| |
No functional effect.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Move the rule setting the custom b:is_ksh variable used for this
workaround (established in 52615f6) into an ftplugin file, rather than
into ftdetect; the latter seems a much more appropriate place since by
this point we've definitely decided the file type is "sh".
From the revised comment in this changeset:
>Setting g:is_posix above also prompts Vim's core syntax/sh.vim script
>to set g:is_kornshell and thereby b:is_kornshell to the same value as
>g:is_posix.
>
>That's very confusing, so before it happens we'll copy b:is_kornshell's
>value as determined by filetype.vim and ~/.vim/ftdetect/sh.vim into a
>custom variable b:is_ksh, before its meaning gets confused.
>
>b:is_ksh as a name is more inline with b:is_bash and b:is_sh, anyway,
>so we'll just treat b:is_kornshell like it's both misnamed and broken.
>
>We can then switch on our custom variable in ~/.vim/after/syntax/sh.vim
>to apply settings that actually *are* unique to Korn shell and its
>derivatives.
|
| |
|
|
|
| |
This and the other files in the now-removed vim/after/ftdetect directory
were moved to vim/ftdetect in f8af47b.
|
| |
|
|
|
|
|
|
|
| |
None of the settings in here need to be run after the core configuration
files are loaded, so I'll put them in a slightly more accessible or
logical place.
This adds a new target `install-vim-ftplugin`, and makes that a
prerequisite of the `install-vim` target.
|
| |
|
|
|
|
| |
Setting these options globally is probably what's been causing me to get
so confused by my indentation level changing to zero when editing other
files in the same Vim instance as a VimL file. This should correct it.
|
| |
|
|
|
|
|
|
|
| |
This method short-circuits the unwanted PHP expression-based indenting
configuration completely, rather than running it all and then undoing it
after the fact.
This involves creating a new direction ~/.vim/indent, and a Makefile
target install-vim-indent to copy everything into it.
|
| |
|
|
|
|
|
|
|
| |
There's no particular reason to run these file detection rules after the
plugins have run, so we'll put them in a more expected directory.
I've created a new Makefile target to install this,
`install-vim-ftdetect`, which is included as a prerequisite of the
`install-vim` target.
|
| |
|
|
|
|
|
|
|
|
| |
There's no particular need to set these options after netrw has loaded;
they can be set before it's loaded, and the plugin will still observe
them.
This empties the vim/after/plugin directory. It doesn't need to be
removed from the Makefile as there are no references to it; it was
installed by a glob cp(1).
|
| |
|
|
|
| |
Remove some person and system specific stuff, including my signature;
nothing complex about that, after all.
|
| | |
|
| | |
|
| |
|
|
| |
As part of a foray into more active use of ksh and derivatives.
|
| | |
|
| | |
|
| |
|
|
| |
So that it actually runs at the right time ...
|
| | |
|
| |
|
|
|
| |
Until I can figure out what's wrong with this syntax, or why the syntax
highlighter thinks it's an error
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
There's been a lot of work done to sh.vim since these customisations
were made, and I can't remember why I made some of them. I'll work
without them for a while and reapply any of them if needed.
|
| | |
|
| |
|
|
| |
This probably contains a few mistakes
|
| | |
|
| |
|
|
| |
Turned out to be a bad idea.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
It keeps doing things I don't expect, and the code looks hard to change.
autoindent should do the job. I might have a go at writing my own later
to handle obvious cases like an opening brace or case statement on the
previous line.
|
| |
|
|
| |
Annoys me more often than it helps
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
