Re: syntax keywords with '[' character

Thank you, that's where I'm going as well. On Sunday, September 3, 2023 at 9:04:47 PM UTC+3 Doug Kearns wrote: > G'day Ron, > > On Sun, 3 Sept 2023 at 22:33, Ron Aaron wrote: > >> I was just given a bug report for a new version of my syntax file, and >> the problem

Re: syntax keywords with '[' character

with the existing code were possible. On Sunday, September 3, 2023 at 5:03:22 PM UTC+3 James McCoy wrote: > On Sun, Sep 03, 2023 at 05:33:22AM -0700, Ron Aaron wrote: > > I was just given a bug report for a new version of my syntax file, and > the > > problem is that a syntax k

Re: syntax keywords with '[' character

Hmm. This works:SQL[[] However, a keyword like exec[] if I try exec[[]] complains about the trailing ] I would have expected syntax keywords to be matched "as is" and not like regexes. On Sunday, September 3, 2023 at 3:33:22 PM UTC+3 Ron Aaron wrote: > I was just given

syntax keywords with '[' character

I was just given a bug report for a new version of my syntax file, and the problem is that a syntax keyword with a lone '[' doesn't work (it causes an error message E789) I have 'syn iskeyword 33-255' (because everything except a space is a valid keyword identifier) but the syntax parser in

Re: Where is Bram?

Yes, RIP Bram -- you were an inspiration as well as being a "mensch". You'll be sorely missed. On Saturday, August 5, 2023 at 5:30:41 PM UTC+3 Yegappan Lakshmanan wrote: > On Sat, Aug 5, 2023 at 5:53 AM Maxim Kim wrote: > > > > https://groups.google.com/g/vim_announce/c/tWahca9zkt4 > > > > I

Re: Any way to make combining characters be separate?

lass I cannot find either, e.g. :s/[\u05b0-\u05c0]/ fails to find it. This seems to be a bug in how combining characters are dealt with. On Tuesday, April 18, 2023 at 5:40:21 PM UTC+3 Ron Aaron wrote: > Hmm. OK, that's not as awkward as using the xxd hack. I'll try it. > > On Sunday,

Re: Any way to make combining characters be separate?

Hmm. OK, that's not as awkward as using the xxd hack. I'll try it. On Sunday, April 16, 2023 at 6:44:31 PM UTC+3 Bram Moolenaar wrote: > > > As a followup to my previous post re delcombine > > , > I'm > > looking for an option

Any way to make combining characters be separate?

As a followup to my previous post re delcombine , I'm looking for an option to display combining characters separately. That is, to treat them as if they were regular characters, in order to make editing them much easier. I

'delcombine' doesn't work as expected

I'm currently on 9.0.1437, and did 'set delcombine'. After 'x' on a character with combining characters, and subsequent 'p', the entire character w/ all its combining characters was pasted. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the

remote_foreground() doesn't work

Running Linux Mint/ Cinnamon desktop/ GTK3 build of vim (9.0.975) For a long time, I noticed that "remote_foreground()" doesn't work to bring that server to the foreground on these systems. remote_expr() does work, so it's not that I don't have the correct server name. My workaround is to get

gvim 9.0.934 not forking GUI sometimes

Recently (last couple weeks) my gvim has stopped reliably forking the GUI on startup. I didn't change any of my configuration, so I'm a bit stumped. Running on Mint 21, Cinnamon desktop. Two different machines, same issue. Launching gvim from within the Konsole terminal. Always in the past the

Re: Cannot compile with +rightleft and +arabic

Thank you, Bram - I don't usually view the newsgroup, which is why I didn't see the discussion around this. I certainly would have jumped in had I noticed it. Best regards, Ron On Wednesday, October 12, 2022 at 12:56:59 PM UTC+3 Bram Moolenaar wrote: > > Ron Aaron wrote: > > >

Re: Cannot compile with +rightleft and +arabic

