I am copy-pasting them.
It's just that the log is written to in the order MaGog identifies changes and it identifies additions before removals.

It works just fine with the capitalization of 'ADDED' and 'REMOVED'; like HypersomniacLive said, sometimes when you skim too fast, you miss bits, so either way is good. I'm just happy you're providing the data!

That's not really a big obstacle.

1. Add a database key which stores a date. (It seems every app of sufficient complexity has an "arbitrary key-value store" auxiliary table)
2. Write a view which shows all entries after that date and embeds the timestamp at which the query was made
3. Add a "mark as read" button which resets the database key to the "queried at" timestamp
4. Use ZeroClipboard to add a "copy to clipboard" button (or put it in a <textarea> and use JS to focus and select all so you just need to Ctrl+C)

You now only see what you need to copy-paste, the non-GOG side of posting updates is just two-clicks, and it becomes trivially easy to sort them however you want.

Depending on your workflow, you could also pin the tab and use Tinycon and a periodic refresh to provide non-distracting-but-visible notification of new updates.

I have obviously been unclear.
The log is a text file.
There is no app, no database, no buttons, no nothing.
Just a text file that is emailed to me by MaGog after every run (i.e. every 6 hours).
And that text file is currently 3-3.5 MB in size per run (i.e. about 30,000 to 35,000 lines).
I'm a simple cat with simple tastes.
The only tool I use to go through the log is vim (vi improved).

Ahh. I assumed you were putting it all into whatever database you use to back MaGog search and then generating reports from that.

Does the code which generates the e-mail report have a structured enough view of the data to sort by game ID and then add/remove status so each dump would be ordered like this?

Game 1, removed file A.zip
Game 1, added file B.zip
Game 2, removed file A.exe
Game 2, removed file B.exe
Game 2, added file C.exe
...

EDIT: If sorts are stable in whatever language you're using, then you can do that with a construct like this.

MaGog doesn't have a database, unless you consider a Perl hash table a form of database.

As for the log file, it is 99% debug information that tells me what MaGog has been doing at every step of its ~65 minute run --- scanning the catalogue, scanning the game pages, scanning the downloadable files, scanning the wiki, checking regional prices, checking regional titles, etc. (very useful for a quick recovery every time GOG changes its formats and breaks something in MaGog, or when MaGog itself has a bug).

The remaining 1% are changes, errors and warnings (all identified by the famous "NOTE!") sparsely interspersed among the debug lines.

Changing the chronological order of lines within the log will make it more difficult to identify breakage when it occurs, hence my hesitancy to sort anything in the file.

I usually copy notes from the log (one or more at a time) in the order I come across them in the log, but I very often paste them in a different order (one that I consider more useful to the readers of that specific post), so my workflow already has "natural" on-the-fly reordering as part of the copy-paste operation. I just need to also reorder the REMOVED and ADDED lines. Zero effort.

Ahh, so like my fanfiction quote randomizer that just loads a gzipped fortune-format text file containing pre-rendered HTML snips, splits it on "\n%\n", and randomly picks an entry to send to the user.

In that case, I'd probably have the system build a second list as it walks through the entries, then add it at the bottom of the e-mail. (I'm the guy who built an analyzer dashboard for his index of gender-bending fiction. The more I can make the machine do for me, the better.)

That is already in the plans, but it always gets delayed by what I consider more useful features, ones that actually offer more data or functionality to the users, rather than just make my life simpler.

Don't tell anyone, but my plan for MaGog ver. 5.0.0 (or 6.0.0 or 7.0.0) is to have a completely automated log generator that will generate the "From Magog's Logs" posts by itself.

Say no more. I know exactly what you mean. :)

Any idea if there is a way to make the dark theme black and not just shades of grey? and the text whiter? I support super contrasty for ease of use :)
Thank you for your tireless change logging services :)

Doing it is trivial enough that I could teach you in an hour or two. The thought and experimentation to do it well is the big time-consuming part.

I've attached an example where I changed the post styling and got unpleasant subpixel-antialising colour fringes to show you what I mean.

Ah yes the super contrast conundrum if done wrong it will make your eyes hurt more... I wonder what causes the sub pixel antialiasing? I'm assuming it has to do with how monitors are made and work. I totally agree perfecting it is where the time commitment would come in. Thank you for sharing your knowledge and trying on my behalf.

It's a feature of modern font rendering systems. Microsoft calls their implementation ClearType.

Not sure when this happened, but Aliens vs. Predator Classic 2000 updated its installer from 2.0.0.25 to 2.0.0.26. Not sure what changed though.