Settings now preserved when switching profiles around.
This commit is contained in:
parent
0884bc0f98
commit
0f7d050f10
6 changed files with 5 additions and 4 deletions
|
@ -7,6 +7,9 @@ You now no longer have to fiddle with configuration options in the various
|
|||
`docs/` and the new `_configuration` command sections of the individual profiles
|
||||
for details.
|
||||
|
||||
Settings will only be saved in the profile you have selected when changing them,
|
||||
but be preserved if you switch around.
|
||||
|
||||
This also means that importing the profiles and updating them has become easier
|
||||
on you, the user.
|
||||
|
||||
|
|
|
@ -95,10 +95,8 @@ Basically all the settings are available using the `customize settings` prefix,
|
|||
then saying `[enable;disable] <setting>` for on/off switches and `set <setting>`
|
||||
for text variables.
|
||||
|
||||
One caveat applies: settings are stored in the _profile where you run the
|
||||
configuration commands_. If you change your active, main profile around a lot
|
||||
you’ll have to set everything up for each of them separately. I suggest instead
|
||||
having a single “main” profiles and including everything else.
|
||||
One caveat applies: settings will only be saved in the profile you have selected
|
||||
when changing them, but be preserved if you switch around.
|
||||
|
||||
## Using a Profile ##
|
||||
|
||||
|
|
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Loading…
Reference in a new issue