This follows the default git diff + less behaviour. So small diffs are printed directly, while larger diffs stay in less interactively. This annoys me a little. What do you think about that? Worth coming up with a solution for? @Jguer

I'll check it out. Would you prefer to always go to less or that they should be always printed directly?

I would like it to always go to less, but then piping manually is more annoying and less wont display colour without the -R flag.

Git uses -F/--quit-if-one-screen by default for less. If you export your own less flags LESS=RSX then that overrides this and less will always show. I'll consider this problem solved.

There's another problem with empty diffs but that should be an easy fix.

I changed the UX a little, I'd say I'm happy with it. Setting LESS=RX makes it perfect. Maybe that should go into the FAQ.

@Morganamilo after I check the diff of an upgrade package how would I go about editing that PKGBUILD?

You'd have to open the file in your editor yourself or use --noshowdiffs. This is why I had the diffs always show the full file paths. I don't know how important editing is to you. I always saw it as viewing but you also happened to be in an editor.

I thought It would be tedious to have edit and diff prompts at the same time. Maybe you can think of something that works.

Requires more work:
We could menu it, NONE (default) , DIFF, EDIT

Less work:
If you don't care for the diff then you also don't care to edit. So only ask to EDIT if you DIFFED it

For me the less work option works

Thinking about it, Would probably work to replace the Would you like to continue with the install Y/n dialog with something along the lines of continue, abort, go back and edit.

Yes maybe it would work, I'll try and think of designs over that as welll