Skip to content

Preprocessor & Postprocessor Configs

Jump to bottom
William Young edited this page May 12, 2018 · 5 revisions

Preprocessor configs are loaded from the file as the file is processing, this means that they will be affected by conditionals. Preprocessor configs take effect immidiatly, and do not affect any lines before.

Preprocessor configs have the syntax

#@config=value

scripts-enabled

This sets wether or not to run scripts when they show up, 0 will cause scripts and insertions to not run and choose their default output if set. Any non 0 setting (normally 1) will cause scripts to run normally

Default is 1

#@scripts-enabled=1

output-comments

Options

  • None - comments will be output with just the comment-character prepended
  • Spaced - comments will be output with the comment-character and a space prepended
  • Chars - comments will be output with the comment-character and the second argument prepended.

Default is None

#@output-comments=Chars;#-->

this setting will cause commented lines to appear like this

# some existing comments
some enabled line
#-->some disabled line

section-style

Section style changes the formatting of the output of section headers. The output format IS affected by output-comments setting, and the comment-character setting.

See 'Special Directives' page for information about Section Headers

Options

  • None - The section headers will not be output to the file
  • Line - The section headers will be output as just a normal comment
  • Padded - The section headers will be output with an empty comment line above and below it
  • Box - The section headers will be output in boxes (this assumes the use of mono-spaced fonts)

Default is Line

#@section-style=Box

Line Style Sections

# Section Name

Padded Style Sections

#
# Section Name
#

Box Style Sections

################
# Section Name #
################

Postprocessor Configs

Postprocessor configs are loaded from the file as the fil esi processing, this means that they will be affected by conditionals. Postprocessor configs take effect after the file is finished processing. The last set value will always be the only one used for any postprocessor config and they do not take effect until the file is completely processed and affect all lines of the file.

Posprocessor configs have the same syntax as preprocessor configs

#@config=value

output-location

output location indicates the location in the filesystem that the file should be saved. you can use ~ to refer to the current user's homefolder, and . to refer to the working directory UDP was run from. If the file resides in a folder that dose not exist on the system the user will be prompted if they would like to create the folder, or abort generating the config

Default is ./compiled configs/<#config-name#> and will automatically create the folder without prompting.

#@output-location=~/.vimrc

output-rotation

output rotation indicates wether the output files should overwrite the existing config, or rotate the existing confing out (eg .zshrc becomes .zshrc.backup1 in the same folder). This can be set to any number indicating the number of backups to keep. Setting this to zero will cause the feature to be disabled and the config will be overwriten in place with no backup.

Default is 0

#@output-rotation=2
Clone this wiki locally