-
Disable and stop the systemd-resolved service:
sudo systemctl disable systemd-resolved.service sudo systemctl stop systemd-resolved
-
Then put the following line in the
[main]
section of your/etc/NetworkManager/NetworkManager.conf
:
Discover gists
Type | Emoji | code |
---|---|---|
feat | ✨ | :sparkles: |
fix | 🐛 | :bug: |
docs | 📚 | :books: |
style | 💎 | :gem: |
refactor | 🔨 | :hammer: |
perf | 🚀 | :rocket: |
test | 🚨 | :rotating_light: |
build | 📦 | :package: |
[ | |
{ | |
"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.
Good question! I am collecting human data on how quantization affects outputs. See here for more information: ggerganov/llama.cpp#5962
In the meantime, use the largest that fully fits in your GPU. If you can comfortably fit Q4_K_S, try using a model with more parameters.
See the wiki upstream: https://github.com/ggerganov/llama.cpp/wiki/Feature-matrix