aboutsummaryrefslogtreecommitdiff
path: root/Makefile
Commit message (Collapse)AuthorAgeFilesLines
* Don't create ~/.vim/configTom Ryder2018-06-221-1/+0
|
* Add -e flag to Vim :helptags buildTom Ryder2018-06-221-1/+1
| | | | Prevents warnings on stderr about output not being to a terminal.
* Use simpler Vim :helptags build commandTom Ryder2018-06-211-2/+1
|
* Use autoload function for temp-makeprg :lmakeTom Ryder2018-06-171-0/+5
|
* Rename terminfo files to *.ti extensionTom Ryder2018-06-111-1/+1
|
* Apply t_cm hack to Makefile Vim invocationTom Ryder2018-06-111-1/+2
| | | | | This prevents it from trying to move output to the bottom of the screen during the make(1) run.
* Replace mail_mutt.vim with mim(1df)Tom Ryder2018-06-071-0/+4
| | | | Way better, and more generally useful.
* Add custom scripts.vimTom Ryder2018-06-061-1/+2
| | | | Including adding sed support
* Consolidate .vimrc and .vim/filetype.vimTom Ryder2018-06-061-6/+3
| | | | And add .vim/script.vim, to be composed in the next commit
* Correct install-vim-ftplugin targetTom Ryder2018-06-051-3/+3
|
* Revert "Merge bundle install into one command"Tom Ryder2018-06-051-2/+2
| | | | | | | This reverts commit 39627969dac81be22aef4c0a50548f9e31ed19f9. I remember now why this is required. Otherwise it copies in README.markdown and VERSION etc from the plugin roots.
* Merge bundle install into one commandTom Ryder2018-06-051-2/+2
|
* Restore ftplugin extras to vim/after dirTom Ryder2018-06-051-7/+2
| | | | | This reverts commit a14bc50. Changed my mind; decided it's tidier this way.
* Move Markdown and PHP ftplugins from after dirTom Ryder2018-06-041-2/+7
| | | | | | | Because we use our own private copies of the primary filetype plugins, they'll get loaded in the correct order from here. Also adjust Makefile to accommodate the extra level.
* Move markdown_autoformat.vim funcs back to localTom Ryder2018-06-041-10/+0
| | | | No advantage to making them autoload
* Refactor suspend_autoformat.vim, add autoloadTom Ryder2018-06-041-0/+10
| | | | | | | | * Add a function to suspend autoformatting for the duration of pasting lines. * Factor the ftplugin's functions out to be autoloaded; this requires Vim >=7.0, but it already needed that. * Add Makefile infrastructure for new autoload directories/files.
* Implement personal filetype.vimTom Ryder2018-06-031-0/+1
| | | | | | | | | | | | | | | | | This implements only the syntax highlighting for file types I regularly use and care about, implemented in the way I want them to work, with files named per type in ftdetect/*.vim. I have chosen only file types with which I regularly deal and for which syntax highlighting and filetype/indent plugins are actually useful. Most other files, e.g. system config files I edit infrequently and only with sudoedit(8), don't really benefit from that. Much of this is just copied from the distribution filetype.vim file, but some of it I do specifically in a way I want, such as the shell decision logic. We'll see how well this works.
* Correct name of Makefile targetTom Ryder2018-06-031-1/+1
|
* Refactor Vim distribution plugin/macro handlingTom Ryder2018-06-021-0/+11
| | | | | | Intelligently choose how to load matchit.vim, and clean up the short-circuit variables for the unwanted distribution plugins in an "after" plugin script.
* Rebuild help tags after installing bundleTom Ryder2018-06-021-0/+1
|
* Merge auto_*dir.vim plugins into one, spun outTom Ryder2018-05-311-36/+2
| | | | Functionality merged into new plugin auto_cache_dir.vim.
* Spin off command_typos Vim pluginTom Ryder2018-05-311-9/+2
| | | | Renamed as uncap_ex.vim.
* Spin off big_file_options Vim pluginTom Ryder2018-05-311-7/+0
|
* Spin off strip_trailing_whitespace Vim pluginTom Ryder2018-05-311-8/+1
|
* Spin off mail_mutt Vim pluginTom Ryder2018-05-311-7/+0
|
* Spin off copy_linebreak Vim pluginTom Ryder2018-05-311-7/+0
|
* Junk detect_background.vim and thereby autoloadTom Ryder2018-05-311-12/+0
| | | | | | | | | | | It's too complicated and confusing, and doesn't do enough to justify wrecking Vim's own logic for doing this sort of thing. Better to just say `:set background=dark` and be done with it. This is the only one of my inline plugins with an `autoload` file, so we can get rid of that, too. Not worth packaging/publishing to www.vim.org.
* Spin off toggle_option_flag Vim pluginTom Ryder2018-05-301-9/+2
|
* Spin off fixed_join Vim pluginTom Ryder2018-05-301-7/+0
|
* Spin off insert_suspend_hlsearch Vim pluginTom Ryder2018-05-301-7/+0
|
* Add Makefile tweak for Neovim installationTom Ryder2018-02-161-26/+30
| | | | | | | A cursory test suggests that all of this configuration works well on Neovim, or at least the bad stuff is gracefully ignored. Allow changing the destination path for ~/.vimrc and ~/.vim/config to suit Neovim's paths, including some instructions and some bloviating in README.md.
* Add missing options terminator to MakefileTom Ryder2018-02-071-1/+1
|
* Replace ftplugin/php.vim with custom versionTom Ryder2018-02-011-0/+6
| | | | | | | Per the comment in the new file, this is to avoid loading in HTML ftplugins as well, a curiosity of the stock ftplugin/php.vim file that's probably a well-intentioned way of accommodating templated files with a mix of PHP and HTML in them.
* Exclude root-level files from Vim bundlesTom Ryder2018-01-231-3/+3
| | | | | | Create the plugin directory hierarchy first, and then copy the files in as long as they're at least one file deep. This prevents files like README.markdown landing in ~/.vim.
* Restore install-vim-autoload targetTom Ryder2018-01-231-0/+5
| | | | It was mistakenly removed in 3e2740f for v0.26.0.
* Remove Pathogen from Vim setupTom Ryder2018-01-231-7/+5
| | | | | | | Given that all of this is installed rather than symbolically linked, there's not really any harm following the old mixed ~/.vim layout for plugins. It's one less dependency and it makes the setup quite a bit less complicated.
* Allow specifying GnuPG --keyid-format at buildTom Ryder2017-12-291-0/+2
| | | | | Old versions of gpg(1) don't support "none" as a --keyid-format; allow specifying it as a Makefile variable KEYID_FORMAT.
* Use only fingerprints for GnuPG keysTom Ryder2017-12-291-1/+1
| | | | The manual page for gpg(1) says this is the safest way to do it.
* Switch from newsbeuter to newsboatTom Ryder2017-12-281-4/+4
| | | | | | Newsbeuter is no longer maintained: <https://github.com/akrennmair/newsbeuter/commit/7c981f460d6c8c3690f140cbb279c277dc8f55fe>
* Add install target for vim-vintTom Ryder2017-12-081-0/+4
|
* Use :compiler scripts for makeprg setupTom Ryder2017-11-191-0/+6
| | | | | | | | | | | | I didn't know about :compiler until now. From :help write-compiler-plugin: > A compiler plugin sets options for use with a specific compiler. The > user can load it with the |:compiler| command. The main use is to set > the 'errorformat' and 'makeprg' options. Vim even has "perl" and "tidy" compilers already that seem to work really well. I'll just add in my own and install them.
* Add Makefile targets for Vim plugin distsTom Ryder2017-11-141-2/+89
| | | | | | | | This is just an experiment to see how well an automated process can make independently distributable versioned tarballs of my Vim plugins. These are not part of the default `all` or `install` target. They create distribution vim-$name-$ver.tar.gz files in vim/dist.
* Move lots of local Vim config into vim/afterTom Ryder2017-11-121-12/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a relatively drastic change that should have been done progressively, but I got carried away in ripping everything out and putting it back in again. Reading the documentation for writing a Vim script (:help usr_41.txt), I am convinced that all of the content that was in the vim/ftplugin directory and some of the vim/indent directory actually belonged in vim/after/ftplugin and vim/after/indent respectively. This is because the section on filetypes makes the distinction between replacing the core filetype or indent plugins and merely adding to or editing them after the fact; from :help ftplugin: > If you do want to use the default plugin, but overrule one of the > settings, you can write the different setting in a script: > > setlocal textwidth=70 > > Now write this in the "after" directory, so that it gets sourced after > the distributed "vim.vim" ftplugin after-directory. For Unix this > would be "~/.vim/after/ftplugin/vim.vim". Note that the default > plugin will have set "b:did_ftplugin", but it is ignored here. Therefore, I have deleted the user_indent.vim and user_ftplugin.vim plugins and their documentation that I wrote, and their ftplugin.vim and indent.vim shims in ~/.vim, in an attempt to make these plugins elegantly undo-ready, and instead embraced the way the documentation and $VIMRUNTIME structure seems to suggest. I broke the ftplugin files up by function and put them under subdirectories of vim/after named by filetype, as the 'runtimepath' layout permits. In doing so, I also carefully applied the documentation's advice: * Short-circuiting repeated loads * Checking for existing mappings using the <Plug> prefix approach * Avoiding repeated function declarations overwriting each other * Guarding against 'cpotions' mangling things (by simply short-circuiting if 'compatible' is set). I've made the b:undo_ftplugin and b:undo_indent commands less forgiving, and append commands to it inline with the initial establishment of the setup they're reversing, including checking that the b:undo_* variable actually exists in the first place. For the indentation scripts, however, three of the four files originally in vim/indent actually do belong there: 1. csv.vim, because it doesn't have an indent file in the core. 2. tsv.vim, because it doesn't have an indent file in the core. 3. php.vim, because it does what ftplugins are allowed to do in preventing the core indent rules from running at all. The indent/vim.vim rules, however, have been moved to after/indent/vim.vim, because the tweaks it makes for two-space indentation are designed to supplement the core indent rules, not replace them. Finally, I've adjusted Makefile targets accordingly for the above, given the vim/ftplugin directory is now empty and there are three new directories in vim/after to install. We wrap these under a single `install-vim-after` parent target for convenience. The `install-vim-after-ftplugin` target accommodates the additional level of filetype directories beneath it.
* Add user_ftplugin.vim and user_indent.vim pluginsTom Ryder2017-11-071-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 09b83b6 and replaces it with a working version. Because of the order in which the autocmd hooks run, the attempted method of adding unloading instructions for my custom ftplugin and indent rules to the b:undo_ftplugin and b:undo_indent doesn't actually work. This is because the custom rules for both groups from ~/.vim are sourced *first*, before their core versions, so the changes the custom rules made to b:undo_ftplugin and b:undo_indent are simply clobbered by the core version when it loads itself. Therefore we need to arrange for two things: 1. A custom variable needs to be checked and executed when the filetype changes to revert the changes for the custom ftplugin or indent rules. 2. That execution needs to take place *first* when the filetype changes. I wrote two simple plugins with very similar code that are designed to run as a user's custom ftplugin.vim and indent.vim implementations, running before their brethren in the Vim core, and setting up an autocmd hook to :execute b:undo_user_ftplugin and b:undo_user_indent plugin respectively. This seemed to work well, so I've implemented it. It involves adding a shim to ~/.vim/indent.vim and ~/.vim/ftplugin.vim to "preload" the plugin when the `filetype indent plugin on` call is made. I've added that to the relevant Makefile targets.
* Merge branch 'feature/spin-vim-plug' into developTom Ryder2017-11-041-0/+6
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * feature/spin-vim-plug: Rename toggle plugin again, use commands not funcs Add short documentation for new custom plugins Use same comment boilerplate for custom plugins Check 'eval' feature for loading command_typos.vim Wrap detect_background.vim func call in 'silent!' Rename and refactor option toggle plugin Don't suggest mappings in Vim plugin comments Move Vim background detection logic into plugin Specify an install-vim-autoload target Spin 'fo' toggle out into new flag toggler plugin Spin copyable linebreak config into new plugin Spin stable join config out into new plugin Use <Plug> prefix, make space strip configurable Rename a misnamed variable in big_file.vim Rename bigfile plugin to big_file Move trailing space strip config into plugin Separate command typos config to plugin
| * Specify an install-vim-autoload targetTom Ryder2017-11-041-0/+6
| | | | | | | | | | We'll use this for defining Vim functions that should be dynamically loaded when required, rather like how pathogen.vim does it.
* | Add ~/.tidyrc and accompanying Makefile targetTom Ryder2017-11-041-0/+5
|/ | | | | | | | | This target also installs a short shell script in ~/.profile.d to set and export the HTML_TIDY environment variable that defines the path to the configuration file. tidy(1) seems to need this to be explicitly set with a default build, as far as I can tell. This pairs nicely with the settings in vim/ftplugin/html.vim.
* Move Vim big file options config into pluginTom Ryder2017-11-021-1/+11
| | | | | | | | | | | Created targets install-vim-doc and install-vim-plugin with accompanying subdirectories of "vim". Added a very short summary of what the plugin does to bigfile.txt. I intend to spin off at least a couple of the blocks of my Vim configuration that are starting to coalesce into distinct plugins unto themselves, and will place the files in these directories.
* Add dfv(1df) version-printing toolTom Ryder2017-11-011-0/+4
| | | | | | | | | | This is mostly just for fun, but could be handy later on when I'm playing with distributed or automated deployments of tagged and verified releases. Like a few of the other shell scripts, this is built by abusing my mi5(1df) wrapper to get static details baked into the shell script that are only known at runtime.
* Check and lint URxvt Perls correctlyTom Ryder2017-10-311-1/+1
| | | | | | Require that the URxvt Perls are built correctly. There's only one at the moment, so I'll make that the single prerequisite for the `check-urxvt` target.
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-19 04:44:15 +0000