As of 2016-02-26, there will be no more posts for this blog. s/blog/pba/
Showing posts with label history. Show all posts

Ive been thinking about grow light and aquaponics, not about doing those, but why people use them to grow. I began to realize its not just about the light, the fish, or the science and technology. It might have nothing with those, only you want to see things still growing in the winter time, because without those plants, there seems to be something missing in your life.

More than ten years ago, I bought a bag of blue light LED and from what I read, its for growth red for flowering there must be around 50 LEDs. Ill be trying on a tomato plant to see if it works with just a few, it that works, I might add more LEDs for more plants.

Also, a fish and a pump, which might just air pump. I am thinking I could use styrofoam to attach a plant, so it can float on water, then put the pump pipe right below the roots, so the roots can have oxygen. Not sure if this will work, because every aquaponics seems to have a grow bed.

Ever since I turned back on Google search history, I probably visit at least once a day to delete keyword with typos. Some people delete embarrassing searches, I delete typos. Its not always as if I dont know how to spell, sometimes, my fat fingers get in the way, or interfered with Pentadactyl commands.

Have you ever written a long and fancy long shell one-liner, execute it, then an error due to a silly typo sitting in the middle of that command? Or you just need to compose a command which you know will be long before its written?

You can always create a file, but sometimes, its a one-time only task. So, is there any way to get the job done easily? Of course, there is and more than one method.

1   Substitution

For fixing a typo in a command you just type, you can use history expansion:

$ typo bash
-bash: typo: command not found
$ ^typo^type
type bash
bash is /bin/bash

or using fc:

$ fc -s typo=type

or substituting other than last command:

$ !-3:s/foo/bar/

The command above substitutes foo with bar in the third previous command.

2   Editing

If you just run fc, then it brings your editor up and feed it with last command. You can even give fc a range, so you can edit a list of commands at once:

$ fc -5 -3

You will have commands from 5th previous command to 3th previous command in your editor. If you are not sure the numbers, you can use -l option to get a numbered list, then issue the command with according numbers:

$ fc -l
$ fc 100 105

Another easier way to edit current command in Bash is to press Ctrl+X then Ctrl+E, or Esc then V if Vi mode enabled.

I somehow I stumbled upon this thread, I thought I should try to build one.

I began to think what program can do this then GNU/Linux distro timeline showed me the light, a project called gnuclad. I downloaded gldts source, I started to write with my entries.

Here is what I have now

Its still a mess, many still missing, dates probably incorrect. Its really hard to recall when you had used something after so many years.

The first program came up in my mind is not gnuclad, but Graphviz, I found this pdf. The last page is a timeline, but it doesnt have a source code and gnuclad generates prettier result.

I have never heard of gnuclad, so I am still learning, the final timeline will take me a very long time to produce. Once I finish, I will release my code since I derivate mine from a GFDL work.