Support non-script based file configuration of options

Relying on profile.ps1 may not fit scenarios where we want to set-executionpolicy to ban scripts.

Would it be possible to populate options from the registry or json file? I would image modifying PSConsoleReadlineOptions is all that it takes?

[lzybkr]

Oh, @nightroman was just suggesting you still use a ps1 file like you would today, but PSReadLine would invoke it in a way that is not affected by the execution policy.

I use the following pattern in my profile to make it feel more like a configuration and less like calling a bunch of commands:

$options =
@{
    PromptText = '> '
    AddToHistoryHandler = {
        param([string]$line)
        return $line.Length -gt 3 -and $line[0] -ne ' ' -and $line[0] -ne ';'
    }
    HistorySavePath = "${env:HOMEDRIVE}${env:HOMEPATH}/PSReadLine_history.txt"
    EditMode = 'Emacs'
    ExtraPromptLineCount = 1
    Colors = @{
        Error = "$([char](0x1b))[44;91m"
    }
}
Set-PSReadLineOption @options

I suppose one option is to mimic the module manifest, basically remove the first and last lines in my example above, then apply the options. This would also need to allow specifying key bindings, maybe like:

@{
    KeyBindings = @{
        UpArrow = 'HistorySearchBackward'
        DownArrow = 'HistorySearchForward'
        'Alt+F1' = @{
            BriefDescription = 'CommandHelp'
            LongDescription = 'Open the help window for the current command'
            ScriptBlock = { ... }
        }
    }
}

[bgshacklett]

There’s precedent for this kind of configuration data in .psd1 files with DSC as well: https://docs.microsoft.com/en-us/powershell/dsc/separatingenvdata