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.