Get a subscription to https://cooking.nytimes.com/. I know it sounds crazy to pay for recipes when there are so many free cooking websites and youtube channels, but everything is tested and the instructions are clear for beginning cooks. There are whole sections for weeknight meals, chicken, pasta, vegetarian, etc. And thousands of recipes in the database so you'll never run out. Source: 10 months ago

From there I'll go to America's Test Kitchen, NYTimes Cooking, and Milk Street. Milk Street is the (relatively) new project from Chris Kimball, who used to head ATK and has more of a focus on everyday cooking and international cuisine and has produces a few gems for me (and is also an absolutely excellent place to buy supplies and tools). All three have the same basic issue of seeming vaguely bland to my palate... Source: 12 months ago

NY Times cooking — Another subscription service, but you can create a free account. Also, try refreshing the page and spamming the ESC key on PC right before the prompt to log-in pops up. They have some very famous recipes, including one for chocolate chip cookies (seriously, make this one!), no-knead bread, and many others. Source: about 1 year ago

NY Times cooking — Another subscription service, but you can create a free account. Also, try refreshing the page and spamming the ESC key on PC right before the prompt to log-in pops up. They have some very famous recipes, including one for chocolate chip cookies (seriously, make this one!), no-knead bread, and many others. Source: over 1 year ago

Add Simply Recipes and New York Times Cooking (although with that one, you only get a certain number of recipes for free each month, then you have to pay.) I do pay for New York Times because I found myself using their recipes so often that I was running out of free ones each month. They publish really good, solid recipes. Source: over 1 year ago

There's a guide on the subreddit wiki on how to format code for display on reddit. When in doubt, you can also use GitHub Gist or Hastebin, though. Source: over 2 years ago

In future, use code formatting or put your code into hastebin.com and then post a link here. It will make it easier to read. Source: over 2 years ago

If you want to post a log, you'll have to generate one first (go to settings > logging and set both logging verbosities to 0-debug and 'log to file' to ON, then do whatever you need to do to create the offending behavior; that should make the log. Then, open the resulting log in a text editor and copy/paste the contents somewhere like hastebin.com and post a link to it here). Source: over 2 years ago

Close RetroArch, then navigate to your 'logs' folder in your RetroArch user directory (if you can't find it, open RetroArch and go to settings > directory and see where your 'logs' directory is located). You should see a text file there. Copy/paste its contents somewhere like hastebin.com and then post a link to it here and I/we can take a look. Source: over 2 years ago

Can you give me the entire command history that got you to where you are now? If you can do that, make sure there is not personal information in the history, especially passwords. Look at the output of history. If it's large, try hastebin.com . Source: over 2 years ago