DEV Community: Daisuke Mino

BigQuery Runner for VSCode

Daisuke Mino — Mon, 07 Mar 2022 10:17:35 +0000

Motivation

Write a query, run it, and see the results on the fly in VSCode, much like BigQuery web UI.

Installation

BigQuery Runner - Visual Studio Marketplace

Features

Query Validation

You can write queries while checking the queries you are writing for syntax errors, unrecognized field names, etc.
Because the extension marks error locations on the editor file.

Query Costs

You need not be overly concerned about how much data the query you are writing will scan and charge for.
Because the extension will show you the amount of data that would be scanned and the amount of data actually scanned.

Running Query

You can query the file you have open directly into a BigQuery, or if you have selected text, you can query that text.

Format Results

Output formats supported include aligned tables, CSV, JSON, and JSON Lines.

Output Results

You can view the results of your query in a dedicated panel, in the output panel, or even output them to a file.

Command Based

You can execute all operations from commands.
Command support means that once you have set your key bindings, you can repeatedly try queries without taking your hands off the keyboard.

Rewrite Teensy with Docker

Daisuke Mino — Tue, 21 Nov 2017 23:43:48 +0000

Using dockerized Teensy Loader CLI makes it easier to rewrite programs to Teensy.
qmk/qmk_firmware is already dockerized. By using minodisk/teensy_loader together, all processes such as building .hex, loading it into Teensy, and rebooting Teensy can be completed with Docker.

Motivation

I do not want to install various things on my local machine.

Premise

qmk/qmk_firmware has been pulled
Docker is already installed in your local machine
In Linux (Docker for Mac or Win might be difficult or not be able to mount USB)

Demo

How to use

Step 1. Prepare YAML for Docker Compose

Add qmk_firmware/docker-compose.yml:

version: '2'
services:
  qmk_firmware:
    build: .
    environment:
      keyboard: ergodox_ez
      subproject:
      keymap: <Your Keymap Name>
    volumes:
      - .:/qmk
      - /qmk/.build
  teensy_loader:
    image: minodisk/teensy_loader:0.0.1
    depends_on:
      - qmk_firmware
    privileged: true
    environment:
      hex: ergodox_ez_<Your Keymap Name>
    volumes:
      - /dev/bus/usb:/dev/bus/usb
    volumes_from:
      - qmk_firmware

Step 2. Build and up

docker-compose build
docker-compose up

Step 3. Press reset button

When the terminal outputs Waiting for Teensy device..., press the reset button on Teensy.

How to work

In teensy_loader container, waits for the .hex to be generated on the volume shared with the qmk_firmaware container
In qmk_firmware container, builds .hex
In teensy_loader container, finds .hex on the volume shared with the qmk_firmware container and runs teensy_loader_cli with wait option
In real world, you press reset button on Teensy (if it maps to a key, press that key)
In teensy_loader container, teensy_loader_cli writes .hex to Teensy and reboots it

Automatically switch to insert mode when focusing on terminal window in Vim8

Daisuke Mino — Tue, 21 Nov 2017 07:36:16 +0000

autocmd BufWinEnter,WinEnter * if &buftype == 'terminal' | silent! normal i | endif

According to :help Terminal-mode, startinsert doesn't work on terminal window.

In Terminal-Normal mode you can move the cursor around with the usual Vim commands, Visually mark text, yank text, etc. But you cannot change the contents of the buffer. The commands that would start insert mode, such as 'i' and 'a', return to Terminal-Job mode. The window will be updated to show the contents of the terminal. |:startinsert| is ineffective.