How does a minimal configuration with Wrap enabled look like? #439
Replies: 1 comment 4 replies
-
Wrapping is globally enabled in default configuration. It is only disabled in the Logs app. Currently there is a global wrap parameter and specifically for <config>
<menu selected=Term item*>
<item id=Term>
<config>
<term>
<scrollback>
<wrap="on" /> <!-- Specific for id=Term (overrides global) -->
</scrollback>
</term>
</config>
</item>
</menu>
<term> <!-- Global config for all terminal apps -->
<scrollback>
<wrap="on" /> <!-- Global wrap for all unspecified -->
</scrollback>
</term>
</config> It seems that the parameters of pre-configured menu items cannot be changed. The only way is to create your own list of menu items. Apparently I have to remove additional reconfiguration for Minimal config: <config>
<menu selected=Term1 item*>
<item id=Term1 /> <!-- This item inherits the global <config/term/> by default -->
<item id=Term2 > <!-- This item inherits the global <config/term/> and merges specific -->
<config>
<term>
<scrollback wrap=1 />
</term>
</config>
</item>
</menu>
<term> <!-- <config/term> inherits all default setting but wrap=0 -->
<scrollback wrap=0 />
</term>
</config> Note that console applications can trigger the wrap option using the following vt sequences: UPDATE: <config>
<menu>
<item id=Term>
<config>
<term>
<scrollback wrap=1 />
</term>
</config>
</item>
</menu>
</config> |
Beta Was this translation helpful? Give feedback.
-
Can I enable Wrap without adding a full config file? From the minimal config is it possible to enable wrap?
I have tried the next minimal version with wrap enabled but that value is not taken.
On the other hand I do not want to override all other default settings with an explicit configuration.
Is there some middle ground?
Beta Was this translation helpful? Give feedback.
All reactions