borekb

I currently use ConEmu + zsh via MSYS2 as my preferred shell on Windows. I need to run many interactive programs like `python`, `node` etc. via winpty, e.g.:

``` alias node='winpty node.cmd' ```

With the new ConPTY, will I be able to run native Windows programs directly? If so, that would be huge, winpty (while I'm really thankful it exists) is a PITA in practice, see e.g. https://github.com/Microsoft/vscode/issues/45693.

I'm a happy user of this editor after trying almost everything that's on the market. In v2, the highlights for me are:

- In-place preview like on GitHub (as opposed to side-by-side preview which I find a bit distracting)

- Command palette – Ctrl+Shift+P

- Proportional fonts

- Delete line (tiny thing but I use it a lot in other editors)

- Configurable keyboard shortcuts

Thanks guys for all the work you put in Caret!

Yep :)

There are some important differences between VP and revisr: https://blog.versionpress.net/2015/01/versionpress-vs-revisr...

We're still in the process of solving it but I would be against the rest of the sentence :)

We try to be very clear about the project status. We would love it to be magically stable soon but unfortunately, there are no shortcuts. Relational databases and (sometimes) crazily coded WordPress plugins do not fit well into the version control workflows, but we're already quite far in terms of the core technology and I'm confident WordPress will be a fully versioned platform one day.

Charging for a GPL'd software (all WordPress plugins have to be GPL, at least in practice) is tricky and most companies in the WordPress space focus on services. Which is what we'll do as well. The technology itself, however, will be free and stay free.

Exactly. VersionPress tries to automate that :)

Sorry, docs.versionpress.net had HTTPS issues, should be fine now.

We're not dumping. A comment (and most other changes) is a single text file so commit is fast.

I really liked the first two paragraphs - they put it well.

VersionPress' automatic change tracking means that new commit is created after every logical change to the site, e.g., after you update a post, update a plugin or just about anything. Revisr, if nothing changed recently, only creates commits when you manually say so. That's a difference.

There's been some discussion whether this should be in the core or not. I understand why they chose their current "simplistic" implementation, it has a lot of benefits but we try to go far, far beyond that.

Really? Last time I checked it was manual commits only. Still, the way they track database is very different from how VersionPress does it. But as I said, I'm glad Revisr exists, it is a great tool for certain scenarios.

Deal!

Is that positive or negative? :)

Revisr is a fine plugin and it does many things nicely. However, it is vastly different from VersionPress, as described here:

http://blog.versionpress.net/2015/01/versionpress-vs-revisr/

To be fair many PHP + MySQL CMSses suffer from similar issues. At least WordPress was hackable enough for us to ship as a mere plugin which I think will be important down the road for user adoption.

This is not finalized yet but something we want to support.

Totally possible, we'll probably add that in some future release.

Hi muxxa, rest assured that we know about this and common LAMP hosting support will certainly come. It's just that to implement the support is relatively time consuming and we don't want to promise for v1 something that we know we will be able to deliver. But don't worry, it is our goal to run everywhere where plain WordPress can so common hosting support is coming.

Hi Smudge, please see the answer above. Thanks.

VersionPress is a combination of hooks, own text format and custom PHP code that manages Git and makes it all work together. VersionPress extracts information from the database, stores is in a format that is suitable for diffing and merging and versions that in a Git repository. So we do not version control db files themselves but rather the information inside the database. Sorry if you find the term "database versioning" technically incorrect, we just had to call it something simple that would still be relatively close to the technical truth.

I'll prepare a blog post on how VersionPress attacks the versioning problem technically.

We'll certainly have a way to restore the site even if it is so broken that you can't access the backend. Think something like external command line utility or, for hosting scenarios, a PHP script.

Though we don't promise this for v1, VersionPress on a common LAMP hosting is certainly something we will do in the future and have prototypes of how it could be done. Of course, the end user will be completely abstracted from things you mentioned, it is our mission to provide version control in a way that everyone can use (i.e., if you don't know Git, fine, you don't have to).

Fixed that. Thanks.

Yes, the team scenario is something that we know we want to support and it will totally be possible.

Thanks, that answers many points very well. VersionPress seems to interest many people so hopefully we'll get chance to properly build it.

You also seem to be very realistic about how large this undertaking is - you're right and we know how big of a thing we're trying to build. That's why we're realistic about our goals for v1 and don't promise more than we can deliver. To support all the complex 3rd party plugins and various hosting environments is something that will come over time. But we have to start somewhere and we believe that we are approaching the problem from the right angle. Thanks!

There are certainly big technical challenges to solve, that's why we're running the crowd-funding campaign and that's why we repeat the phrase "realistic funding" quite often. However, although I'm not saying that VersionPress will work in every thinkable scenario and for every WP site out there, we will be able to cover a lot of sites and a lot of needs WP admins have today.

Thanks for your comment!

We will totally version images/albums because we version everything. Glad VersionPress will be useful to you!