Colaboratiion feature hint [Re: Plans for Vim 7.4]
Hi list! Am 09.05.2013 05:51, schrieb Bram Moolenaar: [..] 5. add collaborative editing [..] This is a feature that Im looking for a long time. Im not so deep inside that I would be able to write the code for this, but maybe I can give a hint from the Libreoffice-project, which uses this way for generating this (if I understand right, this is not yet contributed as stable): - all collaborating programs are using a chatroom based on jabber protocol, so it is possiblie to collaborate over net - the editing commands are sent as xml-code to this chatroom, so all are able to get complex actions, too (maybe this is not needed for vim) - every writer gets an own color, so it is possible to see, who is writing at the moment On the other side, at the moment it is possible to collaborate a bit with vim running inside a screen, but this requires a login for all subscribers to the machine running screen. Last but not least there exist a project for collaborated writing: Google Wave, which is imho open source, so there we can find some useful code for this. Regards from Linuxtag Berlin Oliver -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Colaboratiion feature hint [Re: Plans for Vim 7.4]
On Thu, May 23, 2013 at 1:32 PM, Oliver Rath r...@mglug.de wrote: Hi list! Am 09.05.2013 05:51, schrieb Bram Moolenaar: [..] 5. add collaborative editing [..] This is a feature that Im looking for a long time. Im not so deep inside that I would be able to write the code for this, but maybe I can give a hint from the Libreoffice-project, which uses this way for generating this (if I understand right, this is not yet contributed as stable): - all collaborating programs are using a chatroom based on jabber protocol, so it is possiblie to collaborate over net - the editing commands are sent as xml-code to this chatroom, so all are able to get complex actions, too (maybe this is not needed for vim) - every writer gets an own color, so it is possible to see, who is writing at the moment On the other side, at the moment it is possible to collaborate a bit with vim running inside a screen, but this requires a login for all subscribers to the machine running screen. Last but not least there exist a project for collaborated writing: Google Wave, which is imho open source, so there we can find some useful code for this. There was this new plugin in the news several days ago https://github.com/FredKSchott/CoVim CoVim - Collaborative Editing for Vim -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Patch 7.3.1005
it's still slow for general search, especially in big file. -. Vim 7.3 1005/Vista -. file size, c. 20M (utf-8) It's got stuck after 7.3-996 for me. -Regards, William On Thu, May 23, 2013 at 11:17 AM, h_east h.east@gmail.com wrote: Hi, Cesar 2013/5/23(Thu) 8:04:11 UTC+9 Cesar: It doesn't solve the issue for %s/^\n\+/\r. It gets stuck as before. Really? My vim7.3.1005 works well. It appears to have solved for me. Best regards, Hirohito Higashi -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[PATCH] Fix small typo in regexp.c
I was diving in the Vim source, and I found a small typo. Here's a patch to
fix it.
Thanks,
Rob
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
vim_dev group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
diff -r 05b791824368 src/regexp.c
--- a/src/regexp.c Wed May 22 23:00:40 2013 +0200
+++ b/src/regexp.c Thu May 23 09:05:19 2013 +0200
@@ -7773,7 +7773,7 @@
#ifdef DEBUG
static char_u regname[][30] = {
AUTOMATIC Regexp Engine,
- BACKTACKING Regexp Engine,
+ BACKTRACKING Regexp Engine,
NFA Regexp Engine
};
#endif
Re: Problems of new regexp engine (that we know)
Bram, I fixed: * \%# * \%23c \%23l * \%23c \%23l * \%23c \%23l * Treat leading * as star character * \_[ * \@! https://gist.github.com/mattn/5626661 Please check this patch. - Yasuhiro Matsumoto -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [PATCH] Fix small typo in regexp.c
Rob Hoelz wrote: I was diving in the Vim source, and I found a small typo. Here's a patch to fix it. Thanks. -- DENNIS: Oh, very nice. King, eh! I expect you've got a palace and fine clothes and courtiers and plenty of food. And how d'you get that? By exploiting the workers! By hanging on to outdated imperialist dogma which perpetuates the social and economic differences in our society! Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Plans for Vim 7.4
Hello Bram, hello Ron, Bram Moolenaar wrote: Hello Vim users, [...] Besides that, if you are maintaining runtime files, please send me any pending updates. I will not make big changes just before the release, everything needs some time for testing. Let's set a deadline at the end of May. Attached, you can find a new version of prolog.vim (syntax highlightning for prolog) and koehler.vim (my colorscheme). The former fixes a bug in prologClauseHead higlightning, the later now supports the Underline and Ignore groups. @Ron: please include the koehler.vim in your own repository. Bye, Thomas -- Thomas Köhler Email: jean-...@picard.franken.de WWW: http://gott-gehabt.de IRC: tkoehler Freenode: thkoehler PGP public key available from Homepage! local syntax file - set colors on a per-machine basis: vim: tw=0 ts=4 sw=4 Vim color file Maintainer: Ron Aaron r...@ronware.org Last Change: 2013 May 23 hi clear set background=dark if exists(syntax_on) syntax reset endif let g:colors_name = koehler hi Normal guifg=white guibg=black hi Scrollbar guifg=darkcyan guibg=cyan hi Menu guifg=black guibg=cyan hi SpecialKey term=bold cterm=bold ctermfg=darkred guifg=#cc hi NonTextterm=bold cterm=bold ctermfg=darkred gui=bold guifg=#cc hi Directory term=bold cterm=bold ctermfg=brown guifg=#cc8000 hi ErrorMsg term=standout cterm=bold ctermfg=grey ctermbg=red guifg=White guibg=Red hi Search term=reverse ctermfg=white ctermbg=red guifg=white guibg=Red hi MoreMsgterm=bold cterm=bold ctermfg=darkgreen gui=bold guifg=SeaGreen hi ModeMsgterm=bold cterm=bold gui=bold guifg=White guibg=Blue hi LineNr term=underline cterm=bold ctermfg=darkcyan guifg=Yellow hi Question term=standout cterm=bold ctermfg=darkgreen gui=bold guifg=Green hi StatusLine term=bold,reverse cterm=bold ctermfg=lightblue ctermbg=white gui=bold guifg=blue guibg=white hi StatusLineNC term=reverse ctermfg=white ctermbg=lightblue guifg=white guibg=blue hi Title term=bold cterm=bold ctermfg=darkmagenta gui=bold guifg=Magenta hi Visual term=reverse cterm=reverse gui=reverse hi WarningMsg term=standout cterm=bold ctermfg=darkred guifg=Red hi Cursor guifg=bg guibg=Green hi Commentterm=bold cterm=bold ctermfg=cyan guifg=#80a0ff hi Constant term=underline cterm=bold ctermfg=magenta guifg=#ffa0a0 hi Specialterm=bold cterm=bold ctermfg=red guifg=Orange hi Identifier term=underline ctermfg=brown guifg=#40 hi Statement term=bold cterm=bold ctermfg=yellow gui=bold guifg=#60 hi PreProcterm=underline ctermfg=darkmagenta guifg=#ff80ff hi Type term=underline cterm=bold ctermfg=lightgreen gui=bold guifg=#60ff60 hi Error term=reverse ctermfg=darkcyan ctermbg=black guifg=Red guibg=Black hi Todo term=standout ctermfg=black ctermbg=darkcyan guifg=Blue guibg=Yellow hi CursorLine term=underline guibg=#55 cterm=underline hi CursorColumn term=underline guibg=#55 cterm=underline hi MatchParen term=reverse ctermfg=blue guibg=Blue hi TabLineterm=bold,reverse cterm=bold ctermfg=lightblue ctermbg=white gui=bold guifg=blue guibg=white hi TabLineFillterm=bold,reverse cterm=bold ctermfg=lightblue ctermbg=white gui=bold guifg=blue guibg=white hi TabLineSel term=reverse ctermfg=white ctermbg=lightblue guifg=white guibg=blue hi Underlined term=underline cterm=bold,underline ctermfg=lightblue guifg=lightblue gui=bold,underline hi Ignore ctermfg=black ctermbg=black guifg=black guibg=black hi link IncSearch Visual hi link String Constant hi link Character Constant hi link Number Constant hi link Boolean Constant hi link Float Number hi link FunctionIdentifier hi link Conditional Statement hi link Repeat Statement hi link Label Statement hi link OperatorStatement hi link Keyword Statement hi link Exception Statement hi link Include PreProc hi link Define PreProc hi link Macro PreProc hi link PreCondit PreProc hi link StorageClassType hi link Structure Type hi link Typedef Type hi link Tag Special hi link SpecialChar Special hi link Delimiter Special hi link SpecialComment Special hi link Debug Special Vim
Re: Plans for Vim 7.4
Hallo Bram,
Thomas Köhler wrote:
Attached, you can find a new version of prolog.vim (syntax
highlightning for prolog) and koehler.vim (my colorscheme). The
former fixes a bug in prologClauseHead higlightning, the later
now supports the Underline and Ignore groups.
While I'm at it, I also just fixed a bug in uil.vim, see attached
version.
Ciao,
Thomas
--
Thomas Köhler Email: jean-...@picard.franken.de
WWW: http://gott-gehabt.de
IRC: tkoehler Freenode: thkoehler
PGP public key available from Homepage!
Vim syntax file
Language: Motif UIL (User Interface Language)
Maintainer: Thomas Koehler jean-...@picard.franken.de
Last Change: 2013 May 23
URL:
http://gott-gehabt.de/800_wer_wir_sind/thomas/Homepage/Computer/vim/syntax/uil.vim
Quit when a syntax file was already loaded
if version 600
syntax clear
elseif exists(b:current_syntax)
finish
endif
A bunch of useful keywords
syn keyword uilType arguments callbacks color
syn keyword uilType compound_string controlsend
syn keyword uilType exportedfileinclude
syn keyword uilType module object procedure
syn keyword uilType user_definedxbitmapfile
syn keyword uilTodo contained TODO
String and Character constants
Highlight special characters (those which have a backslash) differently
syn match uilSpecial contained \\\d\d\d\|\\.
syn region uilString start=++ skip=+\|\\+ end=++
contains=@Spell,uilSpecial
syn match uilCharacter'[^\\]'
syn region uilString start=+'+ skip=+\|\\'+ end=+'+
contains=@Spell,uilSpecial
syn match uilSpecialCharacter '\\.'
syn match uilSpecialStatement Xm[^ =(){}]*
syn match uilSpecialFunction MrmNcreateCallback
syn match uilRessourceXmN[^ =(){}]*
syn match uilNumber-\=\\d*\.\=\d\+\(e\=f\=\|[uU]\=[lL]\=\)\
syn match uilNumber0[xX]\x\+\
syn region uilComment start=/\* end=\*/ contains=@Spell,uilTodo
syn match uilComment !.* contains=@Spell,uilTodo
syn match uilCommentError \*/
syn region uilPreCondit
start=^#\s*\(if\\|ifdef\\|ifndef\\|elif\\|else\\|endif\\) skip=\\$
end=$ contains=uilComment,uilString,uilCharacter,uilNumber,uilCommentError
syn match uilIncluded contained [^]*
syn match uilInclude ^#\s*include\s\+.
contains=uilString,uilIncluded
syn match uilLineSkip \\$
syn region uilDefinestart=^#\s*\(define\\|undef\\) end=$
contains=uilLineSkip,uilComment,uilString,uilCharacter,uilNumber,uilCommentError
syn sync ccomment uilComment
Define the default highlighting.
For version 5.7 and earlier: only when not done already
For version 5.8 and later: only when an item doesn't have highlighting yet
if version = 508 || !exists(did_uil_syn_inits)
if version 508
let did_uil_syn_inits = 1
command -nargs=+ HiLink hi link args
else
command -nargs=+ HiLink hi def link args
endif
The default highlighting.
HiLink uilCharacter uilString
HiLink uilSpecialCharacteruilSpecial
HiLink uilNumber uilString
HiLink uilCommentErroruilError
HiLink uilInclude uilPreCondit
HiLink uilDefine uilPreCondit
HiLink uilIncludeduilString
HiLink uilSpecialFunction uilRessource
HiLink uilRessource Identifier
HiLink uilSpecialStatementKeyword
HiLink uilError Error
HiLink uilPreCondit PreCondit
HiLink uilTypeType
HiLink uilString String
HiLink uilComment Comment
HiLink uilSpecial Special
HiLink uilTodoTodo
delcommand HiLink
endif
let b:current_syntax = uil
vim: ts=8
signature.asc
Description: Digital signature
Pretty ugly bug in the new regex engine
Executing this regex:
s#יְהוָה\Z#\\hashem{}#eg
On this text:
וְיַעֲשׂוּ בְנֵי-יִשְׂרָאֵל אֶת-הַפָּסַח, בְּמוֹעֲדוֹ
Gives this garbage:
\hashem{}\hashem{}\hashem{}\hashem{}\hashem{}\hashem{}\hashem{}\hashem{}
Instead of this :
וְיַעֲשׂוּ בְנֵי־יִשְׂרָאֵל אֶת־הַפָּסַח, בְּמוֹעֲדוֹ
(attaching this also as a file)
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups vim_dev group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Executing this regex:
s#יְהוָה\Z#\\hashem{}#eg
On this text:
וְיַעֲשׂוּ בְנֵי-יִשְׂרָאֵל אֶת-הַפָּסַח, בְּמוֹעֲדוֹ
Gives this garbage:
\hashem{}\hashem{}\hashem{}\hashem{}\hashem{}\hashem{}\hashem{}\hashem{}
Instead of this :
וְיַעֲשׂוּ בְנֵי־יִשְׂרָאֵל אֶת־הַפָּסַח, בְּמוֹעֲדוֹ
[patch] test95 fails on Windows
Hi, I found some problems in the test95. 1. The test waits a user's input because set nomore is missing. 2. The test fails on Windows because \i matches § (0xa7). The default value of 'isident' is different on Windows. 3. There are three tests using \i in the test95, but the last one should be \f. Thanks, Ken Takata -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. diff --git a/src/testdir/test95.in b/src/testdir/test95.in --- a/src/testdir/test95.in +++ b/src/testdir/test95.in @@ -7,7 +7,7 @@ STARTTEST :so small.vim :so mbyte.vim -:set nocp encoding=utf-8 viminfo+=nviminfo +:set nocp encoding=utf-8 viminfo+=nviminfo nomore : tl is a List of Lists with: :regexp pattern :text to test the pattern on @@ -30,10 +30,10 @@ :call add(tl, ['\p\+', '?a', '?a']) : Test recognition of some character classes -:call add(tl, ['\i\+', '*?xx ', 'xx']) -:call add(tl, ['\%#=1\i\+', '*?xx ', 'xx']) +:call add(tl, ['\i\+', '*?xx ', 'xx']) +:call add(tl, ['\%#=1\i\+', '*?xx ', 'xx']) :call add(tl, ['\f\+', '*?fname ', 'fname']) -:call add(tl, ['\%#=1\i\+', '*?fname ', 'fname']) +:call add(tl, ['\%#=1\f\+', '*?fname ', 'fname']) : Combining different tests and features :call add(tl, ['[^[=a=]]\+', 'dda??bcd', 'dd']) diff --git a/src/testdir/test95.ok b/src/testdir/test95.ok --- a/src/testdir/test95.ok +++ b/src/testdir/test95.ok @@ -8,5 +8,5 @@ OK - \i\+ OK - \%#=1\i\+ OK - \f\+ -OK - \%#=1\i\+ +OK - \%#=1\f\+ OK - [^[=a=]]\+
Re: Patch 7.3.1005
On 22/05/2013 08:17 p.m., h_east wrote: Hi, Cesar 2013/5/23(Thu) 8:04:11 UTC+9 Cesar: It doesn't solve the issue for %s/^\n\+/\r. It gets stuck as before. Really? My vim7.3.1005 works well. It appears to have solved for me. Best regards, Hirohito Higashi It doesn't work. It only works with set re=1 I'm using vim 7.3.1005 on Windows 7. Regards, -- Cesar -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: To all syntax file maintainers: examples needed
Hello Bram,
Bram Moolenaar wrote:
The plan is to include a new regexp engine in Vim 7.4. For testing
I would like to get a lot of files for which we have syntax
highlighting. I can then compare the highlighting of these files with
the old and the new engine to find anything that is not compatible.
Makes sense.
Please send me a file that exercises most regexp patterns in the syntax
file. It doesn't need to be long, but it should be a complex example of
the language. Send it as an attachment to avoid the white space being
messed up by the mail system.
OK, even though it's tough...
I would prefer one file per syntax, but it must be valid syntax. If one
file is problematic (e.g., you can't concatenate small files without
making it invalid), then a few files would be OK. A rough goal would be
1000 lines.
I made sample files that have valid syntax with the exception of
some extra */ in order to demonstrate that the commentError
groups are also matched.
As I am the maintainer of uil.vim and prolog.vim, I have attached
a sample file for both syntax files.
You might want to take into account that I have not been using
any of those two languages since I left university, which I did
almost 10 years ago, plus you might want to take into account
that prolog has several dialects which might have subtle
differences, plus I added some code that demonstrates the
highlightning groups, but doesn't make any sense otherwise: asIs
demonstrates that mistyped operators are not being highlighted as
operators (which is no correct prolog syntax). Something similar
holds true for notaNumber.
For uil, I just invented a small example. It uses correct syntax,
but I didn't provide matching .c and .h files to be able to
compile that - I don't even have a Motif development environment
any more ;)
IMPORTANT: I will distribute the collection of files, so that others can
reproduce problems, do performance measurements, etc. Make sure your
file has a copyright that permits this. Don't reveal any secrets,
patents, trademarks, etc. A line stating that the Vim license applies
should be sufficient.
I have just hacked the files together, you can distribute them
together with vim under the same license. I even added this as a
comment at the top of the file. :)
Ciao,
Thomas
--
Thomas Köhler Email: jean-...@picard.franken.de
WWW: http://gott-gehabt.de
IRC: tkoehler Freenode: thkoehler
PGP public key available from Homepage!
/* (C) Thomas Koehler
* distributed under the same license as the vim text editor */
/* a uilComment
* contains = @Spell
* contains = uilTodo: TODO
*/
*/
/* keyword uilType: several keywords:
arguments callbacks color
compound_string controls end
exported file include
module object procedure
user_defined xbitmapfile
*/
! another comment, this time single line, can also contain TODO
#include some/other.uil
#define SMALL /* we can even have comments here, including commentErrors
afterwards */ */ 1
#undef SMALL
module link
names = case_sensitive
procedure
AbbruchCB;
SpeedTypeCB;
object
MainDlg: XmForm
{
arguments
{
XmNx = 123;
XmNy = -123;
XmNwidth = 123.123;
XmNheight = .123;
XmNborderWidth = 1;
};
controls
{
XmLabel VUITa;
XmText ST_Quell;
XmPushButton VUITg;
XmFrame
{
arguments
{
XmNlabelString = 'x'; ! uilCharacter
XmNwidth = 25e;
XmNheight = 25f;
XmNleftAttachment = XmATTACH_FORM;
XmNleftOffset = 8ef;
XmNtopAttachment = XmATTACH_WIDGET;
XmNtopOffset = 6u;
XmNtopWidget = XmLabel VUITa;
XmNrightAttachment = XmATTACH_FORM;
XmNrightOffset = 6UL;
XmNbottomAttachment = XmATTACH_WIDGET;
XmNbottomWidget = XmText ST_Quell;
};
controls
{
XmScrolledList Liste;
};
};
};
};
VUITa: XmLabel
{
arguments
{
XmNlabelString = compound_string(Liste);
XmNleftAttachment = XmATTACH_FORM;
XmNleftOffset = 4l;
XmNtopAttachment = XmATTACH_FORM;
XmNtopOffset = 7U;
};
};
ST_Quell: XmText
{
arguments
{
XmNlabelString = compound_string('String that can contain \123, \x,
\' and \\');
XmNcolumns = 0xDFA;
XmNleftAttachment = XmATTACH_FORM;
XmNleftOffset = 8;
XmNtopAttachment = XmATTACH_NONE;
Re: Patch 7.3.1005
Cesar Romani wrote: On 22/05/2013 08:17 p.m., h_east wrote: Hi, Cesar 2013/5/23(Thu) 8:04:11 UTC+9 Cesar: It doesn't solve the issue for %s/^\n\+/\r. It gets stuck as before. Really? My vim7.3.1005 works well. It appears to have solved for me. Best regards, Hirohito Higashi It doesn't work. It only works with set re=1 I'm using vim 7.3.1005 on Windows 7. Works fine for me too. Please verify you are actually at 7.3.1005, not missing any patch. Do you use Mercurial? It could be a Windows-specific problem or perhaps a 64-bit specific problem. What compiler are you using? What optional features do you build with? -- OLD WOMAN: King of the WHO? ARTHUR:The Britons. OLD WOMAN: Who are the Britons? Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [patch] test95 fails on Windows
Ken Takata wrote: I found some problems in the test95. 1. The test waits a user's input because set nomore is missing. 2. The test fails on Windows because \i matches =A7 (0xa7). The default value of 'isident' is different on Windows. 3. There are three tests using \i in the test95, but the last one should be \f. The attachment arrived in 7 bit encoding. The chantes you made to the non-ASCII characters are missing... -- The future's already arrived - it's just not evenly distributed yet. -- William Gibson /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Pretty ugly bug in the new regex engine
Hi Bram!
On Do, 23 Mai 2013, Bram Moolenaar wrote:
Ron Aaron wrote:
Executing this regex:
s#יְהוָה\Z#\\hashem{}#eg
On this text:
וְיַעֲשׂוּ בְנֵי-יִשְׂרָאֵל אֶת-הַפָּסַח, בְּמוֹעֲדוֹ
Gives this garbage:
\hashem{}\hashem{}\hashem{}\hashem{}\hashem{}\hashem{}\hashem{}\hashem{}
Instead of this :
וְיַעֲשׂוּ בְנֵי־יִשְׂרָאֵל אֶת־הַפָּסַח, בְּמוֹעֲדוֹ
(Attaching this as a file in case the UTF8 is messed up in transit)
A simple search for the pattern appears to match everywhere, compare:
/\%#=0יְהוָה\Z
/\%#=1יְהוָה\Z
That seems to be the same bug, Marc reported:
,
| Multi-byte problem? Marc Weber
| echo matchlist('1', '\%#=1\o{\?Ä\Z')
| echo matchlist('1', '\%#=2\o{\?Ä\Z')
`
which simpler written:
echo matchlist('1', '\%#=1Ä\Z')
echo matchlist('1', '\%#=2Ä\Z')
(sorry, no patch yet)
regards,
Christian
--
Aus Murphy's Gesetze:
Das beste, um beim Schreiben neue Gedanken auszulösen, ist, den Brief
zuzukleben.
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
vim_dev group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Patch 7.3.1005
On 23/05/2013 11:32 a.m., Bram Moolenaar wrote: Cesar Romani wrote: On 22/05/2013 08:17 p.m., h_east wrote: Hi, Cesar 2013/5/23(Thu) 8:04:11 UTC+9 Cesar: It doesn't solve the issue for %s/^\n\+/\r. It gets stuck as before. Really? My vim7.3.1005 works well. It appears to have solved for me. Best regards, Hirohito Higashi It doesn't work. It only works with set re=1 I'm using vim 7.3.1005 on Windows 7. Works fine for me too. Please verify you are actually at 7.3.1005, not missing any patch. Do you use Mercurial? It could be a Windows-specific problem or perhaps a 64-bit specific problem. What compiler are you using? What optional features do you build with? I did a 'make clean' and then after building it again and testing, it worked. Sorry for the noise, Regards, -- Cesar -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Problems of new regexp engine (that we know)
As I've said: having vim read plugin/*.vim files and adding some runtimepath/python-lib dir if it exists to sys.dir would be genious. Then people could use plugin/plugin.py only and have it lazily load its code using import Marc Weber -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Problems of new regexp engine (that we know)
On Thursday, May 23, 2013 12:47:20 PM UTC-5, Bram Moolenaar wrote: Friday is the deadline for new features and larger changes. After that it's bug fixing only! Friday in 8 days, I assume, not Friday tomorrow? -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: To all syntax file maintainers: examples needed
On Saturday, May 11, 2013 6:00:11 PM UTC+2, Bram Moolenaar wrote: The plan is to include a new regexp engine in Vim 7.4. For testing I would like to get a lot of files for which we have syntax highlighting. I can then compare the highlighting of these files with the old and the new engine to find anything that is not compatible. Please send me a file that exercises most regexp patterns in the syntax file. It doesn't need to be long, but it should be a complex example of the language. Send it as an attachment to avoid the white space being messed up by the mail system. I would prefer one file per syntax, but it must be valid syntax. If one file is problematic (e.g., you can't concatenate small files without making it invalid), then a few files would be OK. A rough goal would be 1000 lines. At some later point we might also want to do performance measurements. Although I already have a few bad examples for that. IMPORTANT: I will distribute the collection of files, so that others can reproduce problems, do performance measurements, etc. Make sure your file has a copyright that permits this. Don't reveal any secrets, patents, trademarks, etc. A line stating that the Vim license applies should be sufficient. -- This is the polymorph virus! Follow these instructions carefully: 1. Send this message to everybody you know. 2. Format your harddisk. Thank you for your cooperation in spreading the most powerful virus ever! /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// Here's a post I made on the general mailing list: https://groups.google.com/forum/?fromgroups#!topic/vim_use/QU7mW9RWnLc If you comment out the set regexpengine statement, it breaks the folding entirely. -Rob -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Problems of new regexp engine (that we know)
Ben Fritz wrote: On Thursday, May 23, 2013 12:47:20 PM UTC-5, Bram Moolenaar wrote: Friday is the deadline for new features and larger changes. After that it's bug fixing only! Friday in 8 days, I assume, not Friday tomorrow? Yes, end of May. -- Hanson's Treatment of Time: There are never enough hours in a day, but always too many days before Saturday. /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Plans for Vim 7.4
Thomas Köhler wrote: Hello Bram, hello Ron, Bram Moolenaar wrote: Hello Vim users, [...] Besides that, if you are maintaining runtime files, please send me any pending updates. I will not make big changes just before the release, everything needs some time for testing. Let's set a deadline at the end of May. Attached, you can find a new version of prolog.vim (syntax highlightning for prolog) and koehler.vim (my colorscheme). The former fixes a bug in prologClauseHead higlightning, the later now supports the Underline and Ignore groups. Thanks, I'll include them. -- DENNIS: You can't expect to wield supreme executive power just 'cause some watery tart threw a sword at you! Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
minor doc patches
Hello Bram doc/options.txt *'regexpengine''* *'re'* ^ also: doc/options.txt - *'undofile'* *'udf'* + *'undofile'* *'noundofile'* *'udf'* *'noudf'* -- Regards, Thilo 4096R/0xC70B1A8F 721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Patch 7.3.1006
Patch 7.3.1006
Problem:NFA engine not used for \_[0-9].
Solution: Enable this, fixed in patch 1005.
Files: src/regexp_nfa.c
*** ../vim-7.3.1005/src/regexp_nfa.c2013-05-22 23:00:34.0 +0200
--- src/regexp_nfa.c2013-05-23 22:19:29.0 +0200
***
*** 679,687
/* \_[ is collection plus newline */
if (c == '[')
! /* TODO: make this work
!* goto collection; */
! return FAIL;
/* \_x is character class plus newline */
/*FALLTHROUGH*/
--- 679,685
/* \_[ is collection plus newline */
if (c == '[')
! goto collection;
/* \_x is character class plus newline */
/*FALLTHROUGH*/
***
*** 891,898
}
break;
- /* collection: */
case Magic('['):
/*
* Glue is emitted between several atoms from the [].
* It is either NFA_OR, or NFA_CONCAT.
--- 889,896
}
break;
case Magic('['):
+ collection:
/*
* Glue is emitted between several atoms from the [].
* It is either NFA_OR, or NFA_CONCAT.
*** ../vim-7.3.1005/src/version.c 2013-05-22 23:00:34.0 +0200
--- src/version.c 2013-05-23 22:23:07.0 +0200
***
*** 730,731
--- 730,733
{ /* Add new patch number below this line */
+ /**/
+ 1006,
/**/
--
BLACK KNIGHT: I'm invincible!
ARTHUR: You're a looney.
Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org///
\\\help me help AIDS victims -- http://ICCF-Holland.org///
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
vim_dev group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [PATCH] build fix for Minix 3.2.1
Thomas Cort wrote: Greetings, Attached is a one line fix to get vim to build out of the box on Minix 3.2.1. Patch originally by Gautam Tirumala gautam...@gmail.com Thanks, I'll include it. -- ARTHUR: What are you going to do. bleed on me? Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: minor doc patches
Thilo Six wrote: doc/options.txt *'regexpengine''* *'re'* ^ also: doc/options.txt - *'undofile'* *'udf'* + *'undofile'* *'noundofile'* *'udf'* *'noudf'* Thanks! -- ARTHUR: You are indeed brave Sir knight, but the fight is mine. BLACK KNIGHT: Had enough? ARTHUR: You stupid bastard. You havn't got any arms left. Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Patch 7.3.1007
Patch 7.3.1007
Problem:Can't build on Minix 3.2.1.
Solution: Add a condition to an #ifdef. (Gautam Tirumala)
Files: src/memfile.c
*** ../vim-7.3.1006/src/memfile.c 2013-05-06 04:21:35.0 +0200
--- src/memfile.c 2013-05-23 22:22:22.0 +0200
***
*** 127,133
{
memfile_T *mfp;
off_t size;
! #if defined(STATFS) defined(UNIX) !defined(__QNX__)
# define USE_FSTATFS
struct STATFS stf;
#endif
--- 127,133
{
memfile_T *mfp;
off_t size;
! #if defined(STATFS) defined(UNIX) !defined(__QNX__) !defined(__minix)
# define USE_FSTATFS
struct STATFS stf;
#endif
*** ../vim-7.3.1006/src/version.c 2013-05-23 22:25:10.0 +0200
--- src/version.c 2013-05-23 22:26:16.0 +0200
***
*** 730,731
--- 730,733
{ /* Add new patch number below this line */
+ /**/
+ 1007,
/**/
--
Mrs Abbott: I'm a paediatrician.
Basil: Feet?
Mrs Abbott: Children.
Sybil: Oh, Basil!
Basil: Well, children have feet, don't they? That's how they move
around, my dear. You must take a look next time, it's most
interesting. (Fawlty Towers)
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org///
\\\help me help AIDS victims -- http://ICCF-Holland.org///
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
vim_dev group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Patch 7.3.1008
Patch 7.3.1008
Problem:Test 95 fails on MS-Windows.
Solution: Set 'nomore'. Change \i to \f. Change multi-byte character to
something that is not matching \i. (Ken Takata)
Files: src/testdir/test95.in, src/testdir/test95.ok
*** ../vim-7.3.1007/src/testdir/test95.in 2013-05-21 13:30:17.0
+0200
--- src/testdir/test95.in 2013-05-23 22:36:22.0 +0200
***
*** 30,39
:call add(tl, ['\p\+', 'ìa', 'ìa'])
: Test recognition of some character classes
! :call add(tl, ['\i\+', '*§xx ', 'xx'])
! :call add(tl, ['\%#=1\i\+', '*§xx ', 'xx'])
:call add(tl, ['\f\+', '*Ÿfname ', 'fname'])
! :call add(tl, ['\%#=1\i\+', '*Ÿfname ', 'fname'])
: Combining different tests and features
:call add(tl, ['[^[=a=]]\+', 'ddaãâbcd', 'dd'])
--- 30,39
:call add(tl, ['\p\+', 'ìa', 'ìa'])
: Test recognition of some character classes
! :call add(tl, ['\i\+', '*¨xx ', 'xx'])
! :call add(tl, ['\%#=1\i\+', '*¨xx ', 'xx'])
:call add(tl, ['\f\+', '*Ÿfname ', 'fname'])
! :call add(tl, ['\%#=1\f\+', '*Ÿfname ', 'fname'])
: Combining different tests and features
:call add(tl, ['[^[=a=]]\+', 'ddaãâbcd', 'dd'])
*** ../vim-7.3.1007/src/testdir/test95.ok 2013-05-21 13:30:17.0
+0200
--- src/testdir/test95.ok 2013-05-23 19:34:01.0 +0200
***
*** 8,12
OK - \i\+
OK - \%#=1\i\+
OK - \f\+
! OK - \%#=1\i\+
OK - [^[=a=]]\+
--- 8,12
OK - \i\+
OK - \%#=1\i\+
OK - \f\+
! OK - \%#=1\f\+
OK - [^[=a=]]\+
*** ../vim-7.3.1007/src/version.c 2013-05-23 22:26:50.0 +0200
--- src/version.c 2013-05-23 22:39:37.0 +0200
***
*** 730,731
--- 730,733
{ /* Add new patch number below this line */
+ /**/
+ 1008,
/**/
--
BLACK KNIGHT: The Black Knight always triumphs. Have at you!
ARTHUR takes his last leg off. The BLACK KNIGHT's body lands upright.
BLACK KNIGHT: All right, we'll call it a draw.
Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org///
\\\help me help AIDS victims -- http://ICCF-Holland.org///
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
vim_dev group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [PATCH] Fix compilation failure with Ruby 2.0.0
Ben Fritz wrote: On Tuesday, May 21, 2013 3:01:05 PM UTC-5, Bram Moolenaar wrote: Skeept wrote: Also for the next release, if possible would it be possible to distribute a 64 bit for windows as well a 32 bit? It's not all that useful. It uses more memory, is probably a bit slower. I haven't heard real practical advantages. But perhaps that changed with Windows 8? From http://vim.wikia.com/wiki/Where_to_download_Vim, reasons one might want a 64-bit version: 1. Editing files 4GB in size. Isn't that already possible? It's going to be slow anyway. 2. 64-bit WinPE does not have a WOW64 subsystem, hence you cannot run a 32-bit executable. What is WinPE? 3. Windows Server 2008 R2 (i.e. Win7 Server) also does not have the WOW64 subsystem, by default, although it is an optional component you can install. Not a very common system. 4. Potential for performance gains, particularly in heavy memory operations like memcpy and memcmp which can be optimized for the 64-bit word size. But moving 64 bits things arounds is slower, net gain or loss needs to be measured. 5. Getting 32-bit Vim into a 64-bit Edit with Vim context menu entry is tricky. Also, related to WOW64, accessing native commands which only have a 64-bit version (like chcp) will fail without a workaround. I wonder how many downloads the 64 bit version currently has. -- Any resemblance between the above views and those of my employer, my terminal, or the view out my window are purely coincidental. Any resemblance between the above and my own views is non-deterministic. The question of the existence of views in the absence of anyone to hold them is left as an exercise for the reader. The question of the existence of the reader is left as an exercise for the second god coefficient. (A discussion of non-orthogonal, non-integral polytheism is beyond the scope of this article.) (Ralph Jennings) /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: To all syntax file maintainers: examples needed
Thomas Köhler wrote: Hello Bram, Bram Moolenaar wrote: The plan is to include a new regexp engine in Vim 7.4. For testing I would like to get a lot of files for which we have syntax highlighting. I can then compare the highlighting of these files with the old and the new engine to find anything that is not compatible. Makes sense. Please send me a file that exercises most regexp patterns in the syntax file. It doesn't need to be long, but it should be a complex example of the language. Send it as an attachment to avoid the white space being messed up by the mail system. OK, even though it's tough... I would prefer one file per syntax, but it must be valid syntax. If one file is problematic (e.g., you can't concatenate small files without making it invalid), then a few files would be OK. A rough goal would be 1000 lines. I made sample files that have valid syntax with the exception of some extra */ in order to demonstrate that the commentError groups are also matched. Oh, I meant it should not be garbage. Matching with patterns to highlight errors is also useful in this context. As I am the maintainer of uil.vim and prolog.vim, I have attached a sample file for both syntax files. You might want to take into account that I have not been using any of those two languages since I left university, which I did almost 10 years ago, plus you might want to take into account that prolog has several dialects which might have subtle differences, plus I added some code that demonstrates the highlightning groups, but doesn't make any sense otherwise: asIs demonstrates that mistyped operators are not being highlighted as operators (which is no correct prolog syntax). Something similar holds true for notaNumber. For uil, I just invented a small example. It uses correct syntax, but I didn't provide matching .c and .h files to be able to compile that - I don't even have a Motif development environment any more ;) IMPORTANT: I will distribute the collection of files, so that others can reproduce problems, do performance measurements, etc. Make sure your file has a copyright that permits this. Don't reveal any secrets, patents, trademarks, etc. A line stating that the Vim license applies should be sufficient. I have just hacked the files together, you can distribute them together with vim under the same license. I even added this as a comment at the top of the file. :) Thanks! I'm still finding more errors with newly received files, keep them coming! -- Eye have a spelling checker, it came with my PC; It plainly marks four my revue mistakes I cannot sea. I've run this poem threw it, I'm sure your please to no, It's letter perfect in it's weigh, my checker tolled me sew! /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Patch 7.3.1008
Hi Bram, 2013/05/24 Fri 5:43:25 UTC+9 Bram Moolenaar wrote: Patch 7.3.1008 Problem:Test 95 fails on MS-Windows. Solution: Set 'nomore'. Change \i to \f. Change multi-byte character to something that is not matching \i. (Ken Takata) Files:src/testdir/test95.in, src/testdir/test95.ok The following hunk is missing: diff --git a/src/testdir/test95.in b/src/testdir/test95.in --- a/src/testdir/test95.in +++ b/src/testdir/test95.in @@ -7,7 +7,7 @@ STARTTEST :so small.vim :so mbyte.vim -:set nocp encoding=utf-8 viminfo+=nviminfo +:set nocp encoding=utf-8 viminfo+=nviminfo nomore : tl is a List of Lists with: :regexp pattern :text to test the pattern on Thanks, Ken Takata -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [PATCH] Fix compilation failure with Ruby 2.0.0
2. 64-bit WinPE does not have a WOW64 subsystem, hence you cannot run a 32-bit executable. What is WinPE? Windows Preinstallation Environment http://en.wikipedia.org/wiki/Windows_Preinstallation_Environment http://technet.microsoft.com/en-us/library/hh825110.aspx Basically, a live CD. -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Problems of new regexp engine (that we know)
OK, I'll do it. However I doubt that there are some cases that new regexp engine is slower than original. This change make be possible to work with html file syntax, but re=2 seems to be slower than re=1. On 5/24/13, Bram Moolenaar b...@moolenaar.net wrote: Yasuhiro Matsumoto wrote: Currently, I'm trying to fix \%# \%23c #%23c . https://gist.github.com/mattn/5626661 I'll send a patch in later. I very much appreciate the help. Please also write tests. Lots of bugs slipped through because we don't have sufficient testing. -- DENNIS: Look, strange women lying on their backs in ponds handing out swords ... that's no basis for a system of government. Supreme executive power derives from a mandate from the masses, not from some farcical aquatic ceremony. Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- - Yasuhiro Matsumoto -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Windows doesn't support -f option
On Monday, May 20, 2013 4:37:44 AM UTC-5, Tony Mechelynck wrote: On 20/05/13 05:53, Ben Fritz wrote: Does it matter what is used to compile Vim? I think (but do not know) that the Cream distribution is compiled in MinGW, which I use at home to compile Vim when I'm on Windows. I was under the impression Bram used Visual Studio. IIUC, the Vim without Cream distribution is compiled under Cygwin (using some MinGW version of gcc distributed by Cygwin) but it doesn't need Cygwin to run. Bram uses some MS Visual C/C++ compiler (the same one as comes with Visual Studio, but possibly the free version stripped of what is not needed when compiling in batch mode under make). I finally got Visual Studio Express set up on my machine, and compared an executable built from that with one built from MinGW. Neither one supports -f! Steve, how did you manage to make your Cream builds support -f? I don't need cygwin installed to run Vim, does it depend on some sort of cygwin feature anyway? This would be nice to always have supported! -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
