aboutsummaryrefslogtreecommitdiffstats
path: root/src/_pygmentize
Commit message (Collapse)AuthorAgeFilesLines
* Update pygmentize completionShohei YOSHIDA2022-11-161-23/+25
|
* fix (( $+functions[_f] )) || _f()Ludovic Jozeau2021-04-081-1/+1
| | | | checked with: "\(\( \$\+functions\[(.*)\] \)\) \|\|\n(?!\1)"
* Move modelines to end of fileAaron Schrab2012-08-231-3/+8
| | | | | | | | | | | | | | | | | | | | | | Having a vim modeline or emacs local variable line somewhere in the middle of the file isn't really helpful. By default, vim will only check the first and last 5 lines of a file for a modeline (assuming the modeline option is enabled). Emacs is even more strict about the type of local variable line that was in use, it will only check the first line of the file or the second line if the first line specifies a script interpreter (which isn't the case here). Move the vim modeline to the end of the file so that it can actually be found by vim but is out of the way for editing. For emacs more work is required, convert that to the more verbose Local Variables syntax which emacs will look for starting 3000 characters from the end of the file. Also there is no zsh mode for emacs (according to zsh-users/zsh-completions#75), use the "Shell-Script" mode instead. This seems to automatically detect that the files are for zsh. I'm not an emacs user, so I haven't tested that portion much. But, this does at least improve the syntax highlighting there.
* [BREAKING CHANGE] Move compdefs to own directory (to ease packaging andJulien Nicoulaud2012-08-011-0/+142
avoid bloating users fpath with unneeded files such as README.md)