Jeremy Gonyea

How will backwards compatibility of Grav 1plugins/ themes be handled in Grav 2? Wordpress tries pretty hard to be backwards compatible across major versions, while Drupal typically requires a rewrite...

Drupal has a batch api to break up large requests into multiple smaller ones to avoid timeout/ memory issues. It'd be nice to see a similar system in Grav.

I think this is fixed now. The link now points to v1.4.1 (as of 2018-03-12)

This can be closed. The link is pointing to the correct release. -Last checked 20190929

I think many of the portable applications do this (I know Portable Firefox and Notepad++ do this). This check may be present to prevent accidental contamination of user data between...

I would also love to see this on the official lists on portableapps.com. Thanks again for bundling this editor, @garethflowers!

To do what you're looking for, you'll need to edit the GitPortable/App/Appinfo/Launcher/GitBashPortable.ini file ``` [Environment] HOME=%PAL:DataDir%\home PORTABLE_DRIVE=%PAL:Drive% ```

Typically, anything in the App folder will get overwritten on upgrading via a *.paf.exe What are you trying to accomplish?

The closest I could get was to create an executable bash wrapper at `/usr/local/bin/phpcs` with the following: ``` #!/bin/sh export PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin docker run --rm --user $(id -u):$(id -g) --volume $(pwd):/project...

I do the same thing with phpcbf (create a executable bash wrapper at `/usr/local/bin/phpcbf` with the following content): ``` #!/bin/sh export PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin docker run --rm --user $(id -u):$(id -g) --volume...