Add a simple extended error message (#4646) by christianbender · Pull Request #5568 · processing/processing

Hi @christianbender - I see you created another regex. My suggest was rather to modify this one so that it would work with whatever is going on with 23) also.

If you look here you see that your pull requests still has some random changes that come with it, like commented-out println() statements. My git tricks, in the hope that they are useful for you also: I stage changes with git add -p, where I am being asked block by block whether I want to commit this particular change to the next commit [y] or not [n].

When I learn that I made a mistake in a previous commit I fix with git rebase -i HEAD~1. This lets you mark the commits you want to edit by placing an "e" at the beginning of each line. Now you can make retroactive changes to this commit, add them to be committed, and commit with git commit --amend, which picks up the commit message you already wrote. (This also works with more then just the recent commit, by changing HEAD~1 to HEAD~2 and so on.) And lastly, you can also use git rebase to "squash" (merge) different commits into one. This works by placing an "s" of the beginning of the line for the commits that you want to merge with its predecessor (also works with multiple). This way you can have one, logical commit at the end of a process of trial and error - instead of a spew of commits that do and undo various things. Note: whenever you rewrite history (this is what git rebase does), you need to push your changes to GitHub using git push -f - by default GitHub doesn't like history to be rewritten (it's indeed not a good practice, except for pull-requests branches, so before they are in a tree that other people might depend on).