Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update from kickstart #1

Merged
merged 39 commits into from
Sep 22, 2023
Merged

Update from kickstart #1

merged 39 commits into from
Sep 22, 2023

Conversation

eratem
Copy link
Owner

@eratem eratem commented Sep 22, 2023

No description provided.

kdheepak and others added 30 commits July 1, 2023 12:40
Hey y'all 👋 

I think there may have been a typo?
Make init.lua copy-paste friendly
Update README.md with a GitHub friendly video example
Allow easier overriding of default filetypes for LSP
Fix bug when server not explicitely defined in configuration but installed
releated -> related
added a URL to the lua-guide
may help others who miss the :help lua-guide
Add a link to the external lua-guide now that :help lua-guide is gone.
Fix typo in original.

Co-authored-by: Luis G Estrades <luisgarciaestrades@gmail.com>
Originally, the keymaps for jumping to next and previous git hunks were
]c and [c. This was changed in #323 (83b65a1) because they overwrote the
built-in vimdiff keymaps.

However, the more traditional solution is to have ]c and [c *extend* the
built-in keymap. This is what fugitive and gitgutter have been doing for
years.

Gitsigns doesn't do this by itself, but it has a recommended keymap
configuration on which the present patch is based:

	https://github.com/lewis6991/gitsigns.nvim#keymaps

The only thing I've added is to have the keymaps work in visual mode as
well, which is the same behavior as the built in vimdiff keymaps.
This parser is actually needed for some *JSX* parsing, and since
typescript and tsx are already getting installed, it makes sense to
also install the javascript parser.
@eratem eratem merged commit 61aab76 into eratem:master Sep 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.