blog'o thnet

Discussing how to add a copyright notice at each page automatically on the NanoBlogger mailing list, here are the two propositions i can think of.

It can be done by adding directly the copyright notice in the desired template files (i.e. templates/main_index.htm, etc.):

1. Either writing it in the corresponding files...

   $ diff -u templates/main_index.htm templates/main_index.htm.hardwritten
   --- templates/main_index.htm Wed Jul 6 14:49:05 2005
   +++ templates/main_index.htm.hardwritten Mon Aug 8 13:12:05 2005
   @@ -29,6 +29,10 @@
   $NB_Entries
   </div>
   
   +<div class="side">
   +All content herein © 2006, Your Company, Inc. All right reserved.
   +</div>
   +
   <div id="menu">
   $NB_PageLinks
   </div>
   

2. Or writing a little plugin to do that... (based on the plugins/fortune.sh code)

   # cat << EOF > ${NB_INST_PATH}/plugins/copyright.sh
   # NanoBlogger Copyright plugin.
   
   # sample code for templates, based off default stylesheet
   #
   # <div class="side">
   # $NB_Copyright
   # </div>
   
   PLUGIN_OUTFILE="$BLOG_DIR/$PARTS_DIR/copyright.$NB_FILETYPE"
   
   nb_msg "generating copyright ..."
   echo '<div class="copyright">' > "$PLUGIN_OUTFILE"
   echo 'All content herein © 2006, Your Company, Inc. All right reserved.' >> "$PLUGIN_OUTFILE"
   echo '</div>' >> "$PLUGIN_OUTFILE"
   NB_Copyright=$(< "$PLUGIN_OUTFILE")
   EOF
   $
   $ diff -u templates/main_index.htm templates/main_index.htm.plugin
   --- templates/main_index.htm Wed Jul 6 14:49:05 2005
   +++ templates/main_index.htm.plugin Mon Aug 8 13:12:29 2005
   @@ -29,6 +29,10 @@
   $NB_Entries
   </div>
   
   +<div class="side">
   +$NB_Copyright
   +</div>
   +
   <div id="menu">
   $NB_PageLinks
   </div>
   

The advantage of the second proposition is the capability to add a general feature using the NanoBlogger framework, and the use of the CSS to modify the new copyright class.

Reversing a file line-by-line seems not very interesting, but may be in fact very helpful in a lot of cases, especially under Unix-like systems.

Interestingly, just after reading a very good article on that particular subject from the printed edition of the Sys Admin Magazine, great known NetBSD developer Hubert Feyrer blogged about this issue... growing the proposed solution with a new method not yet given, although very simple.

All the spirit of UNIX can be found here: combined different powerful general tools to achieve a very specific task... sounds great to me.

In order to map the arrow keys to use history commands under the emacs mode with ksh(1), please put the following lines in the ${HOME}/.kshrc:

# Arrow keys to use history commands under the emacs command edition mode.
alias __A=`echo "\020"`   # mapping arrow key 'up'
alias __B=`echo "\016"`   # mapping arrow key 'down'
alias __C=`echo "\006"`   # mapping arrow key 'right'
alias __D=`echo "\002"`   # mapping arrow key 'left'
alias __H=`echo "\001"`   # mapping arrow key 'home'

There are two underline characters in alias commands.

To be able to get the PageUp and PageDown keys to work in vi(1), edit the ${HOME}/.exrc file and insert the following lines:

" Mapping PageUp & PageDown keys.
map  ^[[5~   ^B
map  ^[[6~   ^F

Note: comment begin with a " in .exrc, not a #.

How to enter the ^[[5~ character? You have to type Control+V, then press the PageUp key.

How to enter the ^B character? You have to type Control+Vn then press the Control+B keys.

As a last tip, here is how to change the prompt using working directory information. Using export PS1='${PWD} $ ', the behavior is as follow:

/home/jpeg $ cd
/home/jpeg $ cd /var/log
/var/log $

Using export PS1='${PWD##*/} $ ', the behavior is as follow:

jpeg $ cd
jpeg $ cd /var/log
log $