Variable: sops--example-txt

sops--example-txt is a variable defined in sops.el.

Value

"hello from emacs sops-mode!\n"

Documentation

Plain-text stub seeded into new .txt buffers by sops-find-file.

.txt files use sops's native binary store: the whole buffer is
encrypted as a single blob (not parsed as yaml/json/etc.), so no sops-input-type-overrides configuration is required by default.

If you prefer structured content for .txt (yaml-shaped keys with selective encryption), map the path to "yaml" in sops-input-type-overrides; sops-mode then auto-threads
--output-type yaml (via sops--maybe-output-type) to work around
upstream sops's binary-store fallback (see getsops/sops#235).

Source Code

;; Defined in /nix/store/vihl6lkzddv9xrsrsznvqdjq27g2i30p-emacs-packages-deps/share/emacs/site-lisp/elpa/sops-20260920.2121/sops.el
(defconst sops--example-txt
  "hello from emacs sops-mode!
"
  "Plain-text stub seeded into new `.txt' buffers by `sops-find-file'.
`.txt' files use sops's native binary store: the whole buffer is
encrypted as a single blob (not parsed as yaml/json/etc.), so no
`sops-input-type-overrides' configuration is required by default.

If you prefer structured content for `.txt' (yaml-shaped keys with
selective encryption), map the path to \"yaml\" in
`sops-input-type-overrides'; sops-mode then auto-threads
`--output-type yaml' (via `sops--maybe-output-type') to work around
upstream sops's binary-store fallback (see getsops/sops#235).")