Suppose you have weird taste and you absolutely want:
- your visual selection to always have a green background and black foreground,
- your active statusline to always have a white background and red foreground,
- your very own deep blue background.
Suppose you have weird taste and you absolutely want:
diff --git a/builddefs/common_features.mk b/builddefs/common_features.mk | |
index 18f8b0bbfc..4ef3e230e4 100644 | |
--- a/builddefs/common_features.mk | |
+++ b/builddefs/common_features.mk | |
@@ -878,6 +878,10 @@ ifeq ($(strip $(JOYSTICK_ENABLE)), yes) | |
endif | |
endif | |
+ifeq ($(strip $(APPLE_FN_ENABLE)), yes) | |
+ OPT_DEFS += -DAPPLE_FN_ENABLE |
***************************************************************************************************************************** | |
Introduction | |
The code review workflow that I prefer is to check out a feature branch, then `reset --soft` to move the branch HEAD to | |
just before the changes. That way I still have all of the changes in my working copy, and those exact changes are staged | |
for commit. My IDE will highlight the changed lines right in the editor and let me click the gutter to view a quick diff. | |
This is incredibly useful. But problems arise when develop has been merged into a running PR, bringing along a whole bunch | |
of other unrelated changes that have already been reviewed. I don't want all of those other changes to be highlighted in | |
my IDE, but I do want them in my working copy. |
{ | |
"alfredtheme" : { | |
"result" : { | |
"textSpacing" : 5, | |
"subtext" : { | |
"size" : 10, | |
"colorSelected" : "#FEFFFEC4", | |
"font" : "System", | |
"color" : "#C6C6C665" | |
}, |
Guide for myself and others to get RetroArch running on the new Raspberry Pi 4 while projects like RetroPie get an image out for the rpi4.
Disclaimer: I am not an expert and this may not be the most optimal build possible, but it works.
Inspiration taken from: