| Commit message (Collapse) | Author | Age |
... | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Processes in vim are always started in the current directory, which
causes issues when the process is a daemon and the current directory is
a mountpoint. Fix this by adding an option to set the cwd of the new
process with jobstart(). In addition, fix termopen() so that it actually
uses the cwd option from the dict (it couldn't previously set the cwd
value due to dead code).
Signed-off-by: Aleksa Sarai <cyphar@cyphar.com>
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Current name is inappropriate for the following reasons:
1. It is often masked by local `loop` variables.
2. It cannot be searched for. There are many `loop` variables where `loop` is
some local variable. There are many cases when “loop” word is used in
a comment.
3. It is in any case bad idea to use a generic name as a name of the global
variable. Best if global has module prefix: this is why it is in `main.h`:
`main_loop` both stands for “a main loop” and “a loop defined in `main.*`”.
Since I have no idea how to list every occurrence of this variable method used
to rename it is “remove it from globals.h, try to compile, fix errors”. Thus if
some occurrence was hidden under false `#if` branch it was not replaced.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Conforms to Vim's mch_nodetype. Regression by 7db4a15.
buf_write() expects NODE_WRITABLE for character devices such as
/dev/stderr.
Closes #4772
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
...and small refactorings:
- Style changes
- Variable renames
- Changes in variable scope
This change won't bring new problems (undefined behavior) as `memcpy` is
already being used in the function.
|
|/ |
|
|
|
|
|
|
|
|
|
| |
Problem: Editing a URL, which netrw should handle, doesn't work.
Solution: Avoid changing slashes to backslashes. (Yasuhiro Matsumoto)
https://github.com/vim/vim/commit/b4f6a46b01ed00b642a2271e9d1559e51ab0f2c4
Cherry-picked from https://github.com/neovim/neovim/pull/810, rebased.
|
| |
|
|\
| |
| | |
vim-patch:7.4.672
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: When completing a shell command, directories in the current
directory are not listed.
Solution: When "." is not in $PATH also look in the current directory for
directories.
https://github.com/vim/vim/commit/b5971141dff0c69355fd64196fcc0d0d071d4c82
Most of it applied manually.
|
|\ \
| |/
|/| |
Windows: Include winsock2.h before windows.h
|
| |
| |
| |
| |
| |
| |
| | |
winsock2.h is incompatible with winsock.h (included by windows.h) and must
be included first. For reference see
https://msdn.microsoft.com/en-us/library/windows/desktop/ms737629%28v=vs.85%29.aspx
|
|/
|
|
| |
Originally there were 128 new errors, so I thought this is a good idea to fix
all of them. Of course, this commit also fixes many suppressed errors.
|
|\
| |
| | |
Increase readability of unit conversion.
|
| | |
|
|/
|
|
| |
In Windows, open() flags like O_RDONLY need fcntl.h.
|
| |
|
|\
| |
| | |
Make some function accept strings with length in place of just strings
|
| |
| |
| |
| |
| |
| |
| | |
Reasons:
- One does not have to do `s[len] = NUL` to work with these functions if they do
not need to replace the whole string: thus `s` may be const.
- One does not have to save/restore p_cpo to work with them.
|
|/
|
|
|
|
|
| |
Problem: delete() does not work well with symbolic links.
Solution: Recognize symbolik links.
https://github.com/vim/vim/commit/43a34f9f74fdce462fa250baab620264c28b6165
|
| |
|
|
|
|
|
|
| |
Introduced here:
https://github.com/neovim/neovim/commit/4bfac00aa389487c4f11d34e7a3e96e4a1116800#diff-2bf87eef9f7b99dcea4b0c55beee2d63R78
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The previous defaults were including the nvim suffix, causing it to
apear twice in the final paths.
kXDGDataHome and kXDGConfigHome are now set as %LOCALAPPDATA%,
kXDGCacheHome is set as $TEMP.
In Windows there is no distinction between configuration and data
storage, but we don't want to place all files under the same path.
get_xdg_home() now appends a different path suffix for kXDGDataHome.
- Configuration files are saved under %LOCALAPPDATA%\nvim
- Data files are saved under %LOCALAPPDATA%\nvim-data
|
|\
| |
| | |
build: install *.mo into the "standard" directory
|
| |
| |
| |
| |
| |
| |
| | |
Change POROJECT_NAME to 'nvim', and use it as the gettext
domain name. The *.mo files, previously installed as
$runtime/lang/xx/LC_MESSAGES/nvim.mo, are now installed as
$prefix/locale/xx/LC_MESSAGES/nvim.mo.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: Crash when dragging with the mouse.
Solution: Add safety check for NULL pointer. Check mouse position for valid
value. (Hirohito Higashi)
https://github.com/vim/vim/commit/294a7e55b01149154807a23323038784549b8946
---
see: "Crash while mouse-selecting in two-buffer mode"
https://github.com/vim/vim/issues/486
Fix #3704
|
| |
| |
| |
| |
| |
| |
| | |
Problem: Compiler warning for possible loss of data.
Solution: Add a type cast. (Erich Ritz)
https://github.com/vim/vim/commit/5df1ed2de3fa9dcace996b9a0a4c9b3cea79cf1e
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem: $HOME in `=$HOME . '/.vimrc'` is expanded too early.
Solution: Skip over `=expr` when expanding environment names.
https://github.com/vim/vim/commit/be83b73ddb2ee8297037166d243f72e3423a3ce3
---
To reproduce:
```sh
nvim -u NONE -c 'e `=$HOME . "/.vimrc"`'
```
|
|\
| |
| | |
Windows: use $PATHEXT to find executables in path
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
is_executable_in_path() searches for executables in $PATH, but on
Windows executable files have extensions available in the environment
var $PATHEXT. This commit changes is_executable_in_path() to append
those extensions to the filename.
This patch diverges from standard Vim, in that Vim only checked for
the given filename if it already has an extensions. This one always
checks for the given filename.
|
|\ \
| | |
| | | |
Windows: include <io.h>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
if_csope.c uses _open_osfhandle so include the necessary header.
Futher we need <io.h> for read/write/close/lseek.
See: https://msdn.microsoft.com/en-us/library/bdts1c9x.aspx
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| | |
Unix systems must have this header but Windows does not have it at all.
Since src/nvim/os/unix_defs.h includes <unistd.h> without the guard
in order to avoid including this in the numerous places we would
need <unistd.h> on Unix we just include src/nvim/os/os.h which will pull
in <unistd.h> for us.
|
|/
|
|
| |
S_IFLNK is not defined on Windows but libuv defines it for us.
|
|
|
|
| |
It's not present on Windows; see the discussion in #4024.
|
|
|
|
|
|
|
|
|
|
| |
Although UNIX is a registered trademark of The Open Group, it doesn't
really matter whether we refer to these systems as UNIX, Unix, or
Unix-like. So, for consistency, refer to them collectively as Unix.
Related:
http://www.greens.org/about/unix.html
http://www.unixica.com/html/unixunix.html
|
|
|
|
|
|
| |
Among other things, this includes:
- lies about command.com
- references to pcterm
|
|
|
|
|
|
|
|
|
|
| |
- ROOT_UID's comment is misleading, as it's always defined to 0.
- SEEK_{SET,END} & O_NOFOLLOW should already be defined on Unix-like
systems in <stdio.h> and <fcntl.h>, respectively. In any case,
neither of those #ifdef blocks should be in the middle of source files.
- The S_IS{LNK,DIR,...} macros should only be undefined on Windows.
|
|
|
|
|
|
|
| |
Windows provides a RGB macro but we have our own in macros.h.
Undefine the Windows one before including macros.h.
See: https://msdn.microsoft.com/en-us/library/dd162937%28v=vs.85%29.aspx
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
vim-patch:7.4.569
vim-patch:7.4.573
Helped-by: @glts https://github.com/neovim/neovim/pull/2621
Problem: Having CTRL-C interrupt or not does not check the mode of the
mapping. (Ingo Karkat)
Solution: Use a bitmask with the map mode. (Christian Brabandt)
https://github.com/vim/vim/commit/651863c94a882a97aec7968fc87a638ff78e56ff
Problem: Mapping CTRL-C in Visual mode doesn't work. (Ingo Karkat)
Solution: Call get_real_state() instead of using State directly.
https://github.com/vim/vim/commit/5000869712f799d9ca25c0e45dc21d332edae5f4
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For non-Windows systems, we assume that NAME_MAX is in <limits.h>, as
specified in POSIX.1-2008[1]. For Windows, which doesn't have NAME_MAX,
just define it ourselves to _MAX_PATH[2].
Also, remove two (now unused) HAVE_*_H checks.
[1]: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/limits.h.html
[2]: https://msdn.microsoft.com/en-us/library/930f87yf.aspx
Helped-by: Seth Jackson
|
|
|
|
|
|
| |
In Windows the separator character in the PATH environment is ';' instead
of ':'. Add a new define ENV_SEPCHAR to be used instead of hardcoding
the character literal.
|
|\
| |
| | |
shell: Unquote &shell* options before using them
|
| | |
|
|/
|
|
|
| |
MAXNAMLEN can be defined using _MAX_PATH from stdlib.h
which will fix the BASENAMELEN definition too.
|
| |
|
|
|
|
|
| |
The Vim code for windows in if_cscope.c/.h was removed during the refactor,
added missing code for error_closing().
|
|
|
|
|
|
| |
Since uid_t is not defined on Windows use uv_uid_t instead.
We now use uv_uid_t everywhere except one place in src/nvim/main.c
which is wrapped in a #ifdef UNIX check.
|
| |
|