jmau111

Well, don't play on Linux

Trust me, it's full of bugs and a little bit limited. Don't get me wrong, I love this game and it's very cool that we can actually play this on Linux. But at the end of the day the gaming experience is not great on Linux.

WITH THIS METHOD YOU WON'T LOSE YOUR PROGRESSION. This is really important cause this game is fun but takes a lot of time, especially if you want to reach the highest levels. I mean you have to spend a ridiculous amount of time to get all the quests and stuffs no matter what you do and even with some skills and speed run.

Why ?

jmau111

nautilus `pwd`

jmau111

Because we love Prism but it does not work AS IS when in a React context.

import Prism from 'prismjs';

class MyComponents extends Component {
  componentDidMount() {
    Prism.highlightAll();

jmau111

Open ~/.bashrc :

sudo nano ~/.bashrc

and insert :

jmau111

1. Go here and download your archive (depending on your operating system)
2. extract the folder e.g at the root of your path "~/"
3. open terminal and enter :

cd ~/kindlegen

then you can run :

kindlegen /PATH/TO/youEpub.epub

jmau111

<?php
add_action( 'wp_enqueue_scripts', 'jmau_remove_noto_from_frontend' );
function jmau_remove_noto_from_frontend() {
	global $wp_styles;
	$wp_styles->remove( 'wp-editor-font' );
}

jmau111

<?php

/**
 * Replace "text-domain" with your text domain, it's just the i18n load part
 */
class Gutenberg_i18n_Example {

	public function hooks() {
		add_action( 'enqueue_block_editor_assets', [ $this, 'scripts_register' ] );
		add_action( 'enqueue_block_assets', [ $this, 'scripts_enqueue' ] );

jmau111

import {select} from '@wordpress/data';
let featuredImageId = select('core/editor').getEditedPostAttribute('featured_media');
let media = select('core').getMedia(featuredImageId);
console.log(media);

jmau111

In case you have this stupid error. Google leads you to the following :

1. maybe you tried this stackoverflow OWNERSHIP documentation
2. maybe you tried this stackoverflow CONFIG Override
3. hopefully you did not try the "uninstall / install" thing even if it's often recommanded as a "good" solution... which is not and cannot be.

Of course this can solve your case (except 3.) and I'm not saying this gist is the ultimate solution but that might be something related to a config file that just disapeared (this never happens so you probably made some mistake by copy/pasting commands).

In my case there was a problem in the /etc/systemd/system/docker.service.d folder. You have to have a file called `docker.c

jmau111

sudo chown -R $USER:$GROUP ~/.npm && sudo chown -R $USER:$GROUP ~/.config