We had a regression in the 0.68.0 release and I debated whether it was critical enough to release a 0.68.1 to fix it. The defect isn't major but it's in a common enough feature ('*' and '#') that a lot of people have noticed it. Given that Eclipse Neon was just released, I'm guessing a lot of people will be re-installing the current stable build of Vrapper with it. I figured it's best to have a solid release for those people. So here's a quick release with a couple issues we've fixed in the last month. They are:... read more
I was able to find some time this month to work on new Vrapper features, including some plugin requests that have been sitting around for a while. Of course, this project is so mature now that we're looking at the more obscure features in Vim but all of these were requested by users filing Issues on our GitHub page. We hope you continue to enjoy Vrapper!
*search wasn't using iskeyword value to determine word boundaries
( )and text object
swhen sentence ends on a newline
%to jump between block comment
\%Vin command-line substitutions and search for limiting to visually selected area
\kregex class for iskeyword value
:subwordmappingswill setup default mappings:
This new release of Vrapper is pretty sizable. We received some great help in the form of Pull Requests. Thank you to all our users and contributors keeping this project going!
This new release of Vrapper only has a couple defect fixes but they're important fixes. One defect could create an infinite re-paint loop (crashing Eclipse) and another broke Vrapper in older (< 3.7) versions of Eclipse. Both of those defects are fixed!
Time for another Vrapper release. Some great progress was made in the last two months fixing older defects that have been around for a while. There was also a lot of general refactoring to cleanup the code and fix certain little annoyances. Hope everyone enjoys this new release!
It's been another two months so I'm releasing our current changes. Development is still moving slowly, but it's moving forward. Albertdev did a bunch of refactoring to clean up some code under the hood. The work wasn't related to any specific defect but a lot of the commands should be more stable. Here are the changes I can describe:
It's been a bit of a slow month for us. There weren't many changes but it's been two months so I might as well do another release. Here are the changes since my last update
:s//wouldn't clear previous search
Here's your monthly status update on recent changes to Vrapper's unstable update site:
Another two months, another Vrapper release. We've now received over 50,000 installs via the Eclipse Marketplace, which puts us at number 42 out of all 1,800+ plugins available in the Marketplace. Thank you everyone who continues to use and support Vrapper!
We now have over 60 issues on our GitHub repository but I noticed something recently: there are only 11 defects. Of course, since I'm the one who labels these items there are another 10 "annoyances", which are items that don't really prevent you from doing anything but would be nice to have. The reason I bring this up is because we have 35 feature requests. Once again, it seems like Vrapper is at the point where we can meet the majority of user's use cases and we're down to the really obscure and difficult features that only power users even know exist. Also, I don't think we have any feature requests which have a "me too!" comment in them; I think all of our feature requests each have one person waiting on them. I may be a little biased, but I think Vrapper is one of the best Vim emulation plugins for any text editor. I'm not aware of any other Vim emulator that has support for additional (ported) vimscript plugins. I think we're doing pretty good!... read more
I'm still sticking with our monthly status updates. Here are the changes which are currently on our unstable update site:
I just released 0.52.0 a couple days ago but a number of people quickly hit the same problem. Certain command-line commands (such as :w and any mappings to an :eclipseaction) caused the editor to lose focus. This meant you had to click your mouse within the editor to regain focus. As Vim users, we all know how frustrating it is when your hands have to leave the keyboard to use the mouse. So we fixed this issue and released 0.52.1 as quickly as we could. We apologize for any inconvenience.... read more
While December was extremely slow for us, we did have some code changes in January so I'm sticking with our two-month release cycle and releasing 0.52.0 today. The following changes are in 0.52.0:
It's been a month since 0.50.0 was released so I figured I should stick with my monthly status updates and tell you about the recent changes. However, there is nothing to report. Since 0.50.0 was released there hasn't been a single line of code changed and there hasn't been a single defect filed. December is usually a slow month for us anyway, but I'm surprised we haven't had any defects filed either. I guess 0.50.0 must be a rock-solid release (or you guys must all be busy during December too).... read more
0.50.0 has been released, continuing with our two-month release cycle. At this point, I think I've been fully relegated to Project Manager status as albertdev has stepped up and handled basically all development in this release. He's much better at this than I am and Vrapper is stronger for it. I'll take credit for resurrecting this project when the original authors abandoned it, but albertdev is the one who is able to fix the really difficult defects and introduce tough new features. Thank you albertdev for your amazing work!... read more
It's been another month, time for your monthly status update with Vrapper. We've made the following changes on the unstable update site:
Vrapper version 0.48.0 has been released, back on schedule with our two-month release cycle. The only changes since the last news post were more esoteric bug fixes. The following fixes are included in 0.48.0:
Time for another monthly status update on Vrapper. For the last couple years, our GitHub Issues page has hovered around 30 open defects/feature requests. Defects have been filed and fixed and we always seemed to have about 30 open at any given time. This last month brought with it what I'm going to call some "overzealous" new users. We jumped from having ~30 defects to having over 50 in one month. 13 of those issues were filed by a single person. Now, I don't take this as a sign that Vrapper is unstable. I may be overly optimistic here, but I think it's actually because Vrapper has reached a point where we meet about 95% of most users' use cases. We're down to the esoteric features and nit-picking defects; which is to say, the really hard stuff. Just take a look at the current changes on our unstable update site:... read more
If I was sticking closely to my two-month release cycle I would've released last week. However, there weren't too many changes in this release. I also had just fixed a defect and I wanted to make sure my fix solved the problem. Now, a week later, I'm releasing 0.46.0. Here are the changes since the last news post (included in 0.46.0):
Another month, another status update for Vrapper. In the past month, we've made the following changes to the unstable update site:
It seems we're still sticking with this 2-month release cycle. 0.44.0 has been released and is primarily a bug-fix release with a ton of defects fixed. In addition to last month's list of fixes, 0.44.0 includes the following changes:
Time for your monthly status update on Vrapper. We've got another long list of changes in the last month since 0.42.0 was released.
First of all, there was a defect in 0.42.0 where the '?' command (reverse search) simply didn't work. I was tempted to release a 0.42.1 with this defect fixed since it seems like such a fundamental feature. However, it actually took a couple weeks for anyone to find it. This tells me that the '?' feature isn't actually used that often. So we've fixed this defect on the unstable update site but I think it can probably wait for 0.44.0 to be in a stable release. If you actually use the '?' feature a lot and noticed it was broken, you'll have to update to the latest unstable build or wait another month to receive the fix. Sorry for breaking such a basic feature.... read more
It seems springtime brought some new life for Vrapper development after such a slow winter. 0.42.0 has been released and just look at the list of changes made in the last month (included in 0.42.0):
It's been another slow month but I might as well give an update with the changes to the unstable update site since 0.40.0 released:
0.40.0 has been released. This release is smaller than most but I'm keeping with my two-month release cycle one more time. The following changes were added since the last status update and are included in 0.40.0:
As I mentioned in my last post, real life has been getting in the way of me spending time with Vrapper. The holidays certainly didn't help things either. This was a slow month for Vrapper but here's your monthly status update. The following changes have been made to the unstable update site: