I have the following problem: while experimenting with vim macros in Pycharm (I'm using Idea Vim plugin) - I typed a simple macro and make an editor to run it 100 times. The execution is extremely slow and I couldn't stop it using any of these pieces of advice. Has anyone had a similar problem and knows how to stop the execution of this macro?
It's not possible in the current IdeaVim 0.50. Feel free to file an issue in the IdeaVim issue tracker.
Related
I'm a vim/ultisnips newbie trying to be more efficient when writing and coding. I've successfully installed the ultisnips plugin and it works so far.
My question is: is it possible to "reactivate" a snippet after it has been filled? The documentation says:
UltiSnips will only map the jump triggers while a snippet is active to
interfere as little as possible with other mappings.
But actually I would like to reactivate a snippet from time to time in order to efficiently jump between the placeholders while updating/modifying the snippet content.
Any idea how this can be done?
Though one: whenever I run a test with R# using a hotkey (CTRL+U, CTRL+R), the runner window get focus. It's ruining my performance.
Does anyone have any clue as to what I did to cause that? IIRC, this wasn't so until yesterday.
I have not worked out how to stop this from happening, but the following shortcuts do help:
Ctrl+Tab (Navigate between files opened in the editor, and tool windows.)
Shift+Esc (Close current tool/window.)
I have used Stata and gVim on Windows for a while now. Recently I have switched to Linux, and I am planning to also change from Stata to R.
A friend of mine is using R and Emacs ESS which seems to work perfect, however i'd rather like to keep using vim. I have installed the vim-r-plugin2, however, i can only send code to a seperate terminal running R. I would much rather split my screen into a buffer running R and one buffer with my .R file, and then send code from one to the other. With ESS in Emacs this seems to work, you can run a terminal/R in a buffer without a problem. I haven't found a way to make this work. The R plugin for vim uses screen, and the only way to open a buffer running a shell I could find is the Conque Shell plugin.
I know that unlike Emacs, Vim is designed to be a simple text editor. However, having R run in a buffer seems just so much more practical.
I hope my problem is understandable, please bear with me I only recently switched to Linux and know virtually nothing about programming besides statistics. Thanks!
If you do not need to input unicode, you can consider using ConqueShell plugin.
In the meanwhile, the 'evil' (extensible vi emulation layer) mode has matured. This is a vim emulator running in Emacs and works quite well for me.
Another option, and forgive me for pointing you back to EMACS,
viper-mode
http://www.informatik.uni-hamburg.de/RZ/software/emacs/viper/viper_3.html
It's an EMACS mode that makes EMACS feel more like Vim, while giving you full access to the wonderful, mind-boggling complexity of EMACS if you ever want it.
I'm not sure if this question should be done in the superusers, but anyway, lets give it a try.
Here is my problem.. I'm running ubuntu 9.10 and I'm tying to create a development environment with Vim and it's plugins.
I've done everything that I needed, but I'm having some issues with the snippets:
When I'm in a model and I press:
bt<TAB>
I got:
belongs_to :<+association_name+><+, :class_name => "<+Object+>", :foreign_key => "<+<+object+>_id+>"+>
But if I start typing, instead of replace the association_name with what I type, it just place the text after the line.
Anyone know what could be happening?
Thanks.
not sure which plugin you're using but snipMate has a much easier config/syntax for creating and using snippets within vim,
http://www.vim.org/scripts/script.php?script_id=2540
While surfing, I came to know that somebody has done Tower of Hanoi using vim. WOW!!!
Can you people share what all cool things you have been doing in vim.
Edit: Not sure about the Tower of Hanoi solution using vim being all that useful. But I think this question should be re-opened to allow people to comment on any useful things that they've done using vim. For me? See my answer below. (-:
vim has a set of commands that integrate with development tools such as make, gcc, and ctags. You can build your project, navigate to warnings and errors, and jump to function/variable definitions without leaving the editor:
:make builds the project.
:cl lists warnings and errors.
:cc takes you to the to line in the source code that generated the current error.
:cn navigates to the next error.
:cp navigates to the previous error.
:tag name navigates to the definition of the token name. (See man ctags to generate an index of tokens; sometimes make tags will do this automatically.)
Pressing Ctrl+] navigates to the definition of the token under the cursor.
I'm using vim to syntax-color code in my blog and lecture notes. A single Perl line
system "$vimrt\\gvim.exe", qq{
-c "edit /tmp/tmpcode.$ext "
-c "source $vimrt/syntax/2html.vim"
-c "write! /tmp/tmpcode.html"
-c "qa!"};
converts the code into nicely-colored HTML. I know there are stand-alone tools for doing this, but vim is already installed on my system, so this is one less tool to install.
I found myself struggling to be more efficient in vim compared to other non-modal text editors until I learned about "text-objects". Understanding this concept really improved my productivity and also gave me a new way of looking at text which in turn made it easier to deeply understand other vim concepts that I had only understood ephemerally before.
:help text-objects
I was working on a system that had massive log files. We're talking 30,000 10MB logs.
Per day!
Distinguishing between log messages that were coming from the middleware (same company but custom rolled) and our application was getting tedious.
That is until I wrote some custom vim syntax parsing so that anything vim displayed in green was from the middleware (done by the guys in Sophia Antipolis near Cannes) as opposed to anything vim displayed in blue that was from our application software that sat over the top of the SA code.
I also added highlighting to really make exceptions stand out with white lettering on a read background!
Made life so much easier! And it wasn't that hard to do!
Thanks vim!
I couple of months ago I wrote a vim script to save a complete history of all my edits, so I could inspect and measure my programming performance.
I'm using vim a lot recently to edit XML files. I got the xmledit plugin for vim working. Now vim creates closing tags for me, I can enclose highlighted text in an XML tag, and jump to balancing XML tags. It saves a lot of repetitive typing, reduces mistakes, and increases my productivity.