NEOFLUX-IMPORT(1) User Commands NEOFLUX-IMPORT(1)

neoflux-import - convert a Fluxbox configuration to native NeoFlux TOML

neoflux-import [--dry-run] [--force] [--in dir] [--out dir]

neoflux-import is a one-shot converter that reads an existing Fluxbox configuration directory and writes the equivalent NeoFlux files. You run it once when migrating from Fluxbox; the window manager itself never invokes it.

It reads the Fluxbox init file first to pick up general settings and the referenced file paths (keyFile, menuFile, slitlistFile, styleFile), then converts:

  • init — general settings and file references.
  • style — the active style file becomes a NeoFlux theme (title-bar colours and gradient, border colours, and any window.*.pixmap button images).
  • keys — keyboard bindings.
  • menu — the root-menu launcher entries.
  • slitlist — dockapp order for the slit.
  • apps — per-window rules.

The results are written to the destination directory as config.toml, keys.toml (the key bindings), menu.toml (the root menu, with its submenus kept), themes/<style>.toml, and (if any dockapps were listed) slitlist. Bindings and menu go into their own files because neoflux loads keys.toml and menu.toml after config.toml: anything put in config.toml would be overridden by the files neoflux seeds on first start. A converted keys.toml replaces neoflux's default bindings wholesale; the defaults remain available in defaults/keys.toml. With no usable bindings or menu entries in the source, that file is not written and neoflux's own stays. A missing source file is simply skipped. After running, a conversion report is printed: how many bindings, menu entries, and dockapps were emitted; the outcome for each source file; and any notes or skipped items.

By default existing destination files are not overwritten — pass --force to replace them, or --dry-run to preview without writing anything. The exception is a file still exactly as neoflux seeded it (config.toml, keys.toml, menu.toml): that holds none of your work and is replaced without --force, so importing right after a first start of neoflux just works. Check the result with neoflux --check-config.

Print the converted config.toml, keys.toml, menu.toml, theme and slitlist, plus the report, to standard output and write nothing.
Overwrite existing files in the destination directory.
Source Fluxbox configuration directory. Default: ~/.fluxbox.
Destination NeoFlux configuration directory. Default: $XDG_CONFIG_HOME/neoflux, falling back to ~/.config/neoflux.
Print a usage summary and exit.

0
Success (including a dry run).
1
A destination file could not be written, or already exists and --force was not given.
2
A bad command-line argument, or the input directory does not exist.

Preview the conversion without touching anything:

neoflux-import --dry-run

Convert ~/.fluxbox into ~/.config/neoflux, replacing any files already there:

neoflux-import --force

Convert a non-standard location:

neoflux-import --in ~/old/fluxbox --out ~/.config/neoflux

~/.fluxbox/
Default source directory (init, keys, menu, apps, slitlist, and the active style).
~/.config/neoflux/config.toml
~/.config/neoflux/keys.toml
~/.config/neoflux/menu.toml
~/.config/neoflux/themes/<style>.toml
~/.config/neoflux/slitlist
Default destination files.

neoflux(1), fluxbox(1)

neoflux is developed by Chris (OsugiSakae).

November 21, 2026 neoflux 0.6.1