snibbets 2.0.29 → 2.0.31

data/lib/snibbets/todo_spec.rb

@@ -0,0 +1,11 @@
+# frozen_string_literal: true
+
+# RSpec.describe Snibbets::Todo do
+#   subject(:todo) { Snibbets::Todo.new }
+
+#   describe ".todo" do
+#     it "returns todo" do
+#       expect(todo.todo).to be "TODO"
+#     end
+#   end
+# end

data/lib/snibbets/version.rb

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

data/lib/snibbets.rb

@@ -116,7 +116,6 @@ module Snibbets
       notebook = Snibbets.options[:source].gsub(/ /, '%20')
       note = ERB::Util.url_encode(File.basename(filepath, '.md'))
       url = "x-nvultra://open?notebook=#{notebook}&note=#{note}"
-      puts url
       `open '#{url}'`
     end
 
@@ -153,7 +152,7 @@ module Snibbets
     end
 
     def new_snippet_from_clipboard
-      return false unless $stdin.isatty
+      return false unless $stdout.isatty
 
       trap('SIGINT') do
         Howzit.console.info "\nCancelled"
@@ -248,7 +247,7 @@ module Snibbets
       else
         filepath = nil
         if results.empty?
-          warn 'No results'
+          warn 'No results' if Snibbets.options[:interactive]
           Process.exit 0
         elsif results.length == 1 || !Snibbets.options[:interactive]
           filepath = results[0]['path']
@@ -272,7 +271,7 @@ module Snibbets
         snippets = input.snippets
 
         if snippets.empty?
-          warn 'No snippets found'
+          warn 'No snippets found' if Snibbets.options[:interactive]
           Process.exit 0
         elsif snippets.length == 1 || !Snibbets.options[:interactive]
           if Snibbets.options[:output] == 'json'
@@ -280,9 +279,11 @@ module Snibbets
           else
             snippets.each do |snip|
               header = File.basename(filepath, '.md')
-              warn header
-              warn '-' * header.length
-              warn ''
+              if $stdout.isatty
+                puts header
+                puts '-' * header.length
+                puts ''
+              end
               code = snip['code']
               lang = snip['language']
               print(code, filepath, lang)
@@ -307,19 +308,23 @@ module Snibbets
         if Snibbets.options[:output] == 'json'
           print(snippets.to_json, filepath)
         else
-          header = File.basename(filepath, '.md')
-          warn header
-          warn '=' * header.length
-          warn ''
+          if $stdout.isatty
+            header = File.basename(filepath, '.md')
+            warn header
+            warn '=' * header.length
+            warn ''
+          end
           print_all(snippets, filepath)
         end
       elsif Snibbets.options[:output] == 'json'
         print(answer.to_json, filepath)
       else
-        header = "#{File.basename(filepath, '.md')}: #{answer['title']}"
-        warn header
-        warn '-' * header.length
-        warn ''
+        if $stdout.isatty
+          header = "#{File.basename(filepath, '.md')}: #{answer['title']}"
+          warn header
+          warn '-' * header.length
+          warn ''
+        end
         code = answer['code']
         lang = answer['language']
         print(code, filepath, lang)
@@ -333,9 +338,10 @@ module Snibbets
 
         snippets.each do |snippet|
           lang = snippet['language']
-          warn "### #{snippet['title']} ###"
-          warn ''
-          # warn "# #{'-' * snippet['title'].length}"
+
+          puts "### #{snippet['title']} ###"
+          puts ''
+
           print(snippet['code'], filepath, lang)
           puts
         end
@@ -346,7 +352,7 @@ module Snibbets
       if Snibbets.options[:highlight] && Snibbets.options[:output] == 'raw'
         $stdout.puts(Highlight.highlight(output, filepath, syntax))
       else
-        $stdout.puts(output)
+        $stdout.puts(Snibbets.options[:all_notes] ? output : output.clean_code)
       end
       if Snibbets.options[:copy]
         OS.copy(output)

data/scripts/fixreadme.rb

@@ -0,0 +1,23 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+current_ver = `rake cver`
+src = 'src/_README.md'
+dest = 'README.md'
+
+readme = IO.read(src).force_encoding('ASCII-8BIT').encode('UTF-8', invalid: :replace, undef: :replace, replace: '?')
+
+content = readme.match(/(?<=\<!--README-->)(.*?)(?=\<!--END README-->)/m)[0]
+
+content.gsub!(/<!--VER-->(.*?)<!--END VER-->/, current_ver)
+content.gsub!(/<!--GITHUB-->(.*?)<!--END GITHUB-->/m, '\1')
+content.gsub!(/<!--JEKYLL(.*?)-->/m, '')
+
+content.gsub!(/^@cli\((.*?)\)/) do
+  cmd = Regexp.last_match(1)
+  `#{cmd}`.strip.gsub(/\n{2,}/, "\n\n")
+end
+
+File.open(dest, 'w') { |f| f.puts(content) }
+
+Process.exit 0