I, for one, use the rightleft functionality all the time, and I believe many others do as well. It's not perfect, but it works well enough. Getting it yanked out all of a sudden came as a bad surprise. On Sunday, October 9, 2022 at 7:21:42 PM UTC+3 Tony Mechelynck wrote: > On Sun, Oct 9, 2022

Re: [vim/vim] patch 9.0.0696: it is unclear if the +rightleft and +arabic features are used (fbdce18)

I just rebuilt gvim, and to my unhappiness, "--enable-rightleft" does not in fact enable +rightleft. I need that functionality, I've used it for a very long time. Please re-enable it. On Sunday, October 9, 2022 at 11:09:16 PM UTC+3 Yee Cheng Chin wrote: > I think another aspect of this is

Reva ftplugin patch

diff --git a/runtime/ftplugin/reva.vim b/runtime/ftplugin/reva.vim index 05c8bc325..cf90ff82c 100644 --- a/runtime/ftplugin/reva.vim +++ b/runtime/ftplugin/reva.vim @@ -23,3 +23,5 @@ setlocal com=s1:/*,mb:*,ex:*/,:\|,:\\ setlocal fo=tcrqol setlocal matchpairs+=\::; setlocal

8th syntax patches

on: any -" Last Change: 2015/11/08 +" Last Change: 2021/09/20 " Maintainer: Ron Aaron " URL: https://8th-dev.com/ " Filetypes: *.8th @@ -14,12 +14,13 @@ if exists("b:did_8thplugin") finish endif -" Don't load another plugin for this buffe

Re: suppressing 'ansi' control output?

Mi, 24 Mär 2021, Ron Aaron wrote: > > > I want to get the vim version for a bash script. The way I'm trying to > use is: > > > > vim --not-a-term --cmd 'echo v:versionlong|quit' > > > > However, that spews a bunch of ANSI terminal control stuff as well,

Re: suppressing 'ansi' control output?

So what I've come up with is the following, though it seems way too verbose: vim --not-a-term --cmd 'redir! >/tmp/vimver.txt|echon v:versionlong|quit' verlong=`cat /tmp/vimver.text` On Thursday, March 25, 2021 at 7:53:07 AM UTC+2 Ron Aaron wrote: > I want to get the vim version for

suppressing 'ansi' control output?

I want to get the vim version for a bash script. The way I'm trying to use is: vim --not-a-term --cmd 'echo v:versionlong|quit' However, that spews a bunch of ANSI terminal control stuff as well, which I don't want. Is there an option to suppress that output? -- -- You received this message

Re: How to create a syntax keyword at runtime?

s statement > > Although, text properties with external text analyzer might be a good fit > for it. > > понедельник, 14 декабря 2020 г. в 08:04:27 UTC+3, Ron Aaron: > >> I explained exactly what I mean in the original post. >> >> Yes, of course I'm talking about a

Re: How to create a syntax keyword at runtime?

-space as a function declarator. What I can't figure out is how to trap "foo" without trapping the leading colon-space. On Sunday, December 13, 2020 at 5:28:28 PM UTC+2 Charles Campbell wrote: > Ron Aaron wrote: > > Is this possible w/ vim's syntax highlighting? > > > >

Re: How to create a syntax keyword at runtime?

Is this possible w/ vim's syntax highlighting? On Wednesday, December 9, 2020 at 10:56:35 AM UTC+2 Ron Aaron wrote: > Hi all - > > I want to have a keyword (user-defined function) highlighted by my syntax > file. > > The code looks like this: > > : foo blah blah ;

How to create a syntax keyword at runtime?

Hi all - I want to have a keyword (user-defined function) highlighted by my syntax file. The code looks like this: : foo blah blah ; In this case I want "foo" to be scooped up. What I'm doing now is this: syn match colonDef "^\s*:\s\+\zs\S\+" That highlights the correct thing

"state-sensitive" syntax highlighing?

AFAICT, the syntax highlighting engine operates solely by means of regex matches. That's fine as far as it goes, but one of my users has implemented a more useful kind of syntax highlighting in "VSCode" for my "8th" language. Essentially, in 8th (as in most Forths), you can be in either

