HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
dkogan
vnlog
Perl2018–2024
dkogan / vnlog

vnlog

Process labelled tabular ASCII data using normal UNIX tools

6Distinct people
33Mentions
0Explicit recommenders
177GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Process labelled tabular ASCII data using normal UNIX tools

GitHub

Where it is used

The source check is incomplete. Verified examples will appear here.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 4:59:52 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year33 dated mentions

Observed mentions: 2018-06-15 23:31:30 UTC to 2024-02-20 02:11:42 UTC.

0369122018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 4 mentions; 2 submissions, 2 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 12 mentions; 2 submissions, 10 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 9 mentions; 2 submissions, 7 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC422
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC505
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC12210
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC110
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC927
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC110

What Hacker News says

12 sources
I use https://github.com/dkogan/vnlog/ and feedgnuplot for $WORK and it strikes a wonderful balance of simplicity and effectiveness for both quick data exploration and shell scripted data analysis and report generation. What took me a bit to grok at the start was how feedgnuplot's different flags change how it assigns semantic meaning to different data columns. So by default the first column is simply treated as data (y) while the implicit row index becomes the x axis. If you add --domain the first column becomes your domain (x) and the second column your data (y) allowing you to create a scatter plot. If you have multiple curves you can add --dataid with --domain which makes the first column x, the second column the id of the curve that point belongs to, and the third column the data itself (y). You can throw in more dimensions of visual
Read the rest
ization by mapping columns to colors, point size, or 3d. Typing it out it sounds more complicated than it really is. Combined with vnlog to easily select columns and filter rows it becomes a really powerful command line tool set.
In Feedgnuplot – plotting standard input in the shell
I have a text file in a known location. It's backed up on git. I can open and edit that file quickly using bash. From within VIM I can quickly commit to reduce the # keystrokes. More details: https://github.com/jodavaho/bashlog#git-integration (Really though, you can just save as an environment variable your file location) The text file is structured with space-delimited text, like this: https://github.com/dkogan/vnlog My current structure for tracking a contribution to an OKR item (e.g. "meditate") by date (e.g., 2020-01-15) and amount (e.g., "1") is simply: "# date item amount" Easy to open, easy to plop down today's date and the item / amount. Save multiple date/item entries and add them inscripts ... Easy to save. Done. The work came in building stuff to plot it: I have other files that link "items" to goals or other metadata like ca
Read the rest
tegories, etc. Like a relational database, but easily edited in text. For example, to make a link from daily items to Key Results "# item okr" The OKR categories are usually Fighting (I box), Tech, Mental health, and Social, but YMMV Another example is "workout-mapping.vnl" with structure: "# item muscle-group factor" etc etc. vnlog has nice vnl-join commands that quickly build the table and all linked metadata and output formatted text (one command). Then reading that in R is easy ... ``` data <- read.table('../2020-Q4-OKR.vnl',skip=2,stringsAsFactors = FALSE) ``` Aggregating by date is easy: ``` data.agg<- aggregate(x=data$Amount,by=list(data$Date),FUN=sum) ``` Then plot using ggplot2. Examples from 2020 Q4 (just ran the numbers yesterday!) https://josh.vanderhook.info/media/okr.png https://josh.vanderhook.info/media/workouts.png https://josh.vanderhook.info/media/mood.png
In Setting up personal OKR (objectives and key-results)
I've used OKR for 7 years, on a quarterly basis. I had simple markdown files at first, then vnl-log files, and now R notebooks (https://github.com/dkogan/vnlog) to read / plot. It may seem like overhead, and there's some snark in this thread about how it's project / team management without the project and team. I completely disagree. If you set up your KR's so they are 1) quantitative, 2) daily measurable, 3) simple to log ( a few keystrokes while journalling) and 4) completely under your control to achieve. At the end of the day, I mark down my progress on all my OKRs. I can quickly plot them, look back at progress, and look back at goals and concerns by seeing the types of objectives I had. It's a 10,000 foot journal that I otherwise wouldn't have. There's more to this than simply quantifying yourself. We like #'s because they are repre
Read the rest
sentations of complex systems. The self and your personal history are absolutely a complex system worth tracking. Looking back at my OKRs when I was dating my (now) wife, comparing the ways I put effort into our relationship and our changing priorities. Seeing over time my running distances, weight lifting activity, meditation record, and seeing how I consistently attempt to over-achieve by setting KR values too high ... Having those points of reference has made today more enjoyable, and been a constant reminder that progress comes slowly and missing on any particular attempt at something is irrelevant. It's so completely a part of my life now that I can't imagine setting goals or daily priorities without it. Think of it like quantitative journalling.
In Setting up personal OKR (objectives and key-results)

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.