{"action":"created","issue":{"url":"https://api.github.com/repos/tstack/lnav/issues/557","repository_url":"https://api.github.com/repos/tstack/lnav","labels_url":"https://api.github.com/repos/tstack/lnav/issues/557/labels{/name}","comments_url":"https://api.github.com/repos/tstack/lnav/issues/557/comments","events_url":"https://api.github.com/repos/tstack/lnav/issues/557/events","html_url":"https://github.com/tstack/lnav/issues/557","id":373708030,"node_id":"MDU6SXNzdWUzNzM3MDgwMzA=","number":557,"title":"viewing CSV files","user":{"login":"quadespresso","id":6423333,"node_id":"MDQ6VXNlcjY0MjMzMzM=","avatar_url":"https://avatars0.githubusercontent.com/u/6423333?v=4","gravatar_id":"","url":"https://api.github.com/users/quadespresso","html_url":"https://github.com/quadespresso","followers_url":"https://api.github.com/users/quadespresso/followers","following_url":"https://api.github.com/users/quadespresso/following{/other_user}","gists_url":"https://api.github.com/users/quadespresso/gists{/gist_id}","starred_url":"https://api.github.com/users/quadespresso/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/quadespresso/subscriptions","organizations_url":"https://api.github.com/users/quadespresso/orgs","repos_url":"https://api.github.com/users/quadespresso/repos","events_url":"https://api.github.com/users/quadespresso/events{/privacy}","received_events_url":"https://api.github.com/users/quadespresso/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-10-24T22:52:34Z","updated_at":"2018-10-25T15:16:39Z","closed_at":null,"author_association":"NONE","body":"This might be a bit of an edge case, but there do seem to be a couple knock-on effects.\r\n\r\nI have occasion to view logs which have been created on Windows 2016 Server machines where the resulting logfile is in CSV format.\r\n\r\nWhat I've observed is that while attempting to view multiple such CSV files:\r\n- only the first file (as sorted alphabetically) is opened\r\n- the lines end up double-spaced\r\n\r\nFor the second item, it looks like the `\\r\\n` end-of-line is doing this. I ran `dos2unix` against all the files, and that took care of the blank lines, at least for the first file it reads in. Let me know if you'd like me to open a separate issue for that.\r\n\r\nI was hopeful that post-conversion `lnav` would accept having all the files passed to it (since this is how I normally work with `lnav`), but no such luck. Still only reporting the first file. If I explicitly pass the path of another one of the files in question to `lnav`, it'll read it in. But only just the one file; it still ignores the rest of the files, even if all are explicitly passed.\r\n\r\n`lnav` reports that the file format is `plain text`, which is fine for now. I've had no issues slurping in multiple other files of Linux origin, and it seems to happily Do The Right Thing in those cases (even though the format may show as `plain text`). \r\n\r\nCurious, I tried various combinations of passing various logs to `lnav`, ie, some of Linux origin (which I've never had an issue with), some of Windows origin, with mixed results.\r\n\r\nFor example:\r\n\r\n```\r\nlnav */*/logs */*/eventlogs\r\n```\r\n\r\nwhere `eventlogs` contains a few CSV files of Windows origin, I'm able to view everything which matches `*/*/logs` but nothing under `*/*/eventlogs`.\r\n\r\nIf on the other hand I pass just 1 'good' file and 1 Windows CSV file, the only file which gets displayed is the CSV.\r\n\r\nI went ahead and ran it in debug mode. Looking through the debug log, it looks like the files aren't being ignored, so that's good.\r\n[lnav_init_debug.log](https://github.com/tstack/lnav/files/2512555/lnav_init_debug.log)\r\n\r\nI'm including a couple example files (brief snippets, scrubbed of anything sensitive) if you'd like something to repro with (already converted from `\\r\\n` to `\\n`). Renamed to include `.txt` extensions to allow for attaching to this issue:\r\n[app.csv.txt](https://github.com/tstack/lnav/files/2512567/app.csv.txt)\r\n[operational.csv.txt](https://github.com/tstack/lnav/files/2512568/operational.csv.txt)\r\n"},"comment":{"url":"https://api.github.com/repos/tstack/lnav/issues/comments/433091954","html_url":"https://github.com/tstack/lnav/issues/557#issuecomment-433091954","issue_url":"https://api.github.com/repos/tstack/lnav/issues/557","id":433091954,"node_id":"MDEyOklzc3VlQ29tbWVudDQzMzA5MTk1NA==","user":{"login":"quadespresso","id":6423333,"node_id":"MDQ6VXNlcjY0MjMzMzM=","avatar_url":"https://avatars0.githubusercontent.com/u/6423333?v=4","gravatar_id":"","url":"https://api.github.com/users/quadespresso","html_url":"https://github.com/quadespresso","followers_url":"https://api.github.com/users/quadespresso/followers","following_url":"https://api.github.com/users/quadespresso/following{/other_user}","gists_url":"https://api.github.com/users/quadespresso/gists{/gist_id}","starred_url":"https://api.github.com/users/quadespresso/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/quadespresso/subscriptions","organizations_url":"https://api.github.com/users/quadespresso/orgs","repos_url":"https://api.github.com/users/quadespresso/repos","events_url":"https://api.github.com/users/quadespresso/events{/privacy}","received_events_url":"https://api.github.com/users/quadespresso/received_events","type":"User","site_admin":false},"created_at":"2018-10-25T15:16:39Z","updated_at":"2018-10-25T15:16:39Z","author_association":"NONE","body":"> The double-spacing of lines is a bug that should be fixed in the top-of-tree.\r\n\r\nI'm using the build from [here](https://github.com/tstack/lnav/issues/541#issuecomment-426709888). Is the double-spacing fix more recent than that?\r\n\r\n> There's some initial support for XSV logs, but the only supported format at the moment is for the Bro network security monitor. I plan on making it more generic, but don't have a timeline.\r\n\r\nI'm not too concerned for having a ready-made formatter at this time. My main concern is that `lnav` seems to stop after encountering the first CSV file, ie, if I wanted to see any of the other files, I would need to exit `lnav` and restart it, passing the name of the next file (and just the one file) to ensure being able to view it."}}
{"actor":{"display_login":"quadespresso"}}