data/snibbets.gemspec

@@ -27,9 +27,9 @@ Gem::Specification.new do |spec|
   spec.bindir = "bin"
   spec.executables << 'snibbets'
 
-  spec.files = Dir["lib/**/*.rb"].reject { |f| f.end_with?("_spec.rb") }
-  spec.files += Dir["lib/themes/*.theme"]
-  spec.files += Dir["[A-Z]*"]
+  spec.files = Dir.chdir(File.expand_path('..', __FILE__)) do
+    `git ls-files -z`.split("\x0").reject { |f| f.strip =~ %r{^((test|spec|features)/|\.git|buildnotes|.*\.taskpaper)} }
+  end
 
   spec.add_development_dependency "bundler", "~> 2.0"
   spec.add_development_dependency "awesome_print", "~> 1.9"

data/{README.md.orig → src/_README.md}

@@ -1,22 +1,20 @@
+# Snibbets
 
-
+<!--README-->
+<!--GITHUB-->
 [![RubyGems.org](https://img.shields.io/gem/v/snibbets)](https://rubygems.org/gems/snibbets)
-<<<<<<< HEAD
-[![GitHub Actions](https://github.com/ttscoff/snibbets/actions/workflows/check.yml/badge.svg)](https://github.com/ttscoff/snibbets/actions/workflows/check.yml)
-=======
 <!-- [![GitHub Actions](https://github.com/ttscoff/snibbets/actions/workflows/check.yml/badge.svg)](https://github.com/ttscoff/snibbets/actions/workflows/check.yml) -->
->>>>>>> develop
-
+<!--END GITHUB-->
 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.
 
 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 %}-->
 
 ## Collecting Snippets
 
@@ -28,7 +26,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 can be included outside of the code block. For example:
+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`:
 
@@ -49,22 +47,22 @@ A file titled `unix find.bash.md`:
 
         find /dir/dir -type f -mtime +540 -mtime -720 -printf \"%p\",\"%s\",\"%AD\",|"%TD\"\\n > /dir/dir/output.csv
 
-You can include MultiMarkdown metadata in your snippets, either in a YAML block or just at the top of the file with raw key/value pairs. I mostly use this for adding tags, which are then synced to macOS tags when I save. It makes it easy to search for snippets in [nvUltra](https://nvultra.com/), and also allows you to do searches like `snibbets tag:javascript url parser` in Snibbets.
+You can include MultiMarkdown metadata in your snippets, either in a YAML block or just at the top of the file with raw key/value pairs. I mostly use this for adding tags, which are then synced to macOS tags when I save. It makes it easy to search for snippets in [nvUltra](https://nvultra.com/), and also allows you to do searches like `snibbets tag:javascript url parser` with Snibbets.
 
 ## CLI
 
 ### Dependencies
 
-Snibbets requires Ruby 3.0+. On recent versions of macOS, this is not included by default. You can install it via the Command Line Tools from Apple. On macOS and most other systems, you can use something like [Homebrew], [rbenv], [rvm], or [asdf] to install Ruby 3.
+Snibbets requires Ruby 3.0+. On recent versions of macOS, this is not included by default. You can install it via the Command Line Tools from Apple. On macOS and most other systems, you can also use something like [Homebrew], [rbenv], [rvm], or [asdf] to install Ruby 3.
 
 If available, menus are generated by [fzf] or [gum]. If neither are available, a basic Readline menu system will be displayed, so neither are required, just nice to have as they provide fuzzy filtering, scrolling, and type-ahead completion.
 
-[homebrew]: https://brew.sh/ "Homebrew???The Missing Package Manager for macOS (or Linux)"
+[homebrew]: https://brew.sh/ "Homebrew—The Missing Package Manager for macOS (or Linux)"
 [rbenv]: https://github.com/rbenv/rbenv "rbenv/rbenv:Manage your app's Ruby environment"
 [rvm]: https://rvm.io/ "Ruby Version Manager"
 [asdf]: https://asdf-vm.com/ "ASDF environment manager"
 [fzf]: https://github.com/junegunn/fzf "junegunn/fzf:A command-line fuzzy finder"
-[gum]: https://github.com/charmbracelet/gum "charmbracelet/gum:A tool for glamorous shell scripts ????"
+[gum]: https://github.com/charmbracelet/gum "charmbracelet/gum:A tool for glamorous shell scripts 🎀"
 
 ### Installation
 
@@ -106,14 +104,14 @@ Set the `source` key to the folder where you keep your Markdown snippets. Option
 
 The `all` setting determines how Snibbets handles files containing multiple snippets. If `all` is true, then it will always display every snippet in the selected file. If false, it will offer a menu and let you choose which snippet to display. You can use `--all` on the command line to just enable this once.
 
+By default, Snibbets displays only the code from each snippet (and optionally block quotes, see below). If you set `all_notes` to true, then the full content of each snippet containing a code block will be returned, allowing you to see additional notes on the command line. This can be toggled at runtime with `--notes` or `--no-notes`.
+
 The `copy` setting determines whether the output is copied to the clipboard in addition to being displayed on STDOUT. This is the equivalent of running `snibbets QUERY | pbcopy` (macOS) or `snibbets QUERY | xclip` (Linux). This can be enabled for just one run with `--copy` on the command line. Setting it to true in the config will copy to the clipboard every time a snippet is displayed. On Mac this will work automatically, on Windows/Linux you may need to [install `xclip` or `xsel`][xclip].
 
 [xclip]: https://ostechnix.com/access-clipboard-contents-using-xclip-and-xsel-in-linux/
 
 The `editor` setting is used to open the config file, and to open snippets for editing when using the `--edit` flag. This setting can be any command line utility (`code`, `subl`, `vim`, `nano`, etc.), or on macOS it can be an application name (`BBEdit`, `VS Code`, etc.) or a bundle identifier (`com.sublimetext.4`, `com.microsoft.VSCode`, etc.). If no editor is set, then the file will be opened by whatever the system default is (using `open` on macOS, `start` on Windows, or `xdg-open`on Linux).
 
-The `highlight` key turns on syntax highlighting. This requires that either `pygmentize` or `skyligting` is available on your system (both available via package managers like Homebrew). This feature is still in development and results may be mixed.
-
 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. 
@@ -122,26 +120,48 @@ The `menus` setting will determine what method is used for displaying interactiv
 
 The `name_only` key will permanently set Snibbets to only search for snippets by their filename rather than examining their contents. You can enable this at runtime using `--name-only` in the command.
 
+#### 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. 
+
+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. 
+
+If you don't use either extensions or fenced code labels with Skylighting, code won't get highlighted.
+
+To define a snippet as python code, for example:
+
+    ```python
+    class EmlServer(SMTPServer):
+        no = 0
+        def process_message(self, peer, mailfrom, rcpttos, data):
+            filename = '%s-%d.eml' % (datetime.now().strftime('%Y%m%d%H%M%S'),
+                    self.no)
+            f = open(filename, 'w')
+    ```
+
+You can also define a color scheme with `highlight_theme`. If you're using Pygments, run `pygmentize -L styles` to see available options. If you're using Skylighting, you can reference any theme in the [KDE repository]. Skylighting themes are included in Snibbets and can be referenced by their filename without `.theme`, or you can install your own themes and reference them with a full path. (I recommend `nord` when using Sylighting.)
+
+[KDE repository]: https://github.com/KDE/syntax-highlighting/tree/master/data/themes
+
+You can turn highlighting on or off for a single run using `--highlight` or `--no-highlight`. Syntax highlighting definitely affects copyable output, so it's automatically disabled when piping/redirecting output. When using `--copy`, the code sent to the clipboard is not highlighted.
+
+##### Installing a Syntax Highlighter
+
+Snibbet's implementation of Skylighting has limited but better-looking themes, and has some lexers that Pygments lacks. However, Pygments has _more_ lexers and a wider array of themes. It also can determine the target syntax automatically better than Skylighting (which requires the syntax to be specified -- it's pulled from the extensions of your snippets), which is why Pygments is the default if it's installed and you don't configure it otherwise.
+
+- Install [Skylighting] with [Homebrew] (`brew install skylighting`) or [apt-get].
+- Install [Pygments] using [Homebrew] (`brew install pygments`) or `pip install pygments`.
+
+[Skylighting]: https://github.com/jgm/skylighting
+[apt-get]: https://installati.one/install-skylighting-ubuntu-22-04/
+[Pygments]: https://pygments.org/
+
 ### Usage
 
 ```
-Snibbets v2.0.14
-
-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
-    -o, --output FORMAT              Output format (json|launchbar|*raw)
-    -p, --paste, --new               Interactively create a new snippet from clipboard contents (Mac only)
-    -q, --quiet                      Skip menus and display first match
-    -s, --source FOLDER              Snippets folder to search
-        --configure                  Open the configuration file in your default editor
-        --[no-]blockquotes           Include block quotes in output
-        --highlight                  Use pygments or skylighting to syntax highlight (if installed)
-        --save                       Save the current command line options to the YAML configuration
-    -h, --help                       Display this screen
-    -v, --version                    Display version information
+@cli(bundle exec bin/snibbets -h)
 ```
 
 If your Snippets folder is set in the config, simply running `snibbets [search query]` will perform the search and output the code blocks, presenting a menu if more than one match is found or the target file contains more than one snippet. Selected contents are output raw to STDOUT.
@@ -175,7 +195,7 @@ Any time you specify things like a source folder with the `--source` flag, or tu
 
 _I'm currently reworking the LaunchBar action, and it doesn't function very well at this time. I'll update when I have a chance._
 
-### Installation
+<!-- ### 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. 
 
@@ -183,4 +203,5 @@ Once installed, run the action (type `snib` and hit return on the result) to sel
 
 ### Usage
 
-Type `snib` to bring the Action up, then hit Space to enter your query text. Matching files will be presented. If the selected file contains more than one snippet, a list of snippets (based on ATX headers in the file) will be presented as a child menu. Selecting a snippet and hitting return will copy the associated code block to the clipboard.
+Type `snib` to bring the Action up, then hit Space to enter your query text. Matching files will be presented. If the selected file contains more than one snippet, a list of snippets (based on ATX headers in the file) will be presented as a child menu. Selecting a snippet and hitting return will copy the associated code block to the clipboard. -->
+<!--END README-->

data/yard_templates/default/method_details/setup.rb

@@ -0,0 +1,3 @@
+def source
+  return
+end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: snibbets
 version: !ruby/object:Gem::Version
-  version: 2.0.29
+  version: 2.0.31
 platform: ruby
 authors:
 - Brett Terpstra
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2023-04-18 00:00:00.000000000 Z
+date: 2023-04-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -238,17 +238,23 @@ extensions: []
 extra_rdoc_files:
 - README.md
 files:
+- ".devcontainer/Dockerfile"
+- ".devcontainer/devcontainer.json"
+- ".editorconfig"
+- ".irbrc"
+- ".rspec"
+- ".ruby-version"
 - CHANGELOG.md
 - Gemfile
 - Gemfile.lock
-- Gemfile.lock.orig
 - LICENSE.txt
 - README.md
-- README.md.orig
 - README.rdoc
 - Rakefile
+- Snibbets.lbaction/Contents/Info.plist
+- Snibbets.lbaction/Contents/Scripts/default.js
+- Snibbets.lbaction/Contents/Scripts/snibbets.rb
 - bin/snibbets
-- buildnotes.md
 - lib/snibbets.rb
 - lib/snibbets/array.rb
 - lib/snibbets/config.rb
@@ -259,6 +265,7 @@ files:
 - lib/snibbets/menu.rb
 - lib/snibbets/os.rb
 - lib/snibbets/string.rb
+- lib/snibbets/todo_spec.rb
 - lib/snibbets/version.rb
 - lib/snibbets/which.rb
 - lib/themes/atom-one-dark.theme
@@ -287,8 +294,10 @@ files:
 - lib/themes/solarized-dark.theme
 - lib/themes/solarized-light.theme
 - lib/themes/vim-dark.theme
+- scripts/fixreadme.rb
 - snibbets.gemspec
-- snibbets.taskpaper
+- src/_README.md
+- yard_templates/default/method_details/setup.rb
 homepage: https://github.com/ttscoff/snibbets
 licenses:
 - MIT

data/Gemfile.lock.orig

@@ -1,107 +0,0 @@
-PATH
-  remote: .
-  specs:
-    snibbets (2.0.10)
-      tty-which (~> 0.5, >= 0.5.0)
-
-GEM
-  remote: https://rubygems.org/
-  specs:
-    ansi (1.5.0)
-    ast (2.4.2)
-    awesome_print (1.9.2)
-    diff-lcs (1.5.0)
-    docile (1.4.0)
-    gem-release (2.2.2)
-    json (2.6.3)
-    language_server-protocol (3.17.0.3)
-    multi_json (1.15.0)
-    parallel (1.22.1)
-    parse_gemspec (1.0.0)
-    parse_gemspec-cli (1.0.0)
-      multi_json
-      parse_gemspec
-      thor
-    parser (3.2.2.0)
-      ast (~> 2.4.1)
-    rainbow (3.1.1)
-    rake (13.0.6)
-<<<<<<< HEAD
-    rdoc (6.3.1)
-=======
-    rdoc (6.3.3)
->>>>>>> af6f234 (Update rdoc)
-    regexp_parser (2.7.0)
-    rexml (3.2.5)
-    rspec (3.12.0)
-      rspec-core (~> 3.12.0)
-      rspec-expectations (~> 3.12.0)
-      rspec-mocks (~> 3.12.0)
-    rspec-core (3.12.1)
-      rspec-support (~> 3.12.0)
-    rspec-expectations (3.12.2)
-      diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.12.0)
-    rspec-mocks (3.12.5)
-      diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.12.0)
-    rspec-support (3.12.0)
-    rubocop (1.48.1)
-      json (~> 2.3)
-      parallel (~> 1.10)
-      parser (>= 3.2.0.0)
-      rainbow (>= 2.2.2, < 4.0)
-      regexp_parser (>= 1.8, < 3.0)
-      rexml (>= 3.2.5, < 4.0)
-      rubocop-ast (>= 1.26.0, < 2.0)
-      ruby-progressbar (~> 1.7)
-      unicode-display_width (>= 2.4.0, < 3.0)
-    rubocop-ast (1.28.0)
-      parser (>= 3.2.1.0)
-    rubocop-performance (1.16.0)
-      rubocop (>= 1.7.0, < 2.0)
-      rubocop-ast (>= 0.4.0)
-    ruby-progressbar (1.13.0)
-    simplecov (0.22.0)
-      docile (~> 1.1)
-      simplecov-html (~> 0.11)
-      simplecov_json_formatter (~> 0.1)
-    simplecov-console (0.9.1)
-      ansi
-      simplecov
-      terminal-table
-    simplecov-html (0.12.3)
-    simplecov_json_formatter (0.1.4)
-    standard (1.26.0)
-      language_server-protocol (~> 3.17.0.2)
-      rubocop (~> 1.48.1)
-      rubocop-performance (~> 1.16.0)
-    terminal-table (3.0.2)
-      unicode-display_width (>= 1.1.1, < 3)
-    thor (1.2.1)
-    tty-which (0.5.0)
-    unicode-display_width (2.4.2)
-    webrick (1.7.0)
-    yard (0.9.28)
-      webrick (~> 1.7.0)
-
-PLATFORMS
-  arm64-darwin-20
-  x86_64-linux
-
-DEPENDENCIES
-  awesome_print (~> 1.9)
-  bundler (~> 2.0)
-  gem-release (~> 2.2)
-  parse_gemspec-cli (~> 1.0)
-  rake (~> 13.0)
-  rdoc (~> 6.3.1)
-  rspec (~> 3.0)
-  simplecov (~> 0.21)
-  simplecov-console (~> 0.9)
-  snibbets!
-  standard (~> 1.3)
-  yard (~> 0.9, >= 0.9.26)
-
-BUNDLED WITH
-   2.2.29

data/buildnotes.md

@@ -1,47 +0,0 @@
-template: gem, git, gli, project
-executable: na
-readme: src/_README.md
-changelog: CHANGELOG.md
-project: snibbets
-
-# Snibbets
-
-A plain text snippet manager
-
-## Develop
-
-@run(subl .)
-
-## Dummy
-
-@run(bundle exec bin/snibbets $@)
-
-## Deploy
-
-You no longer need to manually bump the version, it will be incremented when this task runs.
-
-```run Update Changelog
-#!/bin/bash
-
-changelog -u
-```
-
-@include(project:Update GitHub README)
-
-```run Update README
-#!/bin/bash
-
-changelog | git commit -a -F -
-git pull
-git push
-```
-
-@include(gem:Release Gem) Release Gem
-@include(project:Update Blog Project) Update Blog Project
-@run(rake bump[patch]) Bump Version
-
-@run(git commit -am 'Version bump')
-
-@after
-Don't forget to publish the website!
-@end

data/snibbets.taskpaper

@@ -1,14 +0,0 @@
-Inbox:
-	- handle multiple code blocks within a section separately for highlighting @maybe @na
-		If a header contains multiple snippets, create an array with a language specifier for each snippet, and then pass the array to the print function to handle individually highlighting each code block. Have a special language specifier for blockquote notes to avoid highlighting them at all.
-		Could possibly just highlight each block as its found, and save an original copy in memory for uncolored output, or just write a decoloring method. Skip highlighting if it's not enabled, but decolor ouput sent to non-tty or --copy.
-snibbets:
-	Feature Requests:
-	Ideas:
-	Bugs:
-Archive:
-Search Definitions:
-	Top Priority @search(@priority = 5 and not @done)
-	High Priority @search(@priority > 3 and not @done)
-	Maybe @search(@maybe)
-	Next @search(@na and not @done and not project = "Archive")