org-columns
) ¶Turn on column view. If point is before the first headline in the
file, column view is turned on for the entire file, using the
‘#+COLUMNS’ definition. If point is somewhere inside the outline,
this command searches the hierarchy, up from point, for a ‘COLUMNS’
property that defines a format. When one is found, the column view
table is established for the tree starting at the entry that
contains the ‘COLUMNS’ property. If no such property is found, the
format is taken from the ‘#+COLUMNS’ line or from the variable
org-columns-default-format
, and column view is established for the
current entry and its subtree.
org-columns-redo
) ¶Recreate the column view, to include recent changes made in the buffer.
org-columns-quit
) ¶Exit column view.
Move through the column view from field to field.
Directly select the Nth allowed value, 0 selects the 10th value.
org-columns-next-allowed-value
) ¶org-columns-previous-allowed-value
)Switch to the next/previous allowed value of the field. For this, you have to have specified allowed values for a property.
org-columns-edit-value
) ¶Edit the property at point. For the special properties, this invokes the same interface that you normally use to change that property. For example, the tag completion or fast selection interface pops up when editing a ‘TAGS’ property.
org-columns-toggle-or-columns-quit
) ¶When there is a checkbox at point, toggle it. Else exit column view.
org-columns-show-value
) ¶View the full value of this property. This is useful if the width of the column is smaller than that of the value.
org-columns-edit-allowed
) ¶Edit the list of allowed values for this property. If the list is found in the hierarchy, the modified values is stored there. If no list is found, the new value is stored in the first entry that is part of the current column view.