Re: bitbucket is going to drop Mercurial

I'm also using mercurial to keep my vim up to date. But I could switch to git though I really hate to do that. -- -- 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

Re: Syntax for '8th'

On Thursday, February 7, 2019 at 10:27:42 PM UTC+2, Bram Moolenaar wrote: > Ron Aaron wrote: > > > The attached are ftplugin and syntax files for '8th', a > > Forth-derivative. I'm the maintainer. > > Thanks, I'll include it. And add a line to filetype.vim to det

Syntax for '8th'

The attached are ftplugin and syntax files for '8th', a Forth-derivative. I'm the maintainer. -- -- 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

Is the mercurial mirror not getting updated?

The last patch I see is 944... -- -- 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

Re: Is the mercurial mirror not getting updated?

Thanks. It looks like my mercurial clone was messed up for some reason. -- -- 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

Choosing proper tools

Kudos to Vim (on my use thereof to create "8th"): http://8th-dev.com/forum/index.php/topic,551.0.html -- -- 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

Help with syntax for '8th'

generated by my build process. If anyone has suggestions on what other syntax files I might look at for help, or to offer help, I would appreciate it. For reference, here's the current syntax file: Vim syntax file Language: 8th Version: 1.0.2 Maintainer: Ron Aaron ron at aaron-tech.com

Re: Patch 7.4.309

Thank you! It works fine now. -- -- 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

Buffer position not preserved when resizing window (7.4.307)

To repro the issue: gvim -u NONE somefile :sp 50G Now switch to the second window C-WW And resize it: C-W+ Note that the first window will jump back to line 1 Seen on Linux (Mint 17, 64 bit) -- -- You received this message from the vim_dev maillist. Do not top-post! Type

Spellchecking and typographical quotes

I've been bothered by the spellchecker highlighting as incorrect, words with a typographically correct quotation mark, for example it’s instead of it's. After much gnashing of teeth, I decided to download an updated spell file (from openoffice) and generate a new dictionary. My first attempt

Re: Spellchecking and typographical quotes

On another spell-related issue: is there some reasonable way to tell vim's spell engine to ignore combining characters? In Hebrew, the spellchecker always flags vowelled text as incorrect, which is annoying when I am dealing with large chunks of (correct) vowelled text. I don't see a way to

Re: Spellchecking and typographical quotes

On Wednesday, April 2, 2014 3:09:00 AM UTC+3, James McCoy wrote: Could you provide some text that demonstrates the problem? Sure! Here is the same word, shalom, with and without vowels: שלום שלוֹם the second version is flagged as 'incorrect', but differs in only the vowel-point

end motion at end of word

I see what seems is to me unexpected behavior: If the cursor is on the last character of a word and I do ce, vim changes from the cursor to the end of the next word. I would expect it to stay on the current word. Is this correct behavior, and can it be modified by an option? -- -- You

Re: end motion at end of word

On Friday, March 28, 2014 11:31:28 AM UTC+3, Ron Aaron wrote: I see. I guess I can do ciw to get the behavior I want, but that's three instead of two... oh, well. Or no, that's no good; since by ce I want to change just the end of the word, I guess I have to to cl -- -- You received

Re: end motion at end of word

On Friday, March 28, 2014 11:52:21 AM UTC+3, Matteo Cavalleri wrote: Or no, that's no good; since by ce I want to change just the end of the word, I guess I have to to cl if you're on the last character, an s will be enough Nice, thanks. -- -- You received this message from the

Re: language-mapping is not applied to macro

Thank you, Andy -- that patch does exactly what I want. Bram, will you incorporate it? Thanks! On 08/04/2013 02:15 PM, Andy Wokula wrote: Yes. Old discussion comes up again. Try attached patch. (note ff=dos) (not sure if it can be applied to current sources, but it's very short). It

Re: language-mapping is not applied to macro

On Sunday, August 4, 2013 5:24:44 PM UTC+3, Bram Moolenaar wrote: It has always been that way. When changing this the users who want remapping to work (the ones involved in this discussion) will be happy, and another set of users (who are not yeet involved, since they are currently happy)

Re: language-mapping is not applied to macro

On Friday, August 2, 2013 9:16:41 PM UTC+3, Bram Moolenaar wrote: Ron Aaron wrote: :lmap is only for typed characters. From the help: No, that's not my problem. I'm attaching a file which demonstrates the exact problem, if you do gvim -u test.vim, and then in insert mode type

Re: language-mapping is not applied to macro

On Saturday, August 3, 2013 10:57:29 PM UTC+3, Bram Moolenaar wrote: It appears you expect lmap's to be remappable. If you look at the output of :lmap you can see they are listed with a star, which means they are not remappable. No, I expect that if I map ' to something, then that mapping

Re: language-mapping is not applied to macro

Perhaps this is related to the bug I reported with Hebrew keymap, some imap doesn't work. -- -- 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

insert map doesn't work with remapped keys (keyboard=...)

I have a mapping: inoremap buffer ' 'Esc:call SmartQuote(1)CRa which does the right thing when a single-quote is inserted. That is, it either creates a set of matching typographically correct single-quotes, or it inserts an apostrophe. It works fine in English. When I switch the

Improving vim startup time for very large files

I (and my colleagues) often need to view extremely large log files ( 1G). From force of habit we use vim; but vim takes a very long time to open huge files. Even turning off the swap etc only partially mitigates the load time. I would like to suggest that perhaps vim could be modified to open

Re: imaps don't work with keymap=hebrew

Patchlevel 1270 works great again. thanks! -- -- 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

Re: imaps don't work with keymap=hebrew

On Friday, June 28, 2013 11:03:24 AM UTC+3, ZyX wrote: Alternatively check out that version 7.3.1178 works correctly and 7.3.1179 does not. Indeed, 1178 works and 1182 does not (I don't have 1179 to check with). Thanks! Ron -- -- You received this message from the vim_dev maillist. Do not

imaps don't work with keymap=hebrew

They have always worked before, but in one of the fairly recent builds they stopped working. I have an input map of `h to something. When I have a rl window and keymap=hebrew, that map no longer works. I tried changing the imap to the actual characters entered by the keymap, e.g. ;י ... but

spell problem: E763: Word characters differ between spell files

Recently I've been getting this E763 error when I turn spelllang=he on. It complains about the Hebrew dictionary. Since it didn't use to do this, I wonder why it does now. Using the latest Vim. -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply

Re: With 'spellang=en,he' and 'complete+=kspell', completion often hangs

C'mon, Bram, is that the best you can suggest? Don't use that spell file? What is it that makes it unusably slow, and how can I work around it? Is the problem the affix stuff? -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are

Re: With 'spellang=en,he' and 'complete+=kspell', completion often hangs

On Saturday, June 15, 2013 10:54:37 PM UTC+3, Bram Moolenaar wrote: The completion works by generating a dump of all valid words. This Hmmm. Isn't there a way to generate a list of only words beginning with a certain prefix? After all, complete generally means you have some text written

With 'spellang=en,he' and 'complete+=kspell', completion often hangs

I don't know if the problem is having two dictionaries or specifically with the Hebrew dictionary, but if I have an English text and press Ctrl-N to complete a word, I get an initial display of matches and then Vim freezes up with a searching... message on the status line. If I change

Re: With 'spellang=en,he' and 'complete+=kspell', completion often hangs

0x0811c8db in utf_ptr2char (p=0xbfffef24 ילוציי) at mbyte.c:1704 1704return ((p[0] 0x1f) 6) + (p[1] 0x3f); (gdb) bt #0 0x0811c8db in utf_ptr2char (p=0xbfffef24 ילוציי) at mbyte.c:1704 #1 0x0811ccb8 in utf_composinglike (p1=0xbfffef22 אילוציי, p2=0xbfffef24 ילוציי) at

Re: Regexp engine work

Maybe wrap it a bit: if has(profile) fun! SynTime(eng) syn clear set re=a:eng edit! syntime on redraw! redraw! redraw! redraw! syntime report syntime off endfun command! -nargs=0 SynTime : call SynTime(1) | call SynTime(2) endif

Re: Regexp engine work

After actually using it, this is better (e.g. it works) if has(profile) let g:syntime_report='' fun! SynTime(eng) syn clear exe 'set re='.a:eng edit! syntime on redraw! redraw! redraw! redraw! redir = g:syntime_report echom Engine

Re: Patch 7.3.1117

In file included from regexp.c:7875:0: regexp_nfa.c: In function ‘nfa_regatom’: regexp_nfa.c:983:5: error: ‘e_missing_sb’ undeclared (first use in this function) -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For

Crash on vim startup

Compiling with ./configure CFLAGS='-g' and then gdb src/vim, I get a crash right at startup do to buffer overflow: #4 0xb7644105 in __GI___fortify_fail (msg=0xb76a3648 buffer overflow detected) at fortify_fail.c:38 #5 0xb7642eba in __GI___chk_fail () at chk_fail.c:29 #6 0xb76421ed in

Re: Crash on vim startup

On Wednesday, June 5, 2013 9:36:00 PM UTC+3, Tony Mechelynck wrote: Which patchlevel? 7.3.1121 Which OS? 32 bit Linux Which featureset {Tiny|Small|Normal|Big|Huge}? Whatever the default is (presumably Normal) -- -- You received this message from the vim_dev maillist. Do not

Re: Crash on vim startup

Which patchlevel? 7.3.1121 Retested w. 1124, same result -- -- 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

Another regexp bug : \

The help says: Note that using \ works the same as using \@=: foo\.. is the same as \(foo\)\@=... But using \ is easier, you don't need the braces. However, if you look for foo\, it only matches f and not foo. Tried with both re=1 and re=2. -- -- You received this

Re: Another regexp bug : \

Aha. OK, I thought it would match foo like the \@= does (e.g. that highlights the foo). The help is not clear, then. On Tuesday, June 4, 2013 3:48:54 PM UTC+3, Andy Wokula wrote: Not a bug -- it matches where foo matches with zero width (f is highlighted but not matched). -- -- You

Re: Patch 7.3.1110

it doesn't appear yet on the ftp site -- -- 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

Re: Patch 7.3.1110

Er, but all the patches up until this last have appeared on the ftp site. I thought that was the canonical patch place. On 06/04/2013 05:26 PM, Bram Moolenaar wrote: Ron Aaron wrote: it doesn't appear yet on the ftp site I thought everybody was using the Mercurial repository. I'll push

Re: Patch 7.3.1110

and applies them. This would be a bit more tedious to do using mercurial (though not impossible). On 06/04/2013 06:32 PM, Bram Moolenaar wrote: Ron Aaron wrote: Er, but all the patches up until this last have appeared on the ftp site. I thought that was the canonical patch place. Recently

Re: Another regexp bug : \

On Tuesday, June 4, 2013 11:30:09 PM UTC+3, ZyX wrote: `\(foo\)\@=` highlights f and matches zero-width as expected. If on your system it does something else it is a bug. Once again, the help states: Note that using \ works the same as using \@=: foo\.. is the same as

Re: Another regexp bug : \

On Wednesday, June 5, 2013 6:58:22 AM UTC+3, ZyX wrote: Ah, I missed these dots. But still the OP says that with those two dots `foo` is highlighted and not `fo`. No, I also missed the two dots! I compared foo\ with \(foo\)\@=. So, never mind, I guess... -- -- You received this message

Curiosity in the NFA code

I'm sure there's a reason, but I wonder: why, in regexp_nfa.c nfa_recognize_char_class(), is the config using chars instead of integer bitmaps? I would expect bitmaps to be faster (as well as taking less space). -- -- You received this message from the vim_dev maillist. Do not top-post!

Re: Matching decomposable Unicode characters

On Friday, May 31, 2013 12:27:21 PM UTC+3, Bram Moolenaar wrote: I find it a bit annoying that Unicode has two forms for the same character. They should have made a choice to either use a base character plus composing characters, or the combined form. Now we need to solve this in software

Re: Matching decomposable Unicode characters

I think there should be an option (probably an option, not a regex flag) which controls whether or not the engine finds ff (unicode 0xfb00) when searching for f, for example. It seems to me that most people may not need it, but those of us who frequently edit multilingual or other rich texts,

Re: Matching decomposable Unicode characters

On Friday, May 31, 2013 1:56:56 PM UTC+3, Mike Williams wrote: On 31/05/2013 11:23, Ron Aaron wrote: ff is a ligature, not a composed character. Although it has a decomposed form it cannot be recomposed with Unicode composing rules (f is not a composing character) There are others including

Re: Matching decomposable Unicode characters

On Friday, May 31, 2013 2:02:27 PM UTC+3, Christian Brabandt wrote: Wouldn't it be enough, if we enhance the equivalence classes a bit? I have posted a patch, which enhances the equivalence classes a while ago. It didn't include U+FB00, but I think, we could easily add the missing chars.

Re: Matching decomposable Unicode characters

On Friday, May 31, 2013 4:39:14 PM UTC+3, Mike Williams wrote: Alas I have zero knowledge of Hebrew so will have to bow to your superior knowledge. You will know better the use case of finding base characters with and without combining marks. Thanks, I guess... There are no ligatures in

Re: Matching decomposable Unicode characters

On Friday, May 31, 2013 4:29:04 PM UTC+3, LCD 47 wrote: Thanks for the links It is indeed a can of worms, but we need to live with it in some reasonable manner. -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For

Re: People with too much time on their hands

Heh :) I didn't bother trying to investigate it much, just thought it was a pretty funny idea. -- -- 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

Matching decomposable Unicode characters

I was puzzled when searching for this in some Hebrew text: /ארבע\Z/ That it did not match this: אַרְבָּעָה As it happens, the אַ is Unicode combined form of the aleph plus the vowel patah. There are two issues: 1) First, is that the normal user would expect a match here, since the

People with too much time on their hands

But this is really cool anyway: http://vim-adventures.com/ -- -- 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

Proposal: plugin manager

. 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. *_Plugin.txt* Manage plugins Author: Ron Aaron r...@ronware.org License: Same terms as Vim itself (see

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 : וְיַעֲשׂוּ בְנֵי־יִשְׂרָאֵל אֶת־הַפָּסַח,

Re: Patch 7.3.988

Timing using: time gvim -f --cmd 'set re=1' -c ':qa!' 0.285s with 're=2' or 're=0' 0.494s -- -- 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

Re: Patch 7.3.988

Did you measure this before patch 988? Patch 989 may also help a little bit. Just rechecked with all patches through 989, the results are similar (this on 32-bit; the other was 64-bit) -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the

Calling Sureshkumar Manimuthu ...

I'm trying to contact Sureshkumar Manimuthu, who authored the vimgdb tool. The email address he gave there seems to be inactive now. Does anyone have contact information for him? Thanks! -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the

Re: Patch 7.3.973

On 05/20/2013 02:34 PM, Bram Moolenaar wrote: The line numbers don't exist. The different types are the same. Is your compiler broken? Or did you duplicate code? Probably a compile problem, I'll check it out later. Like I said, it compiles fine at work. -- -- You received this message

Re: Patch 7.3.970

On Monday, May 20, 2013 2:34:14 PM UTC+3, Bram Moolenaar wrote: So the new engine is faster? Or what do the numbers mean? My experience is that the new engine is slower. Thus we have work to do to make it faster. Just doing gvim --startuptime a.txt with regexpengine=0 and ...

Re: Patch 7.3.973

Yeah, it works fine after I did a clean-clean build at home. Probably a patching problem on my part. -- -- 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 ---

Re: Plans for Vim 7.4

I know it's late to vote, but some sort of sane 'gdb' integration would be supremely useful. I haven't found any packages for this that don't involve a lot of setup. -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying

Re: Patch 7.3.970

Crashes for me: (gdb) bt #0 0xb7fdd424 in __kernel_vsyscall () #1 0xb75391df in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #2 0xb753c825 in __GI_abort () at abort.c:91 #3 0xb757639a in __libc_message (do_abort=2, fmt=0xb766e6c7 *** %s ***: %s terminated\n) at

Re: Patch 7.3.970

Don't know if it makes a difference, but I compile big version, for GTK2 with CFLAGS of -O3 -s -march=native -msse4.2 Only patch 970 causes the crash. -- -- 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

Re: Patch 7.3.973

Arrgh. This one doesn't even compile for me: regexp_nfa.c:11010:3: warning: passing argument 3 of ‘addstate’ from incompatible pointer type [enabled by default] regexp_nfa.c:10088:1: note: expected ‘struct regsub_T *’ but argument is of type ‘struct regsub_T *’ regexp_nfa.c:11018:3: warning:

Re: Patch 7.3.973

Bizarrely, it compiles fine at work. Both are Mint 14, but the one at work is 64bit and the one at home is 32bit. Maybe I misapplied the patch at home, I'll have to take a look this evening. -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below

Re: Plans for Vim 7.4

On Thursday, May 9, 2013 6:51:48 AM UTC+3, Bram Moolenaar wrote: don't want to find out what happens if we go over that, so it's time for Vim 7.4! That's very exciting! 2. add integration with Python instead of inventing more Vim script I hope this doesn't mean Python will be *required*.

Re: Plans for Vim 7.4

On Thursday, May 9, 2013 6:51:48 AM UTC+3, Bram Moolenaar wrote: Hello Vim users, ... so it's time for Vim 7.4! Wonderful news! 2. add integration with Python instead of inventing more Vim script I hope this doesn't mean Python will be required, that would be a badness. -- -- You

Re: patch for viminfo crashing

On 04/21/2013 02:07 PM, Bram Moolenaar wrote: Do you have an idea of when the crash happens? Does it depend on your 'viminfo' setting perhaps? I get the crash when I quit vim (if I had a viminfo file already), and also when switching 'projects' (like sessions, with more information). My

Re: Patch 7.3.905

I didn't try to figure that out; but yes, I do have explicit ':wviminfo' in my autocommands for 'on exit'. On 04/16/2013 02:03 PM, Bram Moolenaar wrote: Ron Aaron wrote: Thank you, this patch works fine. Glad to hear. Did you see where the two calls to write_viminfo_history() come from? I

Re: Patch 7.3.903

Same place. The viminfo_history has zeroes: (gdb) l 6228if (i = 0) 6229while (num_saved 0 6230 !(round == 2 i = viminfo_hisidx[type])) 6231{ 6232p = round == 1 ? history[type][i].hisstr

Re: Patch 7.3.903

Perhaps a stack trace will help. Or setting a breakpoint at write_viminfo_history() and stepping through it. And check that finish_viminfo_history() isn't called. You did include the change in ex_cmds.c, right? I verified manually that the patch contents of 7.3.903 were applied;

Re: Patch 7.3.905

Thank you, this patch works fine. -- -- 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

Re: Patch 7.3.718

None of the patches since 7.3.715 are on the ftp site... -- 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

sessions and window/buffer local variables

I'm in a situation where saving the values of window-local variables would be useful. It seems that sessionoptions does not have an option for window/buffer local variables saving. It would be nice to generalize the 'globals' so that a local window/buffer variable like b:Saveme would be

Replace multibyte combining characters does not work as expected

Given this text (the character sequence is 200d 05b9): ‍ֹ The command: s/\%u200d\Z/x/g Gives the result: x‍ֹ (0078 200d 05b9) I would expect the 200d to be replaced with an 'x'. (I attached the text so you can see it in vim a bit more clearly) -- You received this message from the

  1   2   >