fully disable xterm title?

2017-05-22 Thread bela . lubkin
Hi, I want to fully disable vim's xterm title bar manipulation. Web searches offer ten thousand advices on how to turn it *on*, but very little on turning it off. sigh. Using -- $ script -c 'vim foobar' /tmp/junk -- I can see that even with "set notitle" in my .vimrc, vim still sets the

Re: Bug in ftdetect?

2017-05-22 Thread Frew Schmidt
FYI I reproduced this with a recent checkout and also a 7.3 build, so I'm pretty sure it's neither fixed nor a regression. I will look into profiling the issue, but I am still baffled. -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the

Bug in ftdetect?

2017-05-22 Thread Frew Schmidt
I recently discovered that using ftdetect is absurdly slower than filetype.vim. To reproduce, try this: mkdir -p ~/.vim/ftdetect echo 'autocmd BufNew,BufNewFile,BufRead *.md :set filetype=markdown' > ~/.vim/ftdetect/markdown.vim mkdir testing cd testing touch

Re: "superscript" asterisk is gone!

2017-05-22 Thread Charles E Campbell
Tony Mechelynck wrote: > In Bitstream Vera Sans Mono 8 in gvim 8.0.600 for GTK3 (which I just > made using "make reconfig" after an update of the python2, python3 and > IIRC lua packages), U+20F0 is present in the buffer and gvim > recognises it as a composing character, but its display is easy to

Bug/non-determinism in output of maparg() and map commands

2017-05-22 Thread Brett Stahlman
I would like to be able to save and restore mappings programmatically. In order to do so, however, I need to be able to determine the exact lhs and rhs used to create the mapping. I had assumed the lhs/rhs members of the dictionary returned by maparg() would provided this information, but as the

Re: Search highlighting that honors syntax coloring

2017-05-22 Thread Ben Fritz
On Saturday, May 20, 2017 at 2:49:45 AM UTC-5, Steve Simmons wrote: > Advance apologies if my google-fu has failed and there's already an answer to > this somewhere - > > I'd like to have search highlighting honor the current state of syntax > coloring but inverting foreground and background.

Re: :right command on Chinese characters

2017-05-22 Thread Tim Chase
On 2017-05-22 01:49, Joey Ling wrote: > On Sunday, May 21, 2017 at 8:15:50 PM UTC+8, Tim Chase wrote: > > I suspect what's happening is that, since Vim does the > > right-justification with spaces, Word is displaying all those > > spaces and then not having enough room to display the last > >

Re: :right command on Chinese characters

2017-05-22 Thread Joey Ling
On Sunday, May 21, 2017 at 8:15:50 PM UTC+8, Tim Chase wrote: > On 2017-05-21 19:54, Joey wrote: > > When I run :right command in gvim, it's ok, like this: > > > >彼外道常说自然,我说因缘。——楞严经 > > > > But if I open the txt file with Word, it's like this: > > > >