- Clone your repo.
curl -L https://github.com/Aldaviva/webscale/pull/3.patch | git am -3- If there are merge conflicts, fix them, then
git am --continue. - Make any local changes you want.
git add -A- Commit your changes with
Closes #3at the end of the commit message.git commit --amend(to modify the pull request commit)git commit(to add a new commit of you own).
- If you want to squash multiple WIP commits into one, use
git rebase -i origin/master. - Push.
| #!/bin/bash | |
| PLATFORM=Mac | |
| function main { | |
| if [ "$1" == "repin" ] | |
| then | |
| update | |
| elif [ "$1" == "install" ] | |
| then |
By increasing the maximum width of tabs and taskbar buttons, you can
- see more of their text labels without truncation,
- have a larger hit area for your mouse pointer, and
- make better use of the space on your wide monitor.
This does not break the resizing logic when you open more tabs, so the worst-case scenario behavior is unchanged. For example, you could set the maximum tab width to a size at least as wide as your monitor. Then, when you have one tab open, it will consume 100% of the available space. Next, when you open another tab, they will each consume 50% of the available space. When the minimum tab width is reached, the existing overflow or scrolling logic will still apply.
This Gist has been elevated to the Github repository Aldaviva/VivaldiCustomResources because it's easier to deal with that way.
VivaldiCustomLauncher 1.1.5 uses the new repo to download resources.
This gist was moved to a GitHub repository to make it easier to diff changes and keep in sync with a clone on a filesystem.
| final long start = System.nanoTime(); | |
| // operation being timed | |
| LOGGER.trace("Operation took {} ms", (System.nanoTime() - start) / 1_000_000); |
PowerShell Remoting allows you to connect to a remote shell on another Windows computer.
The server is the Windows computer that will host the shell, and that you will connect to. The client is the Windows computer that will create the connection, on which you will see and interact with the shell.
These steps assume a workgroup with Windows 10 or Server 2016 or later on the server, and Windows 7 or later on the client. It assumes that the client is running with a user account that also exists on the server with the same password. Neither the server nor the client need to be joined to a domain or using Kerberos.