slipcase-open 0.1.7

Open the payload of a Slipcase container in its own application, and write edits back into the container
Documentation
# Machine policy for slipcase-open, installed at /etc/slipcase/open.toml.
#
# Concept 10. This is the highest layer on Linux: root-owned, and taking
# precedence over the user's own configuration at
# $XDG_CONFIG_HOME/slipcase-open/policy.toml. There is no per-user *policy*
# layer here, because Linux has no mechanism that would administer one.
#
# Shipped saying nothing. Every key is optional, and a key that is absent means
# this layer has no opinion about it rather than that it forbids everything —
# so an untouched file leaves the built-in set in force. Uncomment what you mean
# to set.
#
# The set of payload extensions that may be opened. Compared with ASCII case
# folded, and an extension that is not ASCII alphanumeric cannot be allowlisted
# at all: the shell folds ASCII and nothing more, and a rule this tool could
# match but the shell could not would permit one thing and open another.
# allowed = ["pdf", "docx", "xlsx", "odt"]

# Whether `allowed` replaces the built-in set or is added to it. Must be said
# out loud: an administrator who writes a list expecting it to be exhaustive and
# instead gets it unioned with the defaults has a silent hole. "replace" is the
# default when the key is absent.
# mode = "replace"

# Always wins, over every other setting and over the user. Folded the same way
# as `allowed`, and reaching the same set: nothing should be refusable by a rule
# the allow list could not have expressed.
# denied = ["exe", "dll", "scr", "js"]

# Whether the user's own additions are honoured at all.
# user_may_extend = false

# Ask before each write-back rather than repacking as the payload is saved. Off
# by default; on for archival use.
# confirm_each_write_back = false

# How much the tool says without being asked.
#
#   "important"   warnings, failures, questions, and the answer to anything you
#                 did. The default.
#   "everything"  the above, plus what happens on its own — a notification for
#                 every write-back rather than for the first of a session.
#
# Nothing here can silence a question. A session waiting on a decision is asked
# through a different path entirely, so no setting can quieten one into leaving
# a payload stranded.
#
# The desktop's own per-application notification settings are the blunt version
# of this and are not ours to duplicate: GNOME, Windows and macOS can each turn
# this application off outright. What this key is for is the middle ground none
# of them can express.
# notify = "important"