snibbets 2.0.37 → 2.0.38

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 8c4679a3bc38da47aa45d83f80813da7fc15ab4c6ce543c262054e118fc28a15
-  data.tar.gz: b902be45475479939390cf651b6c405ff692ca397bde731f2314a50c2ab02218
+  metadata.gz: dbd4e4bc29849bd8b02294a6773dde5b729b4cfd36dc0a6abe415857d856f79e
+  data.tar.gz: 8c998d26d1ca7938ff5275cbc5ba6a0c79f1d035b7b03a702cffc7dff1e91c27
 SHA512:
-  metadata.gz: 466cdfa3acd6966e3942ab2a9d598132bb23833b85c7a293443b9346c5744b96d93a14d0858f489989e6e82e43dcd493c2404ecb25873a3e882912bbe624b644
-  data.tar.gz: 69e63c3bf7aa31587f37956b4c8a370e663199292d3b7b21fb59298400887b4e4c441f22939d5e1de0048e8bba7f892d4d545e0b635050a306fb244e7a4c1148
+  metadata.gz: 3e2e1b0d3a082f6cc046f1033447d077a34f563f92e36396650c1c5122205a73314e9bba4fade2739c90bf98ed869d8667d39be08ef0d496fed7fc6644531770
+  data.tar.gz: 95a9c41d2f5ae6ffeba69946ceaf48c2c0f9f748555f1e8c32c5ed0369c8d4a5c0adf482f9064022a7a72c931fe7f03d2be17814e3b5d1edd31d6e00f369798e

data/CHANGELOG.md

@@ -1,3 +1,12 @@
+### 2.0.38
+
+2024-08-21 08:54
+
+#### NEW
+
+- `--edit-new` will create a new snippet and open it in configured editor, prompting for title and language
+- `--edit-new-titled FILENAME` will create and edit a new snippet with title, language determined by filename extension or prompted for if missing
+
 ### 2.0.36
 
 2024-04-08 14:25

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    snibbets (2.0.37)
+    snibbets (2.0.38)
       mdless (~> 1.0, >= 1.0.32)
       tty-reader (~> 0.9, >= 0.9.0)
       tty-which (~> 0.5, >= 0.5.0)

data/README.md

@@ -1,17 +1,20 @@
 
