ematysek

Setting up RetroArch on Raspberry Pi 4 and building emulator cores

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:

• This gist showing the basic steps for building and configuring for raspberry pi 3. I'm new to Raspberry Pi and RetroArch myself so this was super helpful and I recommend looking through it.
  https://gist.github.com/AlexMax/32e5d038a66ce57253e740ea75736805
• This Reddit post showing the performanc gains over the pi 3b+

felixqueisler

{
  "alfredtheme" : {
    "result" : {
      "textSpacing" : 5,
      "subtext" : {
        "size" : 10,
        "colorSelected" : "#FEFFFEC4",
        "font" : "System",
        "color" : "#C6C6C665"
      },

mmzsource

My environment

• emacs 26.3
• cider 0.25.0
• leiningen 2.9.4 on Java 11.0.2
• ~/.lein/profiles.clj : {:user {:plugins []}}

Project setup

In a terminal, run these commands:

briangordon

*****************************************************************************************************************************

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.

fauxpark

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

romainl

The right way to override any highlighting if you don't want to edit the colorscheme file directly

Generalities first

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.

kn9ts

GPL3 LICENSE SYNOPSIS

TL;DR* Here's what the license entails:

1. Anyone can copy, modify and distribute this software.
2. You have to include the license and copyright notice with each and every distribution.
3. You can use this software privately.
4. You can use this software for commercial purposes.
5. If you dare build your business solely from this code, you risk open-sourcing the whole code base.

streetturtle

#!/bin/bash

#
# This is sp, the command-line Spotify controller. It talks to a running
# instance of the Spotify Linux client over dbus, providing an interface not
# unlike mpc.
#
# Put differently, it allows you to control Spotify without leaving the comfort
# of your command line, and without a custom client or Premium subscription.
#

jfmengels

lodash v4.17.20

Array

• _.chunk
• _.compact
• _.concat

t-mart

Map	Action
<F1>	Causes Netrw to issue help
<cr>	Netrw will enter the directory or read the file
<del>	Netrw will attempt to remove the file/directory
-	Makes Netrw go up one directory
a	Toggles between normal display, hiding (suppress display of files matching g:netrw_list_hide) showing (display only files which match g:netrw_list_hide)
c	Make browsing directory the current directory
C	Setting the editing window
d	Make a directory