HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
doches
progressbar
C2015–2015
doches / progressbar

progressbar

An easy-to-use C library for displaying text progress bars.

2Distinct people
3Mentions
0Explicit recommenders
474GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

An easy-to-use C library for displaying text progress bars.

GitHub

Where it is used

No documented product use has been verified yet.

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

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM 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 hour3 dated mentions

Observed mentions: 2015-08-29 01:42:31 UTC to 2015-08-29 05:18:25 UTC.

012015-08-29 01:00:00 UTC to 2015-08-29 02:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsAug 29, 01:002015-08-29 02:00:00 UTC to 2015-08-29 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-08-29 03:00:00 UTC to 2015-08-29 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 29, 03:002015-08-29 04:00:00 UTC to 2015-08-29 05:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2015-08-29 05:00:00 UTC to 2015-08-29 06:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 29, 05:00

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
Aug 29, 01:002015-08-29 01:00:00 UTC2015-08-29 02:00:00 UTC110
Aug 29, 02:002015-08-29 02:00:00 UTC2015-08-29 03:00:00 UTC000
Aug 29, 03:002015-08-29 03:00:00 UTC2015-08-29 04:00:00 UTC000
Aug 29, 04:002015-08-29 04:00:00 UTC2015-08-29 05:00:00 UTC101
Aug 29, 05:002015-08-29 05:00:00 UTC2015-08-29 06:00:00 UTC101

What Hacker News says

3 sources
https://github.com/doches/progressbar/blob/master/lib/progre... The correct solution would be a) check the length of format, and if it less than or equal to 4 but greater than 0, then copy the bytes, else, don't... I guess? Why is 4 such an arbitrary chosen number? // new->format is allocated to 4 bytes size_t len = strlen(format); if(len > 0 && len <= 4) { memcpy(new->format, format, len); //i to < 4 new->format[3] = '\0'; } Or it just be better to allocate the new->length to the return value of strlen(format) + 1.
In Show HN: Progressbar - A C library for displaying command-line progress bars
Consider checking the return value of malloc (e.g: https://github.com/doches/progressbar/blob/master/lib/progre...) You're setting users/yourself up for a disaster if you're assuming it will never fail. The standard [0] states that the size of `char` will be 1 byte. So there is no point in doing the sizeof operator on char. (e.g: https://github.com/doches/progressbar/blob/master/lib/progre...) 6.5.3.4 - Paragraph 3 > The sizeof operator... (page 80) [0] http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1124.pdf
In Show HN: Progressbar - A C library for displaying command-line progress bars

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.