To setup your computer to work with *.dev domains, e.g. project.dev, awesome.dev and so on, without having to add to your hosts file each time.
- Homebrew
- Mountain Lion
To setup your computer to work with *.dev domains, e.g. project.dev, awesome.dev and so on, without having to add to your hosts file each time.
# Your init script | |
# | |
# Atom will evaluate this file each time a new window is opened. It is run | |
# after packages are loaded/activated and after the previous editor state | |
# has been restored. | |
# | |
# An example hack to make opened Markdown files always be soft wrapped: | |
# | |
# path = require 'path' | |
# |
# Default GitHub user | |
Host github.com | |
HostName github.com | |
User git | |
UseKeychain yes | |
IdentityFile ~/.ssh/id_rsa_github | |
IdentitiesOnly yes | |
Host github.com-rhm | |
HostName github.com |
# @manojampalam - authored initial script | |
# @friism - Fixed issue with invalid SDDL on Set-Acl | |
# @manojampalam - removed ntrights.exe dependency | |
# @bingbing8 - removed secedit.exe dependency | |
$scriptpath = $MyInvocation.MyCommand.Path | |
$scriptdir = Split-Path $scriptpath | |
$sshdpath = Join-Path $scriptdir "sshd.exe" | |
$sshagentpath = Join-Path $scriptdir "ssh-agent.exe" |
It is my opinion that tabs are better than spaces, especially when working in a team. Why you aks? When using tabs everyone has the ability to indent the code according to their own preference. If your teams decides on using spaces you also need to agree on how many spaces to use for an indent. Do you pick 2 spaces, 4 spaces or something else? Odds are, someone is not going to be happy with the team's decision.
Using tabs gives everyone the freedom to indent the code to their own liking. Most editors have an option to specify how many columns a tab should indent. This allows each team member to pick the setting they're most comfortable with.
To prevent (Git) diff nightmares just follow these simple steps:
module.exports = function scaffoldComponent(name) { | |
return `<script setup lang="ts"> | |
export interface Props { | |
//Component props go here. | |
} | |
/* -------------------------------------------------------------------------- */ | |
const emit = defineEmits<{ | |
// component events go here. |