On Fri, 11 Jul 2014 23:35:15 +0200
Bram Moolenaar b...@moolenaar.net wrote:
Since what version of xterm and screen is this supported? I suspect
older versions do not support it.
It ultimately doesn't really matter. You send DECSM 2000 to ask for it
to be enabled. Either that works and you now
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On July 14, 2014 6:09:22 PM GMT+03:00, Christian Brabandt cbli...@256bit.org
wrote:
On Mo, 14 Jul 2014, v...@googlecode.com wrote:
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 238 by kimmy.li...@gmail.com: linebreak
Hi Павлов!
On Mo, 14 Jul 2014, Павлов Николай Александрович wrote:
Replies here are not posted to the issue tracker.
I know. But I had limited internet connectivity and I am pretty sure,
Bram reads here sporadically.
Best,
Christian
--
Was mich immer tief alteriert hat, das ist die
Paul Evans wrote:
On Fri, 11 Jul 2014 23:35:15 +0200
Bram Moolenaar b...@moolenaar.net wrote:
Since what version of xterm and screen is this supported? I suspect
older versions do not support it.
It ultimately doesn't really matter. You send DECSM 2000 to ask for it
to be enabled.
On Sunday, July 13, 2014 2:20:04 PM UTC-7, Bram Moolenaar wrote:
Jacob Niehus wrote:
On Sunday, July 6, 2014 5:23:39 PM UTC-7, Jacob Niehus wrote:
After patch 7.4.314, I've had characters that I hadn't typed stay on
screen even though they aren't really there and they go away
This is a patch to create a separate json filetype and use it for *.json files
instead of using javascript. It currently just forwards indent and syntax
settings to the javascript filetype, but it does define its own
ftplugin/json.vim file since most of the settings in ftplugin/javascript.vim
