Difference between revisions of "Command/vskip"
< Command
Jump to navigation
Jump to search
m |
m |
||
Line 3: | Line 3: | ||
Avoid using {{cmd|vskip}} in ConTeXt. | Avoid using {{cmd|vskip}} in ConTeXt. | ||
− | The {{cmd|blank}} subsystem can deal with many spacing-related issues. The command retains information about what happened before (and might happen next); bare {{cmd|vskip}}s interfere with this mechanism. | + | The {{cmd|blank}} subsystem can deal with many spacing-related issues that {{cmd|vskip}} cannot address. The command retains information about what happened before (and might happen next); bare {{cmd|vskip}}s interfere with this mechanism. |
− | Consequently problems related to {{cmd|vskip}} | + | Consequently problems related to {{cmd|vskip}} are likely resolved by using {{cmd|blank}}. |
== See Also == | == See Also == | ||
Use {{cmd|blank}}. | Use {{cmd|blank}}. |
Revision as of 17:57, 24 February 2014
Description
Avoid using \vskip in ConTeXt.
The \blank subsystem can deal with many spacing-related issues that \vskip cannot address. The command retains information about what happened before (and might happen next); bare \vskips interfere with this mechanism.
Consequently problems related to \vskip are likely resolved by using \blank.
See Also
Use \blank.