garyo

==> INFO: Fetching info for git ref: master
==> INFO: Downloading tarball from GitHub. This could take a while, please be patient.
==> DEBUG: executing: curl -L https://github.com/emacs-mirror/emacs/tarball/1a1f47e4a1fb70e6810f9eabd0f1826b71a2bcb0 -o /Users/garyo/src/build-emacs-for-macos/tarballs/emacs-mirror-emacs-1a1f47e.tgz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0

100 4024k    0 4024k    0     0  4244k      0 --:--:-- --:--:-- --:--:-- 4244k
100  9.8M    0  9.8M    0     0  5146k      0 --:--:--  0:00:01 --:--:-- 6001k
100 15.0M    0 15.0M    0     0  5219k      0 --:--:--  0:00:02 --:--:-- 5681k
100 20.3M    0 20.3M    0     0  5266k      0 --:--:--  0:00:03 --:--:-- 5588k
100 25.5M    0 25.5M    0     0  5279k      0 --:--:--  0:00

garyo

==> INFO: Copying "Emacs.app" to: /Users/garyo/src/build-emacs-for-macos/builds/Emacs.2023-10-11.cfed3bb.master.macOS-13.arm64
==> INFO: Copying "COPYING" to: /Users/garyo/src/build-emacs-for-macos/builds/Emacs.2023-10-11.cfed3bb.master.macOS-13.arm64
==> INFO: Adding "emacs" CLI helper to Emacs.app
==> DEBUG: executing: cp -pRL /Users/garyo/src/build-emacs-for-macos/helper/emacs-cli.bash /Users/garyo/src/build-emacs-for-macos/builds/Emacs.2023-10-11.cfed3bb.master.macOS-13.arm64/Emacs.app/Contents/MacOS/bin/emacs
==> DEBUG: executing: chmod +w /Users/garyo/src/build-emacs-for-macos/builds/Emacs.2023-10-11.cfed3bb.master.macOS-13.arm64/Emacs.app/Contents/MacOS/bin/emacs
==> INFO: Bundling C source files into Emacs.app for documentation purposes...
==> DEBUG: Copying *.c and *.h files from '/Users/garyo/src/build-emacs-for-macos/sources/emacs-mirror-emacs-cfed3bb/src' to: Contents/Resources/src
==> DEBUG: Patching 'Contents/Resources/lisp/site-start.el' to allow Emacs to find bundled C sources
==> INFO: Bundli

garyo

/**
 * Logseq custom theme by Gary Oberbrunner
 * TO USE: `@import url("https://oberbrunner.com/logseq/themes/garyo/custom.css");`
 */

/* Fonts: Hack */
@import url("https://cdn.jsdelivr.net/npm/hack-font@3.3.0/build/web/hack.css");

/* === Colors based on OneNote === */

garyo

```yaml
---
 doe: "a deer, a female deer"
 ray: "a drop of golden sun"
 pi: 3.14159
 xmas: true
 french-hens: 3
 calling-birds:
   - huey
   - dewey

garyo

[    0.000000] Linux version 5.10.60.1-microsoft-standard-WSL2 (oe-user@oe-host) (x86_64-msft-linux-gcc (GCC) 9.3.0, GNU ld (GNU Binutils) 2.34.0.20200220) #1 SMP Wed Aug 25 23:20:18 UTC 2021
[    0.000000] Command line: initrd=\initrd.img panic=-1 nr_cpus=32 swiotlb=force console=ttyS0,115200 debug pty.legacy_count=0
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Centaur CentaurHauls
[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256

garyo

Query by text "covid-19" -- returns PDB IDs, one per line

Just fill in the keywords section, the rest is constant. Keywords are comma-separated and get "AND"ed together.

% curl --data-binary '<orgPdbQuery>
<queryType>org.pdb.query.simple.AdvancedKeywordQuery</queryType>
<keywords>covid-19</keywords>
</orgPdbQuery>' https://www.rcsb.org/pdb/rest/search

Query by text "1d3"

garyo

diff --git a/io_scene_gltf2/blender/imp/gltf2_blender_gltf.py b/io_scene_gltf2/blender/imp/gltf2_blender_gltf.py
index 5904a974..ed652676 100755
--- a/io_scene_gltf2/blender/imp/gltf2_blender_gltf.py
+++ b/io_scene_gltf2/blender/imp/gltf2_blender_gltf.py
@@ -23,7 +23,26 @@ class BlenderGlTF():
         raise RuntimeError("%s should not be instantiated" % cls)

     @staticmethod
-    def create(gltf):
+    def create(gltf, profile=True):

garyo

DaVinci Resolve Scripting Documentation

Updated as of 08 March 2019

---

In this package, you will find a brief introduction to the Scripting API for DaVinci Resolve Studio. Apart from this README.txt file, this package contains folders containing the basic import modules for scripting access (DaVinciResolve.py) and some representative examples.

Overview

As with Blackmagic Design Fusion scripts, user scripts written in Lua and Python programming languages are supported. By default, scripts can be invoked from the Console window in the Fusion page, or via command line. This permission can be changed in Resolve Preferences, to be only from Console, or to be invoked from the local network. Please be aware of the security implications when allowing scripting access from outside of the Resolve application.

garyo

Install

• Use recent nightly Emacs 27 with libjansson support (native JSON)
• Install Node v10 or later (with npm)
• Run this:

npm install

Run test

emacs -q -l test-init.el test.vue

garyo

///////// This part just prints out all the event loop ticks
// Only use in node.js, not browser (I think)
const async_hooks = require('async_hooks');

async_hooks.createHook({
  init: (id, type, triggerAsyncId, resource) => {
    process._rawDebug(`${type}(${id}): trigger: ${triggerAsyncId}, resource: ${resource}`);
  },
  before: (id) => {
    process._rawDebug(`async hook before: ${id}`);