Skip to main content

Timeline for Issue with using ex commands

Current License: CC BY-SA 3.0

7 events
when toggle format what by license comment
Jun 23, 2017 at 13:49 history bounty ended Tyberius
Jun 22, 2017 at 9:36 comment added B Layer @Tyberius :wv/rv make a lot of sense and I had high hopes to get the two-liner to work...but no luck. The register is just not read from viminfo with the second command so the put to file2 just complains about empty register. My one liner works great for me, though. Maybe you should focus on getting that to work. BTW, if you leave off the 'q' command you will still be in ex and you'll be able to easily read any. errors/messages, examine registers, etc.
Jun 21, 2017 at 19:27 comment added B Layer Do you mean file2? BTW, I just noticed the :wv and :rv commands. Maybe these can be used with the two-command use case. Check out :help viminfo-read-write. (Sorry I'm in a hurry...can't try it out myself until later.)
Jun 21, 2017 at 14:54 comment added Tyberius @BlairM. I gave this method a try and ran into the same problem; it seems to run, but then there is no change to the file1.
Jun 20, 2017 at 0:17 comment added B Layer Before I answered I wondered if that was the case but when I tried it it did not work. The text does not get copied to the second file. For that matter it wasn't in my .viminfo file either. Thus I assumed it wasn't correct and answered with the single-command version. Maybe OP would be better off going that direction since at least two of us have issues with the two command approach. :)
Jun 19, 2017 at 15:31 comment added Tumbler41 Vim saves away registers in the .viminfo file. So the unnamed register is actually saved between instances.
Jun 18, 2017 at 8:45 history answered B Layer CC BY-SA 3.0