This commit changes @is_enabled to only be assigned true or
false.

This commit changes the behavior so that if @is_enabled was
originally true and what is passed to enabled= is truthy,
it does nothing.

With this commit, simply writing `hook "auxin:fifo:30"` will
now automatically generate a new data source "auxin:fifo:30".

Future changes may allow for similar things to be done with
data sources other than auxin.

This commit adds new class OutvokeDataSourceAuxinFifo.

This is unfinished.

To try this version for now:

  1. launch Outvoke as follows.

    $ ./outvoke.rb -e 'hook /auxin/'

  2. In another terminal, do the following.

    $ seq 11 15 > .outvoke.auxin.1.fifo

This commit is related to 04be13b4.

In a block passed to hook, the first argument to loputs now
defaults to e instead of the empty string.

Previously, the value returned by the block passed to hookcc
was simply ignored.

With the introduction of “post_proc_cc” this value can now be
used later.

post_proc_cc is an array for storing Proc objects, with one Proc
stored by default. This Proc is similar to the one registered by
default in post_proc.

This is a disruptive change. In scripts using Outvoke, code that
expects the value returned by the block passed to hookcc to
simply be ignored may behave differently than before.

You don't need to worry too much about this disruptive change if
the block passed to hookcc ends with loputs. Because loputs
returns nil.

With this commit, the argument passed to post_procs will be
changed from event.body to event itself.

This bug appeared in version 0.0.99.20241214 (fa174d9e).

This commit provides a new feature "hookccft".

hookccft is a version of hookft that runs in a separate thread.

This commit is related to 33e6db51.

For msgid, it has been changed to be unique within the Outvoke
object rather than unique within the data source.

OutvokeDataSource#generate_new_msgid has been removed and
Outvoke#generate_new_msgid has appeared instead.

register_proc appeared in version 0.0.99.20241113 (33e6db51).

This commit is related to 0fa405cb.

With this commit, you can now write:

  $ seq 1 30 | ./outvoke.rb -q -e 'hookstd(/0/){ "num: #{e}" }'

Previously, it was necessary to use e.body as follows:

  $ seq 1 30 | ./outvoke.rb -q -e 'hookstd(/0/){|e| "num: #{e}" }'

This commit is slightly related to f2404eaa.

The OutvokeEvent class is a subclass of the String class.

With this commit, you can now write:

  $ seq 1 30 | ./outvoke.rb -q -e 'hookstd(/0/){|e| "num: #{e}" }'

Previously, it was necessary to use e.body as follows:

  $ seq 1 30 | ./outvoke.rb -q -e 'hookstd(/0/){|e| "num: #{e.body}" }'

This bug appeared in version 0.0.99.20241114 (b287c6db).

e.is_quiet_mode is deprecated.

This commit is related to b209dfd5.

This commit adds simple web server functionality.

It is more for one-liners.

If the ring method is defined in outvoke.conf.rb and port 8080
is free, then if you start Outoke as follows and then access
lodalhost:8080 via HTTP, you will hear a sound each time you
access.

  ./outvoke.rb -e 'hookweb{ring}'

It may be more convenient to do it as follows:

  ./outvoke.rb -e 'hookweb{ring; "ok"}'

The following example displays the request headers in an
easy-to-read format.

  ./outvoke.rb -e 'hookweb{ _1.req.header.to_yaml }'

You can change the port by doing the following outside the
block passed to the hook.

$outvoke["web-001"].port = 8081

You can also put the above line in outvoke.conf.rb.

The data source “web-001” uses the following features recently
added to Outvoke:

  - post_procs (20f8d9c1)
  - attachment (d558e477)
  - msgid (0c1a0563)
  - new instance variable "ds" (835cc873)
  - new instance variable "outvoke" (bf184875)
  - OutvokeDataSource#generate_context (698e59bc)

This commit is also related to 1c328546 which changed to use
Object#to_yaml instead of Marshal.#dump. Because both
WEBrick::HTTPRequest objects and WEBrick::HTTPResponse objects
cause errors when Marshal.#dump.