ShikiSuen

Related sample project: https://github.com/vChewing/vChewing-macOS/tree/3.4.9

It seems that individual bug reports doesn't work at all. Besides, the entire InputMethodKit needs a renovation.

This thread will be sent to Apple by certain special approaches after gathering enough usable information.

Let's talk about what InputMethodKits needs to improve. Here's my conclusion. If Apple think there's already an API, then it might be either mulfunctioning or not exposed to Swift.

1. An official Swift-friendly wrapper with neither "!" nor "?" in the parameters of all provided APIs.

longfin

들어가며

이 글은 플라네타리움 공동체 분들께 22년 3분기 이후의 나인 크로니클, 그리고 Libplanet 개발 기조에 대해 제 생각을 전달드리는 것이 목표입니다. 다만 모두가 아시듯이 나인 크로니클과 Libplanet은 오픈 소스 프로젝트이기도 하므로, 제 GitHub Gist 에 초고를 작성하였습니다. 이런 삐딱함(?)은 일견 아무래도 좋은 치기이기도 하지만, 한편으로 저는 어쩌면 이게 제가 이제부터 이야기할 것들을 함축한 것일지 모른다고도 생각합니다.

공격과 수비

게임 개발에 블록체인을 사용하면 느리고 기획도 제한이 심할 것 같은데, 극복할 수 있는 방법이 있으신가요?

dahlia

As of June 2022, VS Code's [Live Share] still does not work well on Apple silicon Macs (M1/M2 series) without [Rosetta 2]. Although [this bug is tracked in the official issue tracker on GitHub][1], unfortuneately, Live Share extension is not open source, so no outsiders can send any patch to address this bug to the upstream. Instead, I'd like to share a workaround I found:[^1]

1. Install [.NET SDK] 6 (arm64) or higher. It's also available on Homebrew Cask: brew install --cask dotnet-sdk.

2. Replace vsls-agent (no postfix) in

dahlia

Comparing two Bencodex binary files

A small CLI program to easily compare two Bencodex trees:

$ pip3 install --user -r requirements.txt
$ ./bdiff.py ./a.dat ./b.dat
--- a.dat

drewkerr

const app = Application.currentApplication()
app.includeStandardAdditions = true

function getJSON(path) {
	const fullPath = path.replace(/^~/, app.pathTo('home folder'))
	const contents = app.read(fullPath)
	return JSON.parse(contents)
}

function run() {

sindresorhus

Pure ESM package

The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.

This means you have the following choices:

1. Use ESM yourself. (preferred)
   Use import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.
2. If the package is used in an async context, you could use await import(…) from CommonJS instead of require(…).
3. Stay on the existing version of the package until you can move to ESM.

asiluoy

신토불이 네이버 쇼핑

네이버 쇼핑에서 해외직구를 제외한 결과물만 보여줍니다.

설치

적용 전

mohanpedala

Table of Contents

• set -e, -u, -x, -o pipefail
• set -e
• set -x
• set -u
• set -o pipefail
• Setting IFS
• Original Reference

set -e, -u, -x, -o pipefail

paolocarrasco

Problem

You have installed GPG, then tried to commit and suddenly you see this error message after it:

error: gpg failed to sign the data
fatal: failed to write commit object

Debug

tomaka

// Suppose you have a variable named `future` which implements the `Future` trait.
let future: impl Future = ...;

// This gist demonstrates how to run the future until completion using the `stdweb` crate.


// The various imports.

extern crate futures;
extern crate stdweb;