| Age | Commit message (Collapse) | Author | 
|---|
|  | Enable it by default in AODocs paths. | 
|  | When only a single TODO day entry exists in a file, this function would
fail with a "pattern not found" error because the copy pattern expects
at least two entries in a file. Alter the function so that it also works
when only one entry is present in the file. | 
|  | When creating a new TODO entry, always use the current date instead of
incrementing the final 'day' segment with <C-a>. That would cause issues
when incrementing from "07" (results in "010" instead of "08" because it
assumes it's in octal), and "08" (results in "9" without a leading zero,
though I'm not sure why). | 
|  | Make it easier to insert reminder comments to write a JSDoc block. | 
|  | AODocs JSON uses camel case, so this seems like a sensible default. | 
|  | Enable `gf` and related commands to work by setting the proper 'path',
and ensuring the `.js` suffix is used on files. | 
|  | I've been keeping a daily to-do list. Every day, I copy yesterday's
entry and use it as today's with some modifications. Add a mapping to
automate copying the previous day's entry. | 
|  |  | 
|  | The import path was renamed. | 
|  |  | 
|  | A command that opens the Jira ticket ID cWORD in the browser. | 
|  | Add a shortcut to quickly insert the UFO ticket folder path at the
command line to save me the trouble of having to type & complete it
manually. | 
|  |  | 
|  |  | 
|  | Mappings for JavaScript files that add and remove the
`no-debugger: warn` rule to `.eslintrc`. | 
|  | Automatically insert the comment leader to facilitate JSDoc comments. | 
|  |  | 
|  | Mappings to modify the client build cache without leaving Vim. Use
`:silent` combined with `<C-l>` to avoid the hit-enter prompt. | 
|  | Otherwise the function call appears in the command line which is
distracting. | 
|  | Make the commit title length 72 characters plus the length of the ID
followed by a colon and space. | 
|  | Since AODocs commit message style prefers putting Jira IDs at the very
start of commit messages, give myself more room in the title.
Personally I think references should be at the end of a commit message,
so I'm going to take back the extra characters.
TODO: Dynamically calculate the issue ID length and adjust the textwidth
to 72 + that value. | 
|  |  | 
|  | To enable `:GoCallers` by telling it to search in the root package. | 
|  | Speed up tests by disabling the test coverage report generator using the
STIF project's custom environment variable flag. | 
|  | I'm not supposed to write this word, so change it to the code word
automatically if I happen to write it accidentally in a commit message.
Interestingly, the bars (`|`) need to go either right next to the
backslashes (`\`) or right after the right-hand side, as in:
    inoreabbrev <buffer> Ouibus the socle commun|
Otherwise, if a space is before the `|`, that space becomes part of the
abbreviation's right-hand side. | 
|  | I had previously defined this command as 'af83'-project-specific. Now
I've become used to it and want to use it everywhere, so promote it to a
global mapping. | 
|  | Instead of using Spring for RSpec only on the STIF project, use it for
all af83 projects. | 
|  | A project-specific config for the STIF app. Set a custom RSpec command
for rspec.vim that runs the Spring preloader instead of calling RSpec
directly. This allows us to eliminate the slow-as-molasses Rails startup
time when iterating on code with tests. | 
|  | When opening files with Pick and pick.vim, use a project-level
.agignore file to ignore files and directories that shouldn't be
searched when fuzzy-finding.
This allows us to eliminate vendor directories like `node_modules`
from the search path. | 
|  | Create a new project-specific config for AF83. Add a project-specific
mapping to save the current Vim session to a file called 'vimsession'. | 
|  | It finally became tedious to have to manually execute my custom script
that posts a mentor log to The Firehose Project in a new shell. Create a
new command that will run the script directly within Vim so I don't have
to leave the editor.
Actual file paths are stored in `projects/file-paths.vim`.
Need to set the `BUNDLE_GEMFILE` so that the Ruby gems required by the
script get loaded.
The absolute path of the current file gets passed to the script for
posting. | 
|  | Assume all Flashnotes HTML files are 'htmldjango'-type files (as they
typically are since Flashnotes is a Django project). This will preclude
me from having to `set ft=htmldjango` when I want to see syntax colours
for Django template tags. | 
|  | No longer using the Command-T plugin, so this setting is irrelevant now. | 
|  | * Remove project files from the ignore list
* Add project config files as they are now
* Create a new untracked file to keep track of project directory paths
The reason why I never tracked project files in the repo was because I
didn't want my file paths to be shared publicly. But over time I've been
making changes to my `flashnotes.vim` config and wanted to be able to
track those changes, especially the `ctags` ones.
Now, I'm able to track those config files and still hide my file paths
from public view using a set of environment variables defined in
`.vim/projects/file-paths.vim`. |