Struct termion::cursor::Goto

pub struct Goto(pub u16, pub u16);

Goto some position ((1,1)-based).

Why one-based?

ANSI escapes are very poorly designed, and one of the many odd aspects is being one-based. This can be quite strange at first, but it is not that big of an obstruction once you get used to it.

Example

extern crate termion;

fn main() {
    print!("{}{}Stuff", termion::clear::All, termion::cursor::Goto(5, 3));
}

Tuple Fields

0: u16

1: u16

Trait Implementations

impl Clone for Goto

fn clone(&self) -> Goto

Returns a copy of the value.

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

Performs copy-assignment from source.

impl Default for Goto

fn default() -> Goto

Returns the “default value” for a type.

impl Display for Goto

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

Formats the value using the given formatter.

impl From<Goto> for String

fn from(this: Goto) -> String

Converts to this type from the input type.

impl PartialEq for Goto

fn eq(&self, other: &Goto) -> bool

This method tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

This method tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Copy for Goto

impl Eq for Goto

impl StructuralPartialEq for Goto