nikhgupta / dotfiles Goto Github PK

VIM shows wrong symbols in place of unicode chars, e.g. in whitespace indicator of airline, or for list characters.

Due to the recent change to airline's appearance, readonly indicator in Base16Eighties theme is hard to see. Fix that.

Currently, bufferline shows tabs for active windows with a background matching the background of the buffer, which makes it hard to figure out the active buffer. Also, for inactive buffers, bufferline tabs does not distinguish that buffer in the bufferline.

When VIM opens, startup screen powered by Startify doesn't open the file specified by s key, and instead, simply modifies the buffer, itself.

In order to restore cursor position after certain commands, VIMRC should use a common marker (lets say, 'z'). This is to avoid the issue when a marker is overwritten by a VIMRC command.

• Do not use cron.
• Make sure that the check does not affect prompt rendering time.

ZSH configuration is old, and not organized in a neat manner. Review the configuration, and reorganize it. Make sure that ~/.zprofile has only the essential elements that are needed by vim.

When adding hunks via GitGutter, sometimes, it adds hunks to staging incorrectly. Investigate or switch to another workflow (preferred, fugitive's hunk additions)

Add more programs (for various languages) for the vim's makeprg and keywordprg options. Also, add a key mapping to run :make via the F5 command. makeprg should handle the most used tasks, e.g. previewing the markdown files, for a particular language/filetype.

Current configuration of Airline themes with the colorschemes that we choose, makes it impossible to distinguish between two panes in the same VIM window. Status line on one split matches too much with the background.

VIM must display whether it is running in Terminal or GUI mode in the Airline, since the terminal and GUI versions share similar displays in the night mode. A simple message stating whether VIM is running in GUI mode or Terminal mode will help distinguish between the two, if need be.

-- issue created via the command line gem: ghi

Emacs configs were removed from the repository via commit 3c2eba7. Add the configuration back to the repository as a submodule (preferably, not).

VIM mappings should be consistent and grouped together based on their function, e.g. all keys related to editing/opening a file can be prefixed with <leader>e (e.g. opening in a split to <leader>es, etc.), and all keys that toggle a setting can be prefixed with <leader>t, etc.

• Host completion from ~/.ssh/config is not present.

• Invalid hostname entries (for other users)

  ~/Code/__dotfiles [ master: ✔ ] 25m ± ➲ ssh                       🕥 [22:28:27] 🔋 [53%]
  Guest                family               MacBookAir         github.com
  root                 heroku.com           nikhgupta          server.wickeddevelopers.com
  ....
  

The current statusline is a very neat implementation. However, since the interface is expected to be minimalistic distraction free version, the status line can be further reduced to only show the most essential information, such as the file modification status, and simple ruler. Currently, statusline displays the filetype, which is not optimal and can be removed from the statusline, etc.

The current statusline is a very neat implementation. However, since the interface is expected to be minimalistic distraction free version, the status line can be further reduced to only show the most essential information, such as the file modification status, and simple ruler. Currently, statusline displays the filetype, which is not optimal and can be removed from the statusline, etc.

Currently, awesome-text and focus colorschemes are present in colors/ directory, which should be extracted as VIM bundles.

Here is the bug:

In order to make ghi output colorful, we must add the following configuration to git globally. Set that up using the dotfiles.

$ git config --global ghi.highlight.style colorful

VIM already supports profiling via the :profile feature. Use it in a custom function within VIM to easily profile VIM's startup and actions.

Review plugins loaded by OhMyZSH, and only load plugins that are necessary. Also, extract custom aliases and functions as OMZ! plugins (and, send PR), if possible.

Bufferline/Airline reports multiple buffers as modified for some reason. (maybe a bug?)

Normal (GUI):

Within Terminal:

Command completion via ^X^L includes color codes, which should be stripped from them.

PIV plugin for PHP adds PHP docs to the VIM help text, which clutters vim help and often, :help <something> jumps to these docs. So, remove them, and add them via keywordprg.