Skip to content

Failed to Install 0.4.0 #3

@plus7wist

Description

@plus7wist

I have tried to install this from cargo:

cargo install -f glint --version 0.4.0

cargo tells me:

error[E0599]: no method named `ansi_code` found for type `crossterm_terminal::Clear` in the current scope
   --> /home/xxxxxx/yyyyyyyyyyyyyyy/glint-0.4.0/src/term_buffer.rs:135:9
    |
135 |         ct::queue!(self.stdout, ct::Clear(ct::ClearType::UntilNewLine)).unwrap();
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ method not found in `crossterm_terminal::Clear`
    |
    = help: items from traits can only be used if the trait is in scope
    = note: the following trait is implemented but not in scope; perhaps add a `use` for it:
            `use crossterm_utils::command::Command;`
    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

error[E0599]: no method named `ansi_code` found for type `crossterm_terminal::Clear` in the current scope
   --> /home/xxxxxx/yyyyyyyyyyyyyyy/glint-0.4.0/src/term_buffer.rs:211:9
    |
211 |         ct::queue!(self.stdout, ct::Clear(ct::ClearType::FromCursorDown)).unwrap();
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ method not found in `crossterm_terminal::Clear`
    |
    = help: items from traits can only be used if the trait is in scope
    = note: the following trait is implemented but not in scope; perhaps add a `use` for it:
            `use crossterm_utils::command::Command;`
    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0599`.
error: failed to compile `glint v0.4.0`, intermediate artifacts can be found at `/tmp/cargo-installSp1q2u`

Caused by:
  could not compile `glint`.

The same error occors if I clone this repo, checkout tag 0.4.0, and run cargo install --path ..

But, it's ok to build that tag use cargo build --release. I don't understand why that happened. Can anyone help me?

I am using cargo version cargo 1.40.0 (bc8e4c8be 2019-11-22).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions