Is cli.width an appropriate default width for rule* functions? about cli HOT 3 CLOSED

PS. I think I should be able to manage a PR if you agree.

from cli.

Hmmm, I get the idea, but I think it is hard to design cli output if the windows can have an infinite width. E.g. I want to show a list of packages, like in https://github.com/r-lib/cliapp/blob/master/inst/scripts/search.R which looks like this:

❯ ./search.R  command line
ℹ Searching...
✔ Found 60 packages in 23ms

1. optparse 1.6.0 -- Command Line Option Parser

  A command line parser inspired by Python's 'optparse' library to be used with
  Rscript to write "#!" shebang scripts that accept short and long
  flag/options.

  3 months ago by Trevor L Davis <[email protected]>

2. colt 0.1.1 -- Command-Line Color Themes

  A collection of command-line color styles based on the 'crayon' package.
  'Colt' styles are defined in themes that can easily be switched, to ensure
  command line output looks nice on dark as well as light consoles.

  about a year ago by Stefan Fleck <[email protected]>

[...]

cliapp uses cli.width to wrap the description here. It does not seem very nice to show the package description in one long line here, does it? In other words, I don't really see that rules are that special that they need an option. Quite often you want to cut/wrap everything at cli.width, I think.

I see the use case for tibbles (and tables in general?), though, so maybe it is better to go the other way and have a tibble.width option. Assuming there isn't one already.

from cli.

• Deleted Response *

Edit: So I just figured out I can set cli.width and width and get the best of both worlds. As you were. Really sorry for wasting your time.

from cli.