Struct RenderedGrid 

pub struct RenderedGrid {
    pub lines: Vec<String>,
    pub spans: Vec<Vec<GridSpan>>,
}

The laid-out popup: lines to write, and where the keys are.

The spans come from the LAYOUT rather than from re-scanning the rendered text, and that is the point: this function knows the byte offset it wrote each key at, while a scanner would have to guess which run of a padded row was a key. magit/highlight.rs carries a note about exactly that hazard — a refs row cannot be scanned back unambiguously, so its producer emits spans directly. Same rule here, applied before the ambiguity can arise.

Fields

lines: Vec<String>

The popup’s text, one entry per line: header, grid rows, then any footer lines. Written into the popup buffer verbatim.

spans: Vec<Vec<GridSpan>>

One entry per line in lines, same order. Empty vectors for lines with nothing to emphasise.

Implementations

impl RenderedGrid

pub fn is_empty(&self) -> bool

No lines — the model was empty or the pane too narrow, and the caller suppresses the popup.

Trait Implementations

impl Clone for RenderedGrid

fn clone(&self) -> RenderedGrid

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for RenderedGrid

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for RenderedGrid

fn default() -> RenderedGrid

Returns the “default value” for a type.