+
 [![RubyGems.org](https://img.shields.io/gem/v/snibbets)](https://rubygems.org/gems/snibbets)
 
 A tool for accessing code snippets contained in a folder of plain text Markdown files.
 
-Snibbets allows me to keep code snippets in raw files, not relying on a dedicated code snippet app. I can collect and edit my snippets using a text editor, nvALT (nvUltra), or simply by saving snippets from my clipboard to a text file using *NIX redirection on the command line. I can add descriptive names and extended descriptions/notes to code snippets using standard Markdown.
+Snibbets allows me to keep code snippets in raw files, not relying on a dedicated code snippet app. I can collect and edit my snippets using a text editor, nvALT (nvUltra), or simply by saving snippets from my clipboard to a text file using \*NIX redirection on the command line. I can add descriptive names and extended descriptions/notes to code snippets using standard Markdown.
 
 What Snibbets does is simply allow a quick search for a specific snippet that I can either output to the terminal, pipe to my clipboard, or access via LaunchBar (via the included LaunchBar Action). It's basically a wrapper for `find` and `grep` with the ability to separate code blocks from other text in my Markdown files.
 
 
+
 ![Snibbets in action](https://cdn3.brettterpstra.com/uploads/2023/04/snibbets2.gif)
 
 
 
+
 ## Collecting Snippets
 
 Snibbets is designed to work with a folder containing Markdown files. Each Markdown file can have somewhat flexible formatting, as long as there's at least one code block (either indented by 4 spaces/1 tab or fenced with backticks).
@@ -22,7 +25,7 @@ The name of the file should be the description of the snippet, at least in the c
 
 You can combine multiple snippets in a file, though. For example, I have a file called 'Ruby hash snippets.rb.md'. That file contains an array of useful snippets, and each one has a descriptive title in an h3 header above it. Those (ATX) headers are used to split the file, and when you search from the command line, you'll get a menu of all of the snippets in the selected file. (And if you have [fzf](https://github.com/junegunn/fzf) or [gum](https://github.com/charmbracelet/gum) installed, you can quickly filter through with fuzzy searching and find exactly what you need.)
 
-If a file contains multiple snippets, they should be separated by ATX-style headers (one or more `#`) describing the snippets. Additional descriptions and notes can be included outside of the code block. Notes are not output on the console, only the code is displayed. If you want a note to be included in console output, make it a blockquote by preceding it with `>`. 
+If a file contains multiple snippets, they should be separated by ATX-style headers (one or more `#`) describing the snippets. Additional descriptions and notes can be included outside of the code block. Notes are not output on the console, only the code is displayed. If you want a note to be included in console output, make it a blockquote by preceding it with `>`.
 
 A file titled `unix find.bash.md`:
 
@@ -80,13 +83,13 @@ Default config:
 ---
 all: false
 copy: false
-editor: 
+editor:
 extension: md
 highlight: false
 include_blockquotes: false
 interactive: true
 launchbar: false
-menus: 
+menus:
 name_only: false
 output: raw
 source: "~/Dropbox/Snippets"
@@ -110,7 +113,7 @@ The `editor` setting is used to open the config file, and to open snippets for e
 
 The `include_blockquotes` setting determines whether blockquotes are included in the output. By default, Snibbets removes everything other than code blocks (indented or fenced) from the output it displays. But if you want to include a note that you'll see on the command line, you can put it in a block quote by preceding each line you want to preserve with a right angle bracket (`>`).
 
-The `interactive` setting determines whether menus will be displayed. This should generally be true, but if you want silent operation that just displays the best match automatically, set it to false. 
+The `interactive` setting determines whether menus will be displayed. This should generally be true, but if you want silent operation that just displays the best match automatically, set it to false.
 
 The `menus` setting will determine what method is used for displaying interactive menus. If this is not set, it will be automatically determined in the order of `fzf`, `gum`, and `console`. You can manually choose to use one of these options over another by making it the `menus` setting.
 
@@ -118,11 +121,11 @@ The `name_only` key will permanently set Snibbets to only search for snippets by
 
 #### Syntax Highlighting
 
-The `highlight` key turns on syntax highlighting. This requires that either `pygmentize` or `skylighting` is available on your system (both available via package managers like Homebrew). This feature is still in development and results may be mixed. You can also set `highlighter` to `pygments` or `skylight` to force using one highlighter over the other. 
+The `highlight` key turns on syntax highlighting. This requires that either `pygmentize` or `skylighting` is available on your system (both available via package managers like Homebrew). This feature is still in development and results may be mixed. You can also set `highlighter` to `pygments` or `skylight` to force using one highlighter over the other.
 
-Highlighting using Skylighting requires that your snippets be named with extra extensions defining the lexer to use. The last extension before `.md` (or whatever your snippet extension is set to) should be the one that the highlighter will recognize as a valid lexer, e.g. `my code.jquery.js.md`. 
+Highlighting using Skylighting requires that your snippets be named with extra extensions defining the lexer to use. The last extension before `.md` (or whatever your snippet extension is set to) should be the one that the highlighter will recognize as a valid lexer, e.g. `my code.jquery.js.md`.
 
-You can also define languages in your fenced code blocks by putting the lexer name right after the opening fence. When defining multiple snippets in one file that are of different languages, this method will ensure that each one is properly highlighted. 
+You can also define languages in your fenced code blocks by putting the lexer name right after the opening fence. When defining multiple snippets in one file that are of different languages, this method will ensure that each one is properly highlighted.
 
 If you don't use either extensions or fenced code labels with Skylighting, code won't get highlighted.
 
@@ -157,13 +160,15 @@ Snibbet's implementation of Skylighting has limited but better-looking themes, a
 ### Usage
 
 ```
-Snibbets v2.0.37
+Snibbets v2.0.38
 
 Usage: snibbets [options] query
     -a, --all                        If a file contains multiple snippets, output all of them (no menu)
     -c, --[no-]copy                  Copy the output to the clibpoard (also displays on STDOUT)
     -e, --edit                       Open the selected snippet in your configured editor
     -n, --[no-]name-only             Only search file names, not content
+        --edit-new                   Create new snippet by opening editor. Title and language prompted.
+        --edit-new-titled TITLE      Create new snippet by opening editor. Pass filename with language extension(s).
         --[no-]notes                 Display the full content of the snippet
     -o, --output FORMAT              Output format (json|launchbar|*raw)
     -p, --paste, --new               Interactively create a new snippet from clipboard contents (Mac only)
@@ -193,6 +198,8 @@ Use the `--edit` flag on any search to open the found snippet file in your edito
 
 #### Creating new snippets
 
+##### From clipboard
+
 I do most of my snippet editing in [nvUltra], but sometimes I have a function in my clipboard that just needs quick saving and there are so few moving parts to creating a snippet that it just feels like they could be automated/simplified. That's why I added the `--paste` flag. If you have a code snippet in your clipboard, you can just run `snibbets --paste` (or just `-p`) and you'll get a prompt asking you to describe the snippet (used for filename) and one asking what language(s) are represented.
 
 You can input the languages as names, e.g. `rust`, `typescript`, or `scala`, or you can just add file extensions that represent the language. If I say `ts` to that prompt, it will generate an extension of `.ts.md` and then add a metadata tag of `typescript` to the file. The code from the clipboard goes into a fenced code block in the document. You can always go add notes to it later, but it's a great way to save snippets as you come across them (or solutions you figure out after a week of banging your head).
@@ -201,6 +208,9 @@ This command requires that a clipboard utility be available. On macOS, you have
 
 [nvUltra]: https://nvultra.com "nvUltra for Mac"
 
+##### With editor
+
+You can also create new snippets by opening a skeleton file in your editor with `--edit-new`. This will prompt for a title and languages, create the new file, and open it in your editor (or in nvUltra with the `--nvultra` flag). If you use `--edit-new-titled TITLE`, the new snippet will get a filename from `TITLE` and languages will be determined from any extension added to the title, or prompted for if none are found.
 
 #### Saving Settings When Running
 
@@ -212,7 +222,7 @@ _I'm currently reworking the LaunchBar action, and it doesn't function very well
 
 <!-- ### Installation
 
-The LaunchBar action can be installed simply by double clicking the `.lbaction` file in Finder. The CLI is not required for the LaunchBar action to function. 
+The LaunchBar action can be installed simply by double clicking the `.lbaction` file in Finder. The CLI is not required for the LaunchBar action to function.
 
 Once installed, run the action (type `snib` and hit return on the result) to select your Snippets folder.
 

data/bin/snibbets

@@ -47,6 +47,18 @@ module Snibbets
           options[:name_only] = v
         end
 
+        opts.on('--edit-new', 'Create new snippet by opening editor. Title and language prompted.') do
+          arguments[:new] = true
+          arguments[:edit_snippet] = true
+          options[:filename] = nil
+        end
+
+        opts.on('--edit-new-titled TITLE', 'Create new snippet by opening editor. Pass filename with language extension(s).') do |v|
+          arguments[:new] = true
+          arguments[:edit_snippet] = true
+          options[:filename] = v
+        end
+
         opts.on('--[no-]notes', 'Display the full content of the snippet') do |v|
           options[:all_notes] = v
         end
@@ -94,19 +106,19 @@ module Snibbets
           arguments[:save_config] = true
         end
 
-        opts.on('-h', '--help', 'Display this screen') do
+        opts.on_tail('-h', '--help', 'Display this screen') do
           puts "{by}Snibbets {w}v#{VERSION}".x
           puts
           puts optparse
           Process.exit 0
         end
 
-        opts.on('-v', '--version', 'Display version information') do
+        opts.on_tail('-v', '--version', 'Display version information') do
           puts "{by}Snibbets {w}v#{VERSION}".x
           Process.exit 0
         end
 
-        opts.on('--changes', 'Display the changelog (release notes)') do
+        opts.on_tail('--changes', 'Display the changelog (release notes)') do
           display_changelog
           Process.exit 0
         end
@@ -127,6 +139,11 @@ module Snibbets
         Process.exit 0
       end
 
+      if arguments[:new]
+        Snibbets.new_snippet_with_editor(options)
+        Process.exit 0
+      end
+
       unless File.directory?(options[:source])
         puts '{br}The Snippets folder doesn\'t exist, please configure it.'.x
         puts '{bg}Run `{bw}snibbets --configure{bg}` to open the config file for editing.'.x

data/lib/snibbets/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Snibbets
-  VERSION = '2.0.37'
+  VERSION = '2.0.38'
 end

data/lib/snibbets.rb

@@ -166,15 +166,17 @@ module Snibbets
       pb = OS.paste.outdent
       reader = TTY::Reader.new
 
-      # printf 'What does this snippet do? '
-      input = reader.read_line('{by}What does this snippet do{bw}? '.x).strip
-      # input = $stdin.gets.chomp
-      title = input unless input.empty?
-
-      # printf 'What language(s) does it use (separate with spaces, full names or file extensions will work)? '
-      input = reader.read_line('{by}What language(s) does it use ({xw}separate with spaces, full names or file extensions{by}){bw}? '.x).strip
-      # input = $stdin.gets.chomp
-      langs = input.split(/ +/).map(&:strip) unless input.empty?
+      begin
+        input = reader.read_line('{by}What does this snippet do{bw}? '.x).strip
+        title = input unless input.empty?
+
+        input = reader.read_line('{by}What language(s) does it use ({xw}separate with spaces, full names or file extensions{by}){bw}? '.x).strip
+        langs = input.split(/ +/).map(&:strip) unless input.empty?
+      rescue TTY::Reader::InputInterrupt
+        puts "\nCancelled"
+        Process.exit 1
+      end
+
       exts = langs.map { |lang| Lexers.lang_to_ext(lang) }.delete_if(&:nil?)
       tags = langs.map { |lang| Lexers.ext_to_lang(lang) }.concat(langs).delete_if(&:nil?).sort.uniq
 
@@ -196,6 +198,93 @@ module Snibbets
       open_snippet_in_nvultra(filepath) if Snibbets.arguments[:nvultra]
     end
 
+    def new_snippet_with_editor(options)
+      return false unless $stdout.isatty
+
+      trap('SIGINT') do
+        Howzit.console.info "\nCancelled"
+        exit!
+      end
+
+      reader = TTY::Reader.new
+      if options[:filename]
+        title = options[:filename].sub(/(\.#{Snibbets.options[:extension]})$/, '')
+        extensions = options[:filename].match(/(\.\w+)+$/)
+        langs = extensions ? extensions[0].split(/\./).delete_if(&:empty?) : []
+        title.sub!(/(\.\w+)+$/, '')
+      else
+        begin
+          input = reader.read_line('{by}What does this snippet do{bw}? '.x).strip
+          title = input unless input.empty?
+        rescue TTY::Reader::InputInterrupt
+          puts "\nCancelled"
+          Process.exit 1
+        end
+      end
+
+      if langs.nil? || langs.empty?
+        begin
+          # printf 'What language(s) does it use (separate with spaces, full names or file extensions will work)? '
+          input = reader.read_line('{by}What language(s) does it use ({xw}separate with spaces, full names or file extensions{by}){bw}? '.x).strip
+          # input = $stdin.gets.chomp
+          langs = input.split(/ +/).map(&:strip) unless input.empty?
+        rescue TTY::Reader::InputInterrupt
+          puts "\nCancelled"
+          Process.exit 1
+        end
+      end
+
+      exts = langs.map { |lang| Lexers.lang_to_ext(lang) }.delete_if(&:nil?)
+      tags = langs.map { |lang| Lexers.ext_to_lang(lang) }.concat(langs).delete_if(&:nil?).sort.uniq
+
+      exts = langs if exts.empty?
+
+      filename = "#{title}#{exts.map { |x| ".#{x}" }.join('')}.#{Snibbets.options[:extension]}"
+      filepath = File.join(File.expand_path(Snibbets.options[:source]), filename)
+
+      output =<<~EOOUTPUT
+        tags: #{tags.join(', ')}
+
+        > #{title}
+      EOOUTPUT
+
+      if langs.count.positive?
+        tags.each do |lang|
+          comment = case lang
+                    when /(c|cpp|objectivec|java|javascript|dart|php|golang|typescript|kotlin)/
+                      '// Code'
+                    else
+                      '# Code'
+                    end
+
+          output << <<~EOLANGS
+
+            ```#{lang}
+            #{comment}
+            ```
+          EOLANGS
+        end
+      else
+        output << <<~EOCODE
+          ```LANG
+          ```
+        EOCODE
+      end
+
+      File.open(filepath, 'w') do |f|
+        f.puts output
+      end
+
+      puts "{bg}New snippet written to {bw}#{filename}.".x
+
+      if Snibbets.arguments[:nvultra]
+        sleep 2
+        open_snippet_in_nvultra(filepath)
+      else
+        open_snippet_in_editor(filepath)
+      end
+    end
+
     def handle_launchbar(results)
       output = []
 

data/src/_README.md

@@ -1,16 +1,19 @@
 # Snibbets
 
 <!--README-->
+
 [![RubyGems.org](https://img.shields.io/gem/v/snibbets)](https://rubygems.org/gems/snibbets)
 
 A tool for accessing code snippets contained in a folder of plain text Markdown files.
 
-Snibbets allows me to keep code snippets in raw files, not relying on a dedicated code snippet app. I can collect and edit my snippets using a text editor, nvALT (nvUltra), or simply by saving snippets from my clipboard to a text file using *NIX redirection on the command line. I can add descriptive names and extended descriptions/notes to code snippets using standard Markdown.
+Snibbets allows me to keep code snippets in raw files, not relying on a dedicated code snippet app. I can collect and edit my snippets using a text editor, nvALT (nvUltra), or simply by saving snippets from my clipboard to a text file using \*NIX redirection on the command line. I can add descriptive names and extended descriptions/notes to code snippets using standard Markdown.
 
 What Snibbets does is simply allow a quick search for a specific snippet that I can either output to the terminal, pipe to my clipboard, or access via LaunchBar (via the included LaunchBar Action). It's basically a wrapper for `find` and `grep` with the ability to separate code blocks from other text in my Markdown files.
 
 <!--GITHUB-->
+
 ![Snibbets in action](https://cdn3.brettterpstra.com/uploads/2023/04/snibbets2.gif)
+
 <!--END GITHUB-->
 <!--JEKYLL{% gif /uploads/2023/04/snibbets2.gif %}-->
 
@@ -24,7 +27,7 @@ The name of the file should be the description of the snippet, at least in the c
 
 You can combine multiple snippets in a file, though. For example, I have a file called 'Ruby hash snippets.rb.md'. That file contains an array of useful snippets, and each one has a descriptive title in an h3 header above it. Those (ATX) headers are used to split the file, and when you search from the command line, you'll get a menu of all of the snippets in the selected file. (And if you have [fzf](https://github.com/junegunn/fzf) or [gum](https://github.com/charmbracelet/gum) installed, you can quickly filter through with fuzzy searching and find exactly what you need.)
 
-If a file contains multiple snippets, they should be separated by ATX-style headers (one or more `#`) describing the snippets. Additional descriptions and notes can be included outside of the code block. Notes are not output on the console, only the code is displayed. If you want a note to be included in console output, make it a blockquote by preceding it with `>`. 
+If a file contains multiple snippets, they should be separated by ATX-style headers (one or more `#`) describing the snippets. Additional descriptions and notes can be included outside of the code block. Notes are not output on the console, only the code is displayed. If you want a note to be included in console output, make it a blockquote by preceding it with `>`.
 
 A file titled `unix find.bash.md`:
 
@@ -82,13 +85,13 @@ Default config:
 ---
 all: false
 copy: false
-editor: 
+editor:
 extension: md
 highlight: false
 include_blockquotes: false
 interactive: true
 launchbar: false
-menus: 
+menus:
 name_only: false
 output: raw
 source: "~/Dropbox/Snippets"
@@ -112,7 +115,7 @@ The `editor` setting is used to open the config file, and to open snippets for e
 
 The `include_blockquotes` setting determines whether blockquotes are included in the output. By default, Snibbets removes everything other than code blocks (indented or fenced) from the output it displays. But if you want to include a note that you'll see on the command line, you can put it in a block quote by preceding each line you want to preserve with a right angle bracket (`>`).
 
-The `interactive` setting determines whether menus will be displayed. This should generally be true, but if you want silent operation that just displays the best match automatically, set it to false. 
+The `interactive` setting determines whether menus will be displayed. This should generally be true, but if you want silent operation that just displays the best match automatically, set it to false.
 
 The `menus` setting will determine what method is used for displaying interactive menus. If this is not set, it will be automatically determined in the order of `fzf`, `gum`, and `console`. You can manually choose to use one of these options over another by making it the `menus` setting.
 
@@ -120,11 +123,11 @@ The `name_only` key will permanently set Snibbets to only search for snippets by
 
 #### Syntax Highlighting
 
-The `highlight` key turns on syntax highlighting. This requires that either `pygmentize` or `skylighting` is available on your system (both available via package managers like Homebrew). This feature is still in development and results may be mixed. You can also set `highlighter` to `pygments` or `skylight` to force using one highlighter over the other. 
+The `highlight` key turns on syntax highlighting. This requires that either `pygmentize` or `skylighting` is available on your system (both available via package managers like Homebrew). This feature is still in development and results may be mixed. You can also set `highlighter` to `pygments` or `skylight` to force using one highlighter over the other.
 
-Highlighting using Skylighting requires that your snippets be named with extra extensions defining the lexer to use. The last extension before `.md` (or whatever your snippet extension is set to) should be the one that the highlighter will recognize as a valid lexer, e.g. `my code.jquery.js.md`. 
+Highlighting using Skylighting requires that your snippets be named with extra extensions defining the lexer to use. The last extension before `.md` (or whatever your snippet extension is set to) should be the one that the highlighter will recognize as a valid lexer, e.g. `my code.jquery.js.md`.
 
-You can also define languages in your fenced code blocks by putting the lexer name right after the opening fence. When defining multiple snippets in one file that are of different languages, this method will ensure that each one is properly highlighted. 
+You can also define languages in your fenced code blocks by putting the lexer name right after the opening fence. When defining multiple snippets in one file that are of different languages, this method will ensure that each one is properly highlighted.
 
 If you don't use either extensions or fenced code labels with Skylighting, code won't get highlighted.
 
@@ -176,6 +179,8 @@ Use the `--edit` flag on any search to open the found snippet file in your edito
 
 #### Creating new snippets
 
+##### From clipboard
+
 I do most of my snippet editing in [nvUltra], but sometimes I have a function in my clipboard that just needs quick saving and there are so few moving parts to creating a snippet that it just feels like they could be automated/simplified. That's why I added the `--paste` flag. If you have a code snippet in your clipboard, you can just run `snibbets --paste` (or just `-p`) and you'll get a prompt asking you to describe the snippet (used for filename) and one asking what language(s) are represented.
 
 You can input the languages as names, e.g. `rust`, `typescript`, or `scala`, or you can just add file extensions that represent the language. If I say `ts` to that prompt, it will generate an extension of `.ts.md` and then add a metadata tag of `typescript` to the file. The code from the clipboard goes into a fenced code block in the document. You can always go add notes to it later, but it's a great way to save snippets as you come across them (or solutions you figure out after a week of banging your head).
@@ -184,6 +189,9 @@ This command requires that a clipboard utility be available. On macOS, you have
 
 [nvUltra]: https://nvultra.com "nvUltra for Mac"
 
+##### With editor
+
+You can also create new snippets by opening a skeleton file in your editor with `--edit-new`. This will prompt for a title and languages, create the new file, and open it in your editor (or in nvUltra with the `--nvultra` flag). If you use `--edit-new-titled TITLE`, the new snippet will get a filename from `TITLE` and languages will be determined from any extension added to the title, or prompted for if none are found.
 
 #### Saving Settings When Running
 
@@ -195,7 +203,7 @@ _I'm currently reworking the LaunchBar action, and it doesn't function very well
 
 <!-- ### Installation
 
-The LaunchBar action can be installed simply by double clicking the `.lbaction` file in Finder. The CLI is not required for the LaunchBar action to function. 
+The LaunchBar action can be installed simply by double clicking the `.lbaction` file in Finder. The CLI is not required for the LaunchBar action to function.
 
 Once installed, run the action (type `snib` and hit return on the result) to select your Snippets folder.
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: snibbets
 version: !ruby/object:Gem::Version
-  version: 2.0.37
+  version: 2.0.38
 platform: ruby
 authors:
 - Brett Terpstra
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2024-04-12 00:00:00.000000000 Z
+date: 2024-08-21 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -330,7 +330,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.2.16
+rubygems_version: 3.2.15
 signing_key:
 specification_version: 4
 summary: Snibbets