Useful for using seting up Latex workshop for VSCode on Macs.
brew install basictex latexindentStep 1. Download the latest version from here: https://www.nongnu.org/chktex/, & un(g)zip it
Useful for using seting up Latex workshop for VSCode on Macs.
brew install basictex latexindentStep 1. Download the latest version from here: https://www.nongnu.org/chktex/, & un(g)zip it
| #!/bin/bash | |
| # First parameter is the sub-directory-absolute-path | |
| # Second parameter is the link of the repo | |
| # A smart split to get the repo-name, with / as a separator | |
| REPO_NAME="$(echo $2 | grep -oE '[^/]+$')" | |
| git init $REPO_NAME | |
| cd $REPO_NAME |
Note
If you want to use pure WSLg, you can try the new WSLg (XWayland) tutorial or the WSLg (Wayland) tutorial.
In this tutorial, we will setup GUI in WSL2, and access it using VNC. No additional software outside WSL (like VcXsrv) is required, except, of course, a VNC Viewer (RealVNC, TightVNC, TigerVNC, UVNC, etc, all of them might work flawlessly).
The key component we need to install is the desktop metapackage you want (GNOME, KDE, Xfce, Budgie, etc) and tigervnc-standalone-server.
For this setup, I will use Ubuntu (20.04, 22.04 and 24.04 are working), and install GNOME Desktop. Since the key components aren't bound to Ubuntu or GNOME, you can use your favorite distro and GUI. Check the [Sample
| xquery version "3.1"; | |
| (: | |
| # Save eXide editor tabs to disk | |
| 1. Install "LocalStorage Manager" Chrome extension | |
| https://chrome.google.com/webstore/detail/localstorage-manager/fkhoimdhngkiicbjobkinobjkoefhkap |
| var transientErrors = new HashSet<WebExceptionStatus>(new[] | |
| { | |
| WebExceptionStatus.ConnectFailure, | |
| WebExceptionStatus.ConnectionClosed, | |
| WebExceptionStatus.KeepAliveFailure, | |
| WebExceptionStatus.Pending, | |
| WebExceptionStatus.PipelineFailure, | |
| WebExceptionStatus.ProtocolError, | |
| WebExceptionStatus.ReceiveFailure, | |
| WebExceptionStatus.RequestCanceled, |
| import React, { memo, useCallback } from 'react'; | |
| import ChildComponent from './wherever/ChildComponent.js'; | |
| const updateChild = (props, childId, changes) => { | |
| props.onUpdate({ | |
| type: 'childChanged', | |
| childId: childId, | |
| changes: changes, | |
| }); | |
| }; |
| 'use strict'; | |
| /** | |
| * Person class. | |
| * | |
| * @constructor | |
| * @param {String} name - name of a person. | |
| * @param {Number} age - age of a person. | |
| * @param {String} gender - gender of a person. | |
| */ |
| using System; | |
| using Moq; | |
| using Refit; | |
| using Xunit; | |
| namespace Some.Kind.Of.Space | |
| { | |
| [Collection("Feature Name")] | |
| [Trait("Feature Aspect", "Classification")] | |
| public class FeatureClassNameTests |
| $cscode = @" | |
| using System; | |
| using System.Net.Http; | |
| using System.Net.Security; | |
| using System.Security.Cryptography; | |
| using System.Security.Cryptography.X509Certificates; | |
| using System.Text; | |
| public class My { |
How to setup a development environment where Git from WSL integrates with native Windows applications, using the Windows home folder as the WSL home and using Git from WSL for all tools.
Note if using Git for Windows, or any tool on the Windows side that does not use Git from WSL then there will likely be problems with file permissions if using those files from inside WSL.
These are the tools I use:
wslgit)