Skip to content

Instantly share code, notes, and snippets.

@Domon
Domon / workaround-for-mac-vim-r179-issue-with-ruby-3-3.md
Last active April 2, 2024 05:21
Work around MacVim r179 (Vim 9.1.0)'s incompatibility issue with Ruby 3.3 by using Ruby 3.2 instead

Workaround for MacVim r179 (Vim 9.1.0)'s incompatibility issue with Ruby 3.3

Patch

A patch is available on 3 Jan 2024: Commit: patch 9.1.0003: Cannot build against Ruby 33 dynamically.

However, it looks like the latest MacVim release (r179 on 5 Jan 2024) does not include that patch.

Workaround: Set up MacVim and Command-T to use Ruby 3.2

<b>Notice</b>: Trying to access array offset on value of type bool in <b>/home/customer/www/quantres.com/public_html/wp-content/plugins/advanced-custom-fields-viewer/viewer.php</b> on line <b>93</b><br />
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="ja">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<meta name="viewport" content="width=device-width">
<meta name='robots' content='noindex,follow' />
<title>Database Error</title>
<style type="text/css">
html {
SQLite3::CorruptException: database disk image is malformed
/usr/local/bundle/ruby/2.7.0/gems/sqlite3-1.4.2/lib/sqlite3/resultset.rb:108:in `step'
/usr/local/bundle/ruby/2.7.0/gems/sqlite3-1.4.2/lib/sqlite3/resultset.rb:108:in `next'
/usr/local/bundle/ruby/2.7.0/gems/sqlite3-1.4.2/lib/sqlite3/resultset.rb:133:in `each'
/usr/local/bundle/ruby/2.7.0/gems/sequel-5.28.0/lib/sequel/adapters/sqlite.rb:334:in `block in fetch_rows'
/usr/local/bundle/ruby/2.7.0/gems/sqlite3-1.4.2/lib/sqlite3/database.rb:339:in `query'
/usr/local/bundle/ruby/2.7.0/gems/sequel-5.28.0/lib/sequel/adapters/sqlite.rb:200:in `block (2 levels) in _execute'
/usr/local/bundle/ruby/2.7.0/gems/skylight-core-4.2.0/lib/skylight/core/probes/sequel.rb:22:in `block (2 levels) in log_connection_yield'
/usr/local/bundle/ruby/2.7.0/gems/activesupport-6.0.3.1/lib/active_support/notifications.rb:180:in `block in instrument'
/usr/local/bundle/ruby/2.7.0/gems/activesupport-6.0.3.1/lib/active_support/notifications/instrumenter.rb:24:in `instrument'
<!doctype>
<html lang="en-US" dir="ltr">
<head>
<title>Error - Internal Error - Apple Community</title>
<meta name="description" content="An unexpected error has occurred.">
<link href="https://communities.apple.com/en202005220507/public/compiled/pages/error.css" rel="stylesheet">
<html>
<head><title>400 Request Header Or Cookie Too Large</title></head>
<body bgcolor="white">
<center><h1>400 Bad Request</h1></center>
<center>Request Header Or Cookie Too Large</center>
<hr><center>nginx</center>
</body>
</html>
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->

I'm planning on either writing this up in detail or maybe doing a screencast about screencasting, but I'll give a short version here.

On sound quality:

This matters a lot. In decreasing order of importance:

  1. Remove echo. You have to hear this to understand. Set up a mic in front of your mouth and record a sentence. Then, put a thick comforter over you and the mic and say it again at the same distance. Listen to
線路上にクマの死骸 JR石北線白滝―丸瀬布間 特急、普通計2本に遅れ
07/16 22:42 更新
 【遠軽】16日午前7時10分ごろ、オホーツク管内遠軽町のJR石北線白滝―丸瀬布間の線路上にクマの死骸があるのを、通りがかった普通列車(2両編成、乗客8人)の乗務員が見つけた。除去作業のため、この普通列車と特急の計2本が最大3時間48分遅れ、約110人に影響が出た。
 JR北海道によると、現場では15日午後9時半ごろ、旭川発北見行き快速列車(1両編成、乗客8人)がクマと接触し停車。乗務員がクマを探したが確認できず、車両点検を行い、6分後に運転を再開したという。
 JRが死骸除去を依頼した遠軽猟友会によると、クマは3歳の雌で、体長約1・5メートル、体重約150キロ。レール中央に横たわっていた。
線路にクマの死骸、3時間不通…タクシーで輸送
2018年07月18日 08時47分
16日午前7時10分頃、北海道遠軽町のJR石北線白滝―丸瀬布間で、上川発遠軽行き普通列車(2両編成)の乗務員が、線路内にクマの死骸を見つけた。列車は白滝駅まで引き返し、乗客8人は同駅からタクシーで振り替え輸送された。クマは除去され、列車は約3時間後に運転を再開した。
JR北海道旭川支社によると、15日夜にも同じ区間で旭川発北見行きの快速列車がクマと遭遇、接触して停車していた。両日とも、乗客にけがはなかった。
<html>
<head><title>504 Gateway Time-out</title></head>
<body bgcolor="white">
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>HiNetCDN/1801</center>
</body>
</html>
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->