Learn how to send emails through Gmail SMTP with Cloudflare Email Routing in this comprehensive guide.
To proceed with this method, ensure that you have enabled two-factor authentication for your Google account. If you haven't done so already, you can follow the link to set it up → Enable 2FA in your Google account.
Inspired by dannyfritz/commit-message-emoji
See also gitmoji.
| Commit type | Emoji |
|---|---|
| Initial commit | 🎉 :tada: |
| Version tag | 🔖 :bookmark: |
| New feature | ✨ :sparkles: |
| Bugfix | 🐛 :bug: |
| [ | |
| { | |
| "city": "Ada", | |
| "zip": 24430, | |
| "county": "Severnobanatski okrug", | |
| "belongsTo": "Ada" | |
| }, | |
| { | |
| "city": "Adaševci", | |
| "zip": 22244, |
1.) Download a Nerd Font
2.) Unzip and copy to ~/.fonts
3.) Run the command fc-cache -fv to manually rebuild the font cache
| <!-- | |
| When an input element gets focused, iOS Safari tries to put it in the center by scrolling (and zooming.) | |
| Zooming can be easily disabled using a meta tag, but the scrolling hasn't been quite easy. | |
| The main quirk (I think) is that iOS Safari changes viewport when scrolling; i.e., toolbars shrink. | |
| Since the viewport _should_ change, it thinks the input _will_ move, so it _should_ scroll, always. | |
| Even times when it doesn't need to scroll—the input is fixed, all we need is the keyboard— | |
| the window always scrolls _up and down_ resulting in some janky animation. | |
| However, iOS Safari doesn't scroll when the input **has opacity of 0 or is completely clipped.** |
| # dotNetDave's (David McCarter) Editor Config - dotNetTips.com | |
| # Updates to this file are posted quarterly at: https://bit.ly/EditorConfig5 | |
| # Updated February 14, 2024 | |
| # dotNetDave's NEW coding standards book is available at: https://bit.ly/CodingStandards8 | |
| # Rockin' the Code World with dotNetDave (weekly live show): https://bit.ly/RockinCodeWorldShows | |
| root = true | |
| # All Files | |
| [*] |
A regular expression, often abbreviated as regex, is a sequence of characters that serves as a pattern for searching within a string. It is widely employed to locate specific patterns, substitute characters, or validate input strings. This tutorial will comprehensively explore the various components of a regex and demonstrate their application in the context of matching an email address.
Here's the regex:
/^([a-z0-9_\.-]+)@([\da-z\.-]+)\.([a-z\.]{2,6})$/
| import { useSyncExternalStore } from "react"; | |
| // For more on the useSyncExternalStore hook, see https://react.dev/reference/react/useSyncExternalStore | |
| // The code is almost identical to the source code of zustand, without types and some features stripped out. | |
| // Check the links to see the references in the source code. | |
| // The links are referencing the v5 of the library. If you plan on reading the source code yourself v5 is the best way to start. | |
| // The current v4 version contains lot of deprecated code and extra stuff that makes it hard to reason about if you're new to this. | |
| // https://github.com/pmndrs/zustand/blob/fe47d3e6c6671dbfb9856fda52cb5a3a855d97a6/src/vanilla.ts#L57-L94 | |
| function createStore(createState) { |
The CTREE is built from the optimized microcode (maturity at CMAT_FINAL), it represents an AST-like tree with C statements and expressions. It can be printed as C code.
