-
Open Conemu
-
Open Settings -> Tasks or go to new tab button -> Setup tasks.
-
Click
+to add a new task -
Enter the name as
Git Bashor whatever you like -
Task parameters:
/icon "C:\Program Files (x86)\Git\etc\git.ico" /dir "C:\_git" -
Command:
| gulp.task("install", function(cb) { | |
| var npm = require("npm"); | |
| npmConfig = {}; | |
| // sample command line opts, you may have others | |
| if (gUtil.env["npm-cache-path"]) npmConfig.cache = gUtil.env["npm-cache-path"]; | |
| if (gUtil.env["npm-log-level"]) npmConfig.loglevel = gUtil.env["npm-log-level"]; | |
| npm.load(npmConfig, function (er) { | |
| if (er) return cb(er); | |
| npm.commands.install([], function (er, data) { cb(er); }); |
If you're using Browserify and Reactify to write React components and build them for the browser, you may, depending on your setup, see errors along the lines of "unexpected token <", which means that your code is not getting Reactified properly. You will either see this in Gulp, because some subsequent step in the pipeline can't parse your code, or in the browser.
Here's how browserify decides how to apply transforms:
- Anything specified when you actually call browserify (i.e. in a gulpfile or on the command line) will be run first. Calls here can specify {global: true}, which will make them be applied to dependencies as well as code in the current module.
- If there is a browserify.transform key in package.json, it can list transforms which should be applied, in the order that they should be applied.
You need to specify reactify before anything else which is going to want to parse the code, because obvs. it isn't valid es5 until it's been reactified (so e.g. having `["browserify-shim", "reactify"
| (defn episode-number [file] | |
| (def match (re-matches | |
| #"\d{4}-\d{2}-\d{2} - (S\d\d E\d\d) - .*" | |
| (.getName file))) | |
| (if (= match nil) | |
| nil | |
| (match 1))) | |
| (def episodes (partition-by episode-number files)) |
- Don't.
- Close Visual Studio and don't open it again until I tell you. Visual Studio is not competent at renaming things.
- Assuming you're using git, clean the working folder to remove anything that's not in version control (this will help the search-and-replace step because it won't have to go through a bunch of generated files)
git clean -fdx
1️⃣
🐦🍐🌳
2️⃣
🐢🐦 🐢🐦
🐦🍐🌳
| // What is the console output of this code? | |
| function switchFoo (foo) { | |
| switch (foo) { | |
| case 1: | |
| foo = 5 | |
| console.log(foo) | |
| case 2: { | |
| console.log(foo) | |
| break |
| Windows Registry Editor Version 5.00 | |
| [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\WindowsStore] | |
| "RemoveWindowsStore"=dword:00000000 | |
You need to run Chrome with two command line flags:
--disable-web-security --user-data-dir
These are kind of documented here: https://peter.sh/experiments/chromium-command-line-switches/
--disable-web-security is the one that turns off the same-origin policy (the name is scarier than the action). Although the docs don't say this, this flag is ignored unless you also specify --user-data-dir. That's because --disable-web-security can be super risky so you shouldn't be surfing in that mode all the time, so Chrome requires you to use an alternative user profile, specified with --user-data-dir. However, you can get away with just giving --user-data-dir and not specifying a dir, and it will use the default one (so you get all your bookmarks, cookies, extension, etc. but --disable-web-security will still feel that honour has been satisfied and tuirn off same-origin policy.
If you start getting shitty fucking error messages like
manpath: can't set the locale; make sure $LC_* and $LANG are correct
whenever you start up a WSL shell, your system locales are all fucked to insane buggery and you need to unfuck them pronto.
You can do this by running the official locale-unfucking command: