Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

*Refactor output width calculations | PERFORMANCE, OUTPUT AESTHETICS #23

Open
fstab50 opened this issue Jul 28, 2019 · 0 comments
Open
Labels
bug Something isn't working enhancement New feature or request

Comments

@fstab50
Copy link
Owner

fstab50 commented Jul 28, 2019

when examining all paths which contain count targets, xlines should be modified to:

  1. Trace | Test | Gather: all paths while performing an inline test to determine if a particular path/target should be included/ excluded. This must be done upfront as is current; prior to performing any line counts on targets.

  2. The set resulting from (1) will be the actual paths counted and displayed in output. Currently screen width accuracy is poor due to long paths used in the calculation of width, but later excluded as containing invalid count targets (binary formats).

@fstab50 fstab50 added bug Something isn't working enhancement New feature or request labels Oct 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant