Skip to content

wat tour eventually has problems #47

Description

@mbforbes

Here's one issue that I got past---it appears that there's supposed to be stripColor but it's not there? I just went with supportsColor and the tour continued.

? chalk

  enabled  styles  supportsColor  readme/


  ┌────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
  |                                                                                                                                |
  |  Nice. That last tab you did shows what's in Chalk. The green items are methods, blue are properties, and the rest are         |
  |  docs, such as Chalk's readme on Github.                                                                                       |
  |                                                                                                                                |
  └────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘


  ┌────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
  |                                                                                                                                |
  |  Take a look at what's in "stripColor". You've typed half of it already.                                                       |
  |                                                                                                                                |
  └────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

? chalk stripColor

? Did you mean: chalk supportsColor

This was also kind of weird because I hadn't already typed half of it (assuming "it" refers to "stripColor").

The problem I'm stuck on now is the grepping option:

? github dthree wat
? Results: 1. GitHub - dthree/wat: Instant, central, community-built docs
     Instant, central, community-built docs. Contribute to wat development by creating  an account on GitHub....
:

  ┌────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
  |                                                                                                                                |
  |  You can also run this with "gh ..." or "readme ...".                                                                          |
  |                                                                                                                                |
  └────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘


  ┌────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
  |                                                                                                                                |
  |  Wat can also grep things! Let's have some fun:                                                                                |
  |                                                                                                                                |
  |  Run "gh awesome node -l | grep simple | less" to find some simply awesome things.                                             |
  |                                                                                                                                |
  └────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

? gh awesome node -l | grep simple | less

  Missing required option. Showing Help:

  Usage: grep [options] <pattern> [files...]


  Grep (POSIX) implementation.

  Options:

    --help                    output usage information
    -i, --ignore-case         ignore case distinctions
    -w, --word-regexp         force pattern to match only whole words
    -s, --no-messages         suppress error messages
    -v, --invert-match        select non-matching lines
    -m, --max-count <num>     stop after num matches
    -b, --byte-offset         print the byte offset with output lines
    -n, --line-number         print the line number with output lines
    -H, --with-filename       print the file name for each match
    -h, --no-filename         suppress the file name prefix on output
    -q, --quiet               suppress all normal output
    --silent                  suppress all normal output
    --include <file_pattern>  search only files that match file_pattern

?

(Awesome tool, BTW! The only other thing I've noticed is that navigating my cursor around a line of command I've typed causes the text to flicker and the cursor to jump around. This might be an underlying issue; if it's relevant / fixable, please let me know and I'll open a separate issue for it.)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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