Replies: 10 comments 1 reply
-
|
I don't know yet. https://github.com/noborus/ov/blob/master/docs/image.md#column-mode-toggle-c |
Beta Was this translation helpful? Give feedback.
-
|
The highlighting works on the left.
Lars
Am Di., 11. Aug. 2020 um 06:46 Uhr schrieb Noboru Saito <
notifications@github.com>:
… I don't know yet.
It worked with me.
https://github.com/noborus/ov/blob/master/docs/image.md#column-mode-toggle-c
Does the highlight do not work on the left or right?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#21 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMGOCGBUUWQY6U5OKDWAFALSADEJHANCNFSM4P2T5RMA>
.
|
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
ls -l won't work because the delimiter will be multiple spaces. |
Beta Was this translation helpful? Give feedback.
-
|
I don't think that PR will resolve this. Parsing tabular data accurately and correctly is not even always possible, since they may be ambiguity. But it's still worth to try our best, because there are so many Linux/Unix command line tools that produce it (and are not able to produce csv or json, sadly). The README actually claims:
which made me think it can actually parse tabular data. |
Beta Was this translation helpful? Give feedback.
-
|
A simple example of how tabular data can be ambiguous: Are date and time in the same column or two different columns? Or even worse: We don't know if date is one column or 3 columns by just looking at padding/alignment. It may not matter much in some cases, but in some other unlucky cases, it can be important. |
Beta Was this translation helpful? Give feedback.
-
I think it is unreasonable. Anyway, vertical alignment is difficult to parse. |
Beta Was this translation helpful? Give feedback.
-
|
I think in the context of command line (and not spreadsheets), vertical alignment is part of tabular output/data, because command line output is generally meant for viewing, searching or filtering (with grep/sed), not parsing. Formats like csv and tsv are also tabular, but they are mostly spreadsheet-oriented I think. Ideally all commands that print tables should be able to produce csv, tsv or json by giving a flag, but that's very far-fetching. |
Beta Was this translation helpful? Give feedback.
-
|
My reply remains unchanged, just repeating, but converted to discussions. |
Beta Was this translation helpful? Give feedback.
-
|
The support for tabular data is one of my favorite features of ov. I've been creating view modes for lots of specific stuff and amassing quite a wishlist of features. Relating to column mode, it would be cool to support tables when there's also the presence of non-tabular data. It always bothered me how fstab is supposed to be a table but is always sloppily and confusingly formatted. Thank to ov and some preparation this is no longer an annoyance.
This required removing all comments from the file and some light text processing to turn repeating spaces into single tabs. I assume it would be way too complex for little gain, but being able to ignore comments, or maybe being able to define specific ranges for tabulation, would be helpful in my current goal of pretty printing and paging all the things. Commonly there's files or command outputs that are ripe for formatting and would require little or no preprocessing, if not for some small thing such as notifications messages sent along to STDIN , or comment strings. |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Table switch -c has no effect, file content is just displayed as usal (e.g. by calling "ov -c -d: /etc/passwd"). Using ov Version 0.4.0. Same effect with $HEAD. Distro is Mint 19.3.
Originally posted by @larsklemstein in #5 (comment)
Beta Was this translation helpful? Give feedback.
All reactions