pasting text: bug?
This behaviour is not consistent but it happens often. When editing something like this: title test - 5 May 2013/title I copy a line, delete the text in between the title tag and paste the copied line there instead. The result is sometime normal, but at other times the new text is pasted before the title tag, rather than in between the tags. Is this normal? P -- -- You received this message from the vim_mac 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_mac group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_mac+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Macvim slow with set list and Unicode listchars
On Wed, Mar 13, 2013 at 11:16 PM, Kevin Burke wrote: I've been investigating a problem with Unicode listchars. My .vimrc looks like: show line endings set list set listchars=tab:▸\ ,eol:¬ When I open a file containing many tab characters, Macvim is extremely slow to scroll - holding down j yields a key repeat rate of about once per second. If I turn off list: set nolist Or, use a different tab listchar: set listchars=tab:+\ ,eol Scrolling suddenly becomes very fast. I have pushed a fix for this now. It was caused by a font lookup API call which for some reason is super-slow on Mountain Lion whereas on Snow Leopard it was fast. (That is also why I couldn't reproduce to begin with.) Björn -- -- You received this message from the vim_mac 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_mac group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_mac+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: MacVim as (a kind of) Framework
On Tue, Jun 4, 2013 at 9:29 PM, Tae Won Ha wrote: Hi. About a month ago, I started to factor out a framework part from MacVim: https://github.com/qvacua/macvim I now can build a MacVim app which consists of two parts: a Vim framework (with vim+runtime and supporting classes like MMVimView) and an app which uses that framework. There are two new targets: - MacVimFramework: This is the framework. - MacVimWithFramework: This is a copy of the MacVim target which uses the above framework. The binary can be found here: https://www.dropbox.com/s/hpczl4fo2zxg4zh/MacVimWithFramework.app.zip It's compiled on 10.8 and I hope that it works on other machines, too. (It works on my machine, ;-) There are yet many rough edges though, for example: - You cannot call the framework a real framework yet: it's just a collection of classes that can be compiled in a separate framework target. - Sometimes I just blindly refactored, not really having carefully read the whole code or having thought about whether it's a sensible separation of code. Well, just get it done first and then refactor again, I'd say... - The framework uses PSMTabBarControl, ie it expects the client-app to include it. - Things can be in a broken state, eg all new windows have a fixed hard-coded size... However, I think/hope that it can serve as a base for a real MacVim-framework. I'll try to consolidate the code base further and start to think about how to make it a real and easy to use framework. Best, Tae PS. I'm sorry that I ignored the usual formatting of the code. PPS. I started to migrate the code to ARC; well, at least for two small files. I don't have much to say other than have fun hacking away on this. Unfortunately, getting things to compile as a framework is the easy part -- how to deal with the fact that Vim is an application and not just a view will require more thought (I have no good solution, and I've spent some time thinking on this). Björn -- -- You received this message from the vim_mac 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_mac group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_mac+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Compiler warning extravaganza on Tiger PPC
Here on Tiger PPC I updated to 7.3.1148. Here is a new compiler warning I haven't seen yet; it occurred during the plain Vim portion of building MacVim. In file included from regexp.c:7891: regexp_nfa.c: In function ‘post2nfa’: regexp_nfa.c:2754: warning: ‘end_state’ may be used uninitialized in this function regexp_nfa.c:2753: warning: ‘start_state’ may be used uninitialized in this function regexp_nfa.c: In function ‘addstate’: regexp_nfa.c:3378: warning: ‘save_lpos.col’ may be used uninitialized in this function regexp_nfa.c:3378: warning: ‘save_lpos.lnum’ may be used uninitialized in this function regexp_nfa.c:3380: warning: ‘save_ptr’ may be used uninitialized in this function regexp_nfa.c: In function ‘nfa_regmatch’: regexp_nfa.c:4363: warning: ‘add_off’ may be used uninitialized in this function Then later, during the Mac-specific portion of building MacVim, I saw these warnings (also never seen until 7.3.1148): /Developer/usr/bin/gcc-4.0 -x objective-c -arch ppc -pipe -Wno-trigraphs -fobjc-exceptions -fpascal-strings -fasm-blocks -Os -Wreturn-type -Wunused-variable -fmessage-length=0 -mtune=G5 -fvisibility=hidden -I/macvim/src/MacVim/build/MacVim.build/Release/MacVim.build/MacVim.hmap -mdynamic-no-pic -F/macvim/src/MacVim/build/Release -F/macvim/src/MacVim -I/macvim/src/MacVim/build/Release/include -I/macvim/src/MacVim/build/MacVim.build/Release/MacVim.build/DerivedSources -c /macvim/src/MacVim/MMTextView.m -o /macvim/src/MacVim/build/MacVim.build/Release/MacVim.build/Objects-normal/ppc/MMTextView.o /macvim/src/MacVim/MMTextView.m: In function ‘-[MMTextView checkImState]’: /macvim/src/MacVim/MMTextView.m:322: warning: ‘MMTextViewHelper’ may not respond to ‘-checkImState’ /macvim/src/MacVim/MMTextView.m:322: warning: (Messages without a matching method signature /macvim/src/MacVim/MMTextView.m:322: warning: will be assumed to return ‘id’ and accept /macvim/src/MacVim/MMTextView.m:322: warning: ‘...’ as arguments.) And here too: /Developer/usr/bin/gcc-4.0 -x objective-c -arch ppc -pipe -Wno-trigraphs -fobjc-exceptions -fpascal-strings -fasm-blocks -Os -Wreturn-type -Wunused-variable -fmessage-length=0 -mtune=G5 -fvisibility=hidden -I/macvim/src/MacVim/build/MacVim.build/Release/MacVim.build/MacVim.hmap -mdynamic-no-pic -F/macvim/src/MacVim/build/Release -F/macvim/src/MacVim -I/macvim/src/MacVim/build/Release/include -I/macvim/src/MacVim/build/MacVim.build/Release/MacVim.build/DerivedSources -c /macvim/src/MacVim/MMAtsuiTextView.m -o /macvim/src/MacVim/build/MacVim.build/Release/MacVim.build/Objects-normal/ppc/MMAtsuiTextView.o /macvim/src/MacVim/MMAtsuiTextView.m: In function ‘-[MMAtsuiTextView checkImState]’: /macvim/src/MacVim/MMAtsuiTextView.m:376: warning: ‘MMTextViewHelper’ may not respond to ‘-checkImState’ /macvim/src/MacVim/MMAtsuiTextView.m:376: warning: (Messages without a matching method signature /macvim/src/MacVim/MMAtsuiTextView.m:376: warning: will be assumed to return ‘id’ and accept /macvim/src/MacVim/MMAtsuiTextView.m:376: warning: ‘...’ as arguments.) Finally, here are some compiler warnings from the plain Vim portion that seem to have been around for ages on Tiger PPC (especially the latter): gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MACVIM -Wall -Wno-unknown-pragmas -pipe -DMACOS_X_UNIX -no-cpp-precomp -g -O -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/eval.o eval.c eval.c: In function ‘get_lval’: eval.c:2729: warning: ‘prevval’ may be used uninitialized in this function and, gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MACVIM -Wall -Wno-unknown-pragmas -pipe -DMACOS_X_UNIX -no-cpp-precomp -g -O -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/search.o search.c search.c: In function ‘current_search’: search.c:4521: warning: ‘save_VIsual.coladd’ may be used uninitialized in this function search.c:4521: warning: ‘save_VIsual.col’ may be used uninitialized in this function search.c:4521: warning: ‘save_VIsual.lnum’ may be used uninitialized in this function I now see that all of those compiler warnings exist on 10.5.8 PPC also. -gmn -- -- You received this message from the vim_mac 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_mac group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_mac+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Compiler warning extravaganza on Tiger PPC
dv1445 wrote: Here on Tiger PPC I updated to 7.3.1148. Here is a new compiler warning I haven't seen yet; it occurred during the plain Vim portion of building MacVim. In file included from regexp.c:7891: regexp_nfa.c: In function ‘post2nfa’: regexp_nfa.c:2754: warning: ‘end_state’ may be used uninitialized in this function regexp_nfa.c:2753: warning: ‘start_state’ may be used uninitialized in this function I think I can fix these. regexp_nfa.c: In function ‘addstate’: regexp_nfa.c:3378: warning: ‘save_lpos.col’ may be used uninitialized in this function regexp_nfa.c:3378: warning: ‘save_lpos.lnum’ may be used uninitialized in this function regexp_nfa.c:3380: warning: ‘save_ptr’ may be used uninitialized in this function Can't fix these without adding overhead. regexp_nfa.c: In function ‘nfa_regmatch’: regexp_nfa.c:4363: warning: ‘add_off’ may be used uninitialized in this function I can fix this one. Finally, here are some compiler warnings from the plain Vim portion that seem to have been around for ages on Tiger PPC (especially the latter): gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MACVIM -Wall -Wno-unknown-pragmas -pipe -DMACOS_X_UNIX -no-cpp-precomp -g -O -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/eval.o eval.c eval.c: In function ‘get_lval’: eval.c:2729: warning: ‘prevval’ may be used uninitialized in this function Can be fixed at a small price. gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MACVIM -Wall -Wno-unknown-pragmas -pipe -DMACOS_X_UNIX -no-cpp-precomp -g -O -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/search.o search.c search.c: In function ‘current_search’: search.c:4521: warning: ‘save_VIsual.coladd’ may be used uninitialized in this function search.c:4521: warning: ‘save_VIsual.col’ may be used uninitialized in this function search.c:4521: warning: ‘save_VIsual.lnum’ may be used uninitialized in this function Not so easy to fix. -- hundred-and-one symptoms of being an internet addict: 125. You begin to wonder how often it REALLY is necessary to get up and shower or bathe. /// 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_mac 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_mac group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_mac+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: pasting text: bug?
OK, that makes a lot of sense now. Thanks for clarifying. Best, Peiman *www.peimankhosravi.co.uk* || Subscribe to RSS Feedhttp://peimankhosravi.co.uk/miscposts.rss *To receive emails about upcoming concerts visit this pagehttp://spectralkimia.wordpress.com/ enter your email address in the 'follow' section. * On 9 June 2013 15:34, björn bjorn.winck...@gmail.com wrote: On Sun, Jun 9, 2013 at 1:22 PM, peiman khosravi wrote: This behaviour is not consistent but it happens often. When editing something like this: title test - 5 May 2013/title I copy a line, delete the text in between the title tag and paste the copied line there instead. The result is sometime normal, but at other times the new text is pasted before the title tag, rather than in between the tags. Is this normal? If you select a line with a newline character, then Vim will paste *above* the cursor. If there is no newline character in the selection then it pastes *at* the cursor. It is a feature, not a bug, I'm afraid. Björn -- -- You received this message from the vim_mac 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_mac group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_mac+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message from the vim_mac 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_mac group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_mac+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
