Or, does the issue happens only to me? I’m feeling uneasy because no one
comes up with the issue so far :-)
After the last series of patches, I tried re-running the builds on Travis CI,
and this issue occurs there as well [1] (context: [2]). Your patch fixes the
test run error [3], but I'm
On Wednesday, January 21, 2015 at 8:00:27 PM UTC-6, James McCoy wrote:
This sounds like what's already reported at
https://code.google.com/p/vim/issues/detail?id=267.
Yes, seems very like the same.
On Thursday, 22 January 2015 07:20:54 UTC+2, Ben Fritz wrote:
Try with this patch
On Jan 22, 2015, at 0:15, Kazunobu Kuriyama kazunobu.kuriy...@nifty.com wrote:
Hi,
On Jan 21, 2015, at 3:01, Bram Moolenaar b...@moolenaar.net wrote:
Patch 7.4.587
Problem:Conceal does not work properly with 'linebreak'. (cs86661)
Solution: Save and restore boguscols. (Christian
On Thursday, January 22, 2015 at 10:11:40 AM UTC-6, ZyX wrote:
2015-01-21 23:02 GMT+03:00 Ben Fritz fritzophre...@gmail.com:
Many open-source projects do not accept major new features or
potentially breaking changes except at minor or major version
updates. Vim is the same way. 7.4.600
2015-01-22 19:24 GMT+03:00 Ben Fritz fritzophre...@gmail.com:
On Thursday, January 22, 2015 at 10:11:40 AM UTC-6, ZyX wrote:
2015-01-21 23:02 GMT+03:00 Ben Fritz fritzophre...@gmail.com:
Many open-source projects do not accept major new features or
potentially breaking changes except
2015-01-21 23:02 GMT+03:00 Ben Fritz fritzophre...@gmail.com:
On Wednesday, January 21, 2015 at 1:33:35 PM UTC-6, Tim Lebedkov wrote:
For a beginning, you could maintain a separate installer so that people
can actually try that it works and you get feedback. Then you can also
gradually
Updates:
Status: Accepted
Comment #2 on issue 321 by drc...@campbellfamily.biz: syntax/tex.vim does
not track braces inside \ensuremath{} blocks
https://code.google.com/p/vim/issues/detail?id=321
Please try syntax/tex.vim v84 from my website:
Kazunobu Kuriyama wrote:
On Jan 22, 2015, at 0:15, Kazunobu Kuriyama kazunobu.kuriy...@nifty.com
wrote:
Hi,
On Jan 21, 2015, at 3:01, Bram Moolenaar b...@moolenaar.net wrote:
Patch 7.4.587
Problem:Conceal does not work properly with 'linebreak'. (cs86661)
Solution:
Patch 7.4.590
Problem:Using ctrl_x_mode as if it contains flags.
Solution: Don't use AND with CTRL_X_OMNI. (Hirohito Higashi)
Files: src/edit.c
*** ../vim-7.4.589/src/edit.c 2014-11-12 18:59:17.602000656 +0100
--- src/edit.c 2015-01-20 19:43:45.376745467 +0100
***
***
Patch 7.4.591 (after 7.4.587)
Problem:test_listlbr_utf8 fails when the conceal feature is not available.
Solution: Check for the conceal feature. (Kazunobu Kuriyama)
Files: src/testdir/test_listlbr_utf8.in
*** ../vim-7.4.590/src/testdir/test_listlbr_utf8.in 2015-01-20
On Thu, Jan 22, 2015 at 06:14:43PM +0900, Kazunobu Kuriyama wrote:
On Jan 22, 2015, at 0:15, Kazunobu Kuriyama kazunobu.kuriy...@nifty.com
wrote:
Hi,
On Jan 21, 2015, at 3:01, Bram Moolenaar b...@moolenaar.net wrote:
Patch 7.4.587
Problem:Conceal does not work properly with
Comment #1 on issue 321 by ewtoo...@gmail.com: syntax/tex.vim does not
track braces inside \ensuremath{} blocks
https://code.google.com/p/vim/issues/detail?id=321
I just found a way to fix this problem! After some vimming, I found
replacing line 469 with the following lines sufficient to
Dominique Pellé dominique.pe...@gmail.com wrote:
Hi
The regexp .\{1,9000} is very slow with the new regexp engine
compared to the old engine. Compare the timing of those 2
commands where the only difference is set re=1 vs set re=2:
$ time vim -X -u NONE \
-c 'set re=1' \
Bram Moolenaar wrote:
Dominique Pellé dominique.pe...@gmail.com wrote:
Hi
The regexp .\{1,9000} is very slow with the new regexp engine
compared to the old engine. Compare the timing of those 2
commands where the only difference is set re=1 vs set re=2:
$ time vim -X -u NONE \
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 321 by ewtoo...@gmail.com: syntax/tex.vim does not track braces
inside \ensuremath{} blocks
https://code.google.com/p/vim/issues/detail?id=321
What steps will reproduce the problem?
1. open vim
2. type :setf tex
3. type
Am Sonntag, 18. Januar 2015 14:16:17 UTC+1 schrieb MarcWeber:
If you followed the official documentation: http://www.vim.org/develop.php
you should be fine.
In the past there have some issues with the patch / review workflow for
different reasons. A fork NeoVim has happened as well for
Am Mittwoch, 21. Januar 2015 20:57:26 UTC+1 schrieb Christian Brabandt:
Hi Tim!
On Mi, 21 Jan 2015, Tim Lebedkov wrote:
I did, but everything I hear is that the changes will be merged maybe
in 2016 (and maybe not).
I can understand, that this is frustrating and I have felt the same,
17 matches
Mail list logo