| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |
|
|
| |
git-log-pretty-since.sh: fix bug
|
| | |
|
| |
|
| |
[ci skip]
|
| |
|
|
|
|
|
|
|
| |
Without this the "cd scripts/.." might change to another dir (since
CDPATH is looked at before a local path), and then NEOVIM_SOURCE_DIR
might end up being "/somewhere/else\n/somewhere/else" (since the "cd"
prints the dir already in that case).
Closes https://github.com/neovim/neovim/pull/5213.
|
| |\
| |
| | |
option: Do not expand options, obtained from XDG vars
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It is a wrong thing to do, this makes valid variable values be treated
incorrectly: in
XDG_DATA_HOME='/home/$foo/.local/share'
`$foo` should be treated literally and not expanded to `foo` environment
variable value.
Also makes option_expand not try to expand too long strings even if these too
long strings are default values. Previously it thought that default values
should always be expanded. Also does not try to expand NULL should it be the
default value just in case.
Fixes #4961
|
| | | |
|
| | |
| |
| |
| | |
Fixes https://github.com/neovim/neovim/issues/5060.
|
| |/ |
|
| |
|
| |
goto statement was only introduced in Lua 5.2.
|
| |
|
| |
vimpatch.sh: fix awk expr
|
| |
|
|
|
|
|
| |
If a user has multiple remotes set for neovim/neovim, then
find_get_remote was returning 'remote1\nremote2\n', which breaks
anything trying to use it. Since we're just using this remote to fetch
from, any one will do.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
check_executable now just wraps the "exists && executable" check. This
will be needed to allow fallbacks for commands.
|
| |
|
|
|
|
|
|
|
| |
It's acceptable for “git describe --tags --exact-match …” to fail, since
all runtime updates commits are untagged. All that matters is that we
get a tag when one exists.
Therefore, ignore the failure status of the git describe call, relying
on the captured output instead.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are a total of 5 shell scripts in the Neovim source tree.
All but runtime\macros\less.sh had warnings/errors when run through
Shellcheck (http://www.shellcheck.net/).
This commit fixes all warnings/errors and also changes the shebang to
"#!/bin/sh" when possible (this was not possible for vim-patch.sh
because it uses many bashisms).
The shellcheck errors that were fixed are:
SC2068: Double quote array expansions to avoid re-splitting elements.
SC2086: Double quote to prevent globbing and word splitting.
SC2124: Assigning an array to a string! Assign as array, or use *
instead of @ to concatenate
SC2155: Declare and assign separately to avoid masking return values.
|
| | |
|
| | |
|
| |
|
|
|
| |
Rather than assume the user named their neovim/neovim remote "upstream",
parse the information from "git remote -v".
|
| |
|
|
|
| |
The new version of the lua client uses libmpack as a backend, and some test
scripts had to be updated to reflect that.
|
| |
|
|
|
|
|
| |
Make get_vim_sources fetch the whole repository (it's not THAT big) so we can
pick up all the patches. The regexp didn't pick up the NA patches if there was a
comma after NA, so I extended it (I allowed arbitray things after NA, so maybe
someone can write a comment or so, should not lead to confusion).
|
| |
|
|
| |
This was not the correct way to fix the issue.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Calling "vim-patch.sh -p" on a checked-out branch already created with
"-p" will re-use the branch and append commits.
* Fetch upstream/master before checking out branch on first call of "-p".
* Reverted creation of commit in submit step ("-s") to previous behavior:
Create an empty commit with correct commit message when "-p" is called.
* Submitting a pull request with "-s" will create a correct pull request
message even if multiple patches have been ported in one single branch
with "-p".
|
| |
|
|
|
|
| |
When calling "vim-patch.sh -s" on a checked-out branch created with
"vim-patch.sh -p", create commit from staged changes, push to origin,
create pull request (using hub), and clean up patch files.
|
| | |
|
| |
|
|
|
|
| |
* Support pull requests with multiple commits.
* Offer to clean up files after review.
* Always use full commit hash in assign_commit_details().
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
This will avoid confusion if additional `it()` blocks are added.
(`setup()` only runs once per `describe()` block, whereas `before_each()`
runs before each `it()`).
|
| | | |
|
| |/
|
|
|
|
|
| |
Problem: For some options two consecutive commas are OK. (Nikolay Pavlov)
Solution: Add the P_ONECOMMA flag.
https://github.com/vim/vim/commit/0e7c4b99c608d22fd1b8526e700420b248319b1f
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Any patch may contain mixed encodings, so we must process them as byte
arrays. E.g. with stock `sed` on OS X patch
8a94d873aa8c753a8522ea86a049bdf2abd0c507 causes this error:
sed: RE error: illegal byte sequence
To avoid that, set LC_ALL=C.
Also remove redundant *.patch creation from review_pr().
|
| |
|
|
| |
Sort non-tagged patches in descending order, like tagged patches.
|
| |
|
|
| |
The examples were missing the required -p flag.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
What works:
1. ShaDa file dumping: header, registers, jump list, history, search patterns,
substitute strings, variables.
2. ShaDa file reading: registers, global marks, variables.
Most was not tested.
TODO:
1. Merging.
2. Reading history, local marks, jump and buffer lists.
3. Documentation update.
4. Converting some data from &encoding.
5. Safer variant of dumping viminfo (dump to temporary file then rename).
6. Removing old viminfo code (currently masked with `#if 0` in a ShaDa file for
reference).
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
- MSVC generates output using Windows newlines (\r\n) instead of (\n).
|
| |\
| |
| | |
Generate unicode tables with script
|
