| Commit message (Collapse) | Author | Age |
... | |
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: No digraph for the new rouble sign.
Solution: Add the digraphs =R and =P.
https://code.google.com/p/vim/source/detail?r=8ad2ecd116021ad5c945426e8bb80d741392b780
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: When 'verbose' is set to display the return value of a function, may get E724 repeatedly.
Solution: Do not give an error for verbose messages. Abort conversion to string after an error.
https://code.google.com/p/vim/source/detail?r=99d8f2d72dcd4b850de81998cc9b1120c8165762
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Relative numbering not updated after a linewise yank. Issue 235.
Solution: Redraw after the yank. (Christian Brabandt)
https://code.google.com/p/vim/source/detail?r=6d984caa0409fd284722c44cb09a0a2b5360bd4f
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Clang analyzer: fix dead stores / reduce scope
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: Substitute() with zero width pattern breaks multi-byte character.
Solution: Take multi-byte character size into account. (Yukihiro Nakadaira)
https://code.google.com/p/vim/source/detail?r=238f5027830cad22e17a970483af9b160869cdf3
|
| | | |
| | | |
| | | |
| | | | |
- Add API function to call replace_termcodes
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- To clean up the mix between feedkeys and replace_termcodes
the vim_feedkeys API function now does the same thing as the
vimscript feedkeys() function
- The original f_feedkeys() function now calls the vim_feedkeys()
function from the API
|
|/ / /
| | |
| | |
| | | |
- Add nocopy helper alternative to cstr_to_string
|
|\ \ \ |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
It was used in Vim for NeXT OS.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
libuv provide uv_get_total_mem_kib. So HAVE_TOTAL_MEM should always be
true.
Before that commit in neovim maxmem=5120 and maxmemtot=10240. Now
both equal to half of system memory.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This feature allow to use any white space characters instead of one
<TAB> in tag files. It is disabled in vanilla Vim's default build
configuration. Exuberant ctags use format with exactly one TAB.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Feature description from Vim documentation:
NOTE: this code is currently disabled, as the RISC OS implementation was
removed. In the future this will use the 'filetype' option.
On operating systems which support storing a file type with the file, you can
specify that an autocommand should only be executed if the file is of a
certain type.
The actual type checking depends on which platform you are running Vim
on; see your system's documentation for details.
To use osfiletype checking in an autocommand you should put a list of types to
match in angle brackets in place of a pattern, like this: >
:au BufRead *.html,<&faf;HTML> runtime! syntax/html.vim
This will match:
- Any file whose name ends in ".html"
- Any file whose type is "&faf" or "HTML", where the meaning of these types
depends on which version of Vim you are using.
Unknown types are considered NOT to match.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
All code which was inside #ifdef CURSOR_SHAPE is being used now, except
one in version.c (that occurence is fixed by this commit).
|
| | | | |
|
| | |/
| |/|
| | |
| | | |
It is already partially removed from screen.c
|
| | |
| | |
| | |
| | | |
This is unused after dropped amiga and msdos support.
|
| | | |
|
| | | |
|
| |/
|/|
| |
| | |
Fixes #1039
|
|/
|
|
|
|
|
| |
Problem: Fixes for computation of topline not tested.
Solution: Add test. (Hirohito Higashi)
https://code.google.com/p/vim/source/detail?r=646616b6ff4defcc7bef0b198b540f6d965a8126
|
| |
|
|
|
|
|
|
|
|
| |
Problem: When increasing the size of the lower window, the upper
window jumps back to the top. (Ron Aaron)
Solution: Change setting the topline. (Nobuhiro Takasaki)
https://code.google.com/p/vim/source/detail?r=88a6e9f33822d33b6c32db578750c6c178c63f50
|
|
|
|
|
| |
They were removed but they can be handy to separate some things to do at
startup in a .vimrc for example.
|
|
|
|
|
| |
It was already removed in 01ca460 and I erroneously introduced it again in
PR #978.
|
|\
| |
| | |
Minor buffer.c style cleanups
|
| | |
|
| |
| |
| |
| | |
This is never built and references some obscure jsb terminal
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* With the changes in commit
"events: Refactor how event deferral is handled"
(2e4ea29d2c7b62eb8baf1c41cd43433e085dda0) the function argument
'defer' of 'job_start' and member variable 'defer' of 'struct job'
can be removed.
* Update/Fix the documentation for function 'job_start'.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Not necessary, as discussed in #980.
From the libuv mailing list:
https://groups.google.com/forum/#!topic/libuv/OD38PeGeVgQ
E.g. this could happen (red: on Windows):
> > alloc_cb(handle1);
> > alloc_cb(handle2);
> > read_cb(handle1);
> > read_cb(handle2);
But this couldn't:
> > alloc_cb(handle1);
> > alloc_cb(handle1);
> > read_cb(handle1);
> > read_cb(handle1);
Because each stream has a 1-to-1 correspondance with a libuv handle. The
code removed was never executed.
Closes #980.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It used to be 1024 bytes, which is very tiny and slows down some operations
(imaging `cat`-ing a large file). Benchmarks show a large speedup for such
cases. ref #978.
For modern systems 0xFFFF bytes (65535 B = 64 KB = 0.0625 MB) per job
shouldn't be a big problem.
|
| |
| |
| |
| |
| |
| | |
This evades the tempfile problem (unless of course one manually adds
redirects to the shell commandline, which some plugins seem to do, e.g.:
vim-easytags).
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
With the goal to support pipe-only system() calls.
Notes on the second (vim) argument to f_system() (i.e.: redirected input)
and its implications:
- When calling system('cat -', ['some', 'list']), vanilla vim (before a
recent patch that added support for passing lists) just passes an empty
file to the process. This is the same as immediately closing the pipe,
which os_system does when no input is given. If we wouldn't close the
pipe, the process will linger forever (as is the case with `cat -`).
As of now, it's not allowed to pass a non-NULL pointer as the `output`
parameter. In other words, it's not possible to signal disinterst in the
process output. That may change in the future.
|
| |
| |
| |
| |
| |
| | |
- One can now manually close the in-pipe, without having to tear down the
job.
- One can be notified of write success/failure.
|