On Wed, Jul 26, 2017 at 8:51 AM, Nazri Ramliy wrote:
>
> Changing TERM=xterm results in invisible cursor:
Clarification: it's not that the cursor is completely invisible. It is
similar to what Marius reported in that for my case this is what I see
when opening :terminal:
1. I see new blank vim w
Hi Bram,
2017/7/26 Wed 4:47:55 UTC+9 Bram Moolenaar wrote:
> Ken Takata wrote:
>
> > 2017/7/25 Tue 5:29:46 UTC+9 Bram Moolenaar wrote:
> > > Ken Takata wrote:
> > >
> > > > I found some issues with the terminal feature (mainly on Windows):
> > > >
> > > > * Couldn't build with VC2010, because l
On Wed, Jul 26, 2017 at 3:35 AM, Bram Moolenaar wrote:
>
> I'm using a real xterm and don't see this problem.
> I don't have a blinking cursor, perhaps that is related?
Looks like it's not related.
Running xterm with cursor blinking enabled and disabled works fine
when TERM=ansi:
# Without blin
2017-07-25 18:00 GMT+03:00 mattn :
> Thanks your suggestion. BTW, I don't use neovim but I heard neovim have
> tmap/tnoremap? to remap terminal keys.
Neovim has separate terminal mode, with separate commands for mapping
(:tmap/:tnoremap). So ``, as well as everything else is sending
input directly
Tony Mechelynck wrote:
> After applying patches 8.0.768 to 8.0.771, I get the following warning
> from gcc in the Tiny build (compile goes on, and link happens
> apparently satisfactorily):
>
> gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
> -U_FORTIFY_SOURCE -D_FORTIFY_S
Patch 8.0.0776
Problem:Function prototypes missing without the quickfix feature. (Tony
Mechelynck)
Solution: Move non-quickfix functions to buffer.c.
Files: src/buffer.c, src/proto/buffer.pro, src/quickfix.c,
src/proto/quickfix.pro
*** ../vim-8.0.0775/src/buffe
Patch 8.0.0775
Problem:In a terminal the cursor is updated too often.
Solution: Only flush when needed. (Yasuhiro Matsumoto). Remeber whether the
cursor is visible. (closes #1873)
Files: src/terminal.c
*** ../vim-8.0.0774/src/terminal.c 2017-07-24 23:36:34.890967822
John Marriott wrote:
> On 23-Jul-2017 04:33, Bram Moolenaar wrote:
> > Patch 8.0.0748
> > Problem:When running Vim in a terminal window it does not detect the
> > right
> > number of colors available.
> > Solution: Detect the version string that libvterm returns. Pass the
>
Patch 8.0.0774
Problem:Build failure without the multi-byte feature on HPUX.
Solution: Move #ifdefs. (John Marriott)
Files: src/term.c
*** ../vim-8.0.0773/src/term.c 2017-07-23 16:45:05.669761183 +0200
--- src/term.c 2017-07-25 22:03:02.024915396 +0200
***
*** 4307,4322
Patch 8.0.0773
Problem:Mixing 32 and 64 bit libvterm builds fails.
Solution: Use OUTDIR. (Ken Takata)
Files: src/Make_cyg_ming.mak, src/Make_mvc.mak, src/libvterm/Makefile.msc
*** ../vim-8.0.0772/src/Make_cyg_ming.mak 2017-07-24 22:26:39.757774872
+0200
--- src/Make_cyg_ming.ma
On 25-Jul-2017 08:12, Tony Mechelynck wrote:
After applying patches 8.0.768 to 8.0.771, I get the following warning
from gcc in the Tiny build (compile goes on, and link happens
apparently satisfactorily):
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
-U_FORTIFY_SOURCE -D
Ken Takata wrote:
> 2017/7/25 Tue 5:29:46 UTC+9 Bram Moolenaar wrote:
> > Ken Takata wrote:
> >
> > > I found some issues with the terminal feature (mainly on Windows):
> > >
> > > * Couldn't build with VC2010, because libvterm requires stdbool.h.
> > > Reuse if_perl_msvc/stdbool.h for this.
On 23-Jul-2017 04:33, Bram Moolenaar wrote:
Patch 8.0.0748
Problem:When running Vim in a terminal window it does not detect the right
number of colors available.
Solution: Detect the version string that libvterm returns. Pass the number
of colors in $COLORS.
Files
Marius Gedminas wrote:
> On Tue, Jul 25, 2017 at 10:10:23AM +0800, Nazri Ramliy wrote:
> > Cursor visible:
> >
> > TERM=ansi vi -u NONE -U NONE -c :terminal
> >
> > Cursor not visible:
> >
> > TERM=xterm vi -u NONE -U NONE -c :terminal
> >
> > help?
>
> I can reproduce (vim 8.0.771 running i
Kazunobu Kuriyama wrote:
> 2017-07-25 18:10 GMT+09:00 Ozaki Kiichi :
>
> > > First, the patch seems to prevent Vim from crashing by simply changing
> > the order of the calls of XCheckTypedEvent(). This happens to work for the
> > purpose because the call for PropertyNotify happens to catch the
Patch 8.0.0772
Problem:Other stdbool.h dependencies in libvterm.
Solution: Remove the dependency and use TRUE/FALSE/int. (Ken Takata)
Files: src/libvterm/include/vterm.h, src/libvterm/src/mouse.c,
src/libvterm/src/pen.c, src/libvterm/t/harness.c,
src/libvterm/bin
I discovered an odd syntax highlighting problem while working on
a syntax plugin. I am trying to highlight single-line or multi-line
strings as group String and highlight any characters in strings
after the 'textwidth' column as group Error. The following simple
example demonstrates the problem.
Hi,
2017/7/25 Tue 20:11:29 UTC+9 tux. wrote:
> I always sync to head first. I'll supply the log tomorrow evening, won't be
> on the machine today...:) Basically, undefined _vterm_* symbols during
> linking, only on x64. Hmm.
If you try to build 32- and 64-bit version in the same directory, it
Hi Bram,
2017/7/25 Tue 5:29:46 UTC+9 Bram Moolenaar wrote:
> Ken Takata wrote:
>
> > I found some issues with the terminal feature (mainly on Windows):
> >
> > * Couldn't build with VC2010, because libvterm requires stdbool.h.
> > Reuse if_perl_msvc/stdbool.h for this.
> > (Maybe it's better
2017-07-24 21:57 GMT+09:00 M Kelly :
> Hi,
> Sorry if this is posted/solved already.
> When building v8.0.0765 I get this error:
>
> gui_x11.c: In function ‘gui_mch_get_color’:
> gui_x11.c:2274:14: warning: unused variable ‘colormap’ [-Wunused-variable]
> Colormap colormap;
> ^
I always sync to head first. I'll supply the log tomorrow evening, won't be on
the machine today...:) Basically, undefined _vterm_* symbols during linking,
only on x64. Hmm.
Thank you!
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the te
2017-07-25 18:10 GMT+09:00 Ozaki Kiichi :
> > First, the patch seems to prevent Vim from crashing by simply changing
> the order of the calls of XCheckTypedEvent(). This happens to work for the
> purpose because the call for PropertyNotify happens to catch the INCL
> PropertyNotify which is to be
Hi,
Sorry if this is posted/solved already.
When building v8.0.0765 I get this error:
gui_x11.c: In function ‘gui_mch_get_color’:
gui_x11.c:2274:14: warning: unused variable ‘colormap’ [-Wunused-variable]
Colormap colormap;
^
gui_x11.c:2273:17: warning: unused variable ‘availabl
Hi,
I get a build error on ubuntu with gcc with v8.0.765:
gui_x11.c: In function ‘gui_mch_get_color’:
gui_x11.c:2274:14: warning: unused variable ‘colormap’ [-Wunused-variable]
Colormap colormap;
^
gui_x11.c:2273:17: warning: unused variable ‘available’ [-Wunused-variable]
> First, the patch seems to prevent Vim from crashing by simply changing the
> order of the calls of XCheckTypedEvent(). This happens to work for the
> purpose because the call for PropertyNotify happens to catch the INCL
> PropertyNotify which is to be sent to the requestor prior to the actual
On Tue, Jul 25, 2017 at 10:10:23AM +0800, Nazri Ramliy wrote:
> Cursor visible:
>
> TERM=ansi vi -u NONE -U NONE -c :terminal
>
> Cursor not visible:
>
> TERM=xterm vi -u NONE -U NONE -c :terminal
>
> help?
I can reproduce (vim 8.0.771 running in gnome-terminal with
TERM=xterm-256color).
Note
Tux wrote:
> Hmm... works partially.
>
> x86 builds fine, x64 fails with a number of undefined _vertm_
> symbols...
Did you sync to head? There were a fe more MSVC improvements.
If you still see problems, please show the error messages.
Or send us a patch! :-)
--
Married is a three ring circ
27 matches
Mail list logo
