Comments on: Some Crux ports for console clocks

By: scott

scott — Mon, 12 Jul 2010 19:07:00 +0000

Sorry for rambling. I’m still learning about tput. Using this

tput setf 1

would be a more portable way to set the text color to blue instead of using echo as I did above.

Also since the cursor is distracting and unnecessary, your script could use tput to hide the cursor with

tput civis

(You can un-hide the cursor again with “tput cnorm”)

By: scott

scott — Mon, 12 Jul 2010 18:29:57 +0000

I am truly honored to have “ticker” mentioned in one of your articles You mentioned wishing it could do color. I was tempted to start adding special codes to add color, or pause, or vary the speed. But then I thought, keep it simple, you can do those things from the shell.

So, for example, you could use a while loop to update the time every 20 seconds or so (like ticker-clock does), but then every 15 times through the loop (5 mins) you could call

echo -e “\x1b[0;34m”

to turn the color blue (vt100), then pipe the output of some other script (like a weather forecast, or remind) to a new invocation of ticker to scroll the message. You could change the color to reflect the content of the message. Likewise, you can vary the speed by invoking ticker multiple times with different -d parameters. You can “pause” by calling sleep(1) between calls to ticker. If you know the height of your screen (e.g. use LINES=`tput lines`) you can scroll a message completely off the screen with

ticker -l $LINES “”

I tried to make it as light as possible so you could string together multiple calls to it in a script with minimal drain on resources. That’s why I embedded the glyphs right in the source, rather than loading them from a file. But I will think about adding an option to load an alternate “font” from a file someday. In the meantime, if you know some C it is really pretty easy to tweak the look of a glyph. There are no dependencies, so its dead simple to recompile (see the Makefile).

By: K.Mandla

K.Mandla — Sun, 11 Jul 2010 21:37:55 +0000

I sort of did, a couple of years ago. If you follow the Projects link at the top of the page, you’ll find Ubuntu GTK1.2 Remix, which was something I set up for myself, and later shared.

I don’t really support it any longer, mostly because my own philosophy on software setups has changed. But it’s still there and will still be usable for as long as the Hardy repos are online. You could give it a try if you like; I still seed the ISO and sometimes still get questions about it.

Aside from that though, I don’t have any plans to mastermind my own distro. I feel like the system I would build is already available, in the form of Arch or Crux or a console-only Debian system. I would just be duplicating efforts, and I have so little time as it is.

Nope, no KMandlux in the future. Sorry.

By: Prinzzchavo

Prinzzchavo — Sun, 11 Jul 2010 10:47:15 +0000

As far as the comments go, we all have more real-life-commitments on summertime.

As always, a very inspiring post(I’m starting to have CLI dreams, really), but my question is:

Have you ever considered creating your own Distro?

As far as I can see, from the way you almost always achieve your goal (Building up instead of tearing down, Porting from AUR to Crux…), you might actually have, by now, a complete OS of your own, something like a Kmandlux…hehehe