mirror of
https://codeberg.org/scip/note.git
synced 2025-12-17 12:41:10 +01:00
CHANGED: does no more use the external touch command to create a new
file, use perls open() instead.
CHANGED: excluded some of the help texts from the usage message and the
interactive help command to a manpage.
ADDED: new commandline flag "--encrypt" which one can use to encrypt
the mysql database password. This will be decrypted before
connecting to the db. There is also a new config file option
"encrypt_passwd" which indicates an encrypted db-password.
ADDED: another new config option "ShortCd", which can be set to "yes"
or 1 and if set, then a command like "cd 13" would jump
directly to the topic of the note with the number 13.
ADDED: now you can at any time cd back to the "root" of the
topic-structure using the command "cd /".
CHANGED: mysql.pm does now only do a table-lock on single write
accesses, no more on the whole session. This allows one to
access the same db twice or more.
FIXED: Changed README and Changelog for readability on 80 by 25
displays. And changed indentation of the note script itself.
ADDED: NOTEDB.pm - a generic module, which holds some methods, which
are used by binary.pm, mysql.pm and dbm.pm.
ADDED: NOTEDB.pm generate_search(), which allows one to
use AND, OR and various combinations of them using ( and ).
ADDED: a search does now return the 2nd line of a note if a matching
note's first line is a topic.
CHANGED: use "unshift" instead of push to add $libpath to @INC.
ADDED: a new feature, Caching of notes. supported by binary.pm and
mysql.pm. To turn it on, one need to set "Cache" in the config
to a true value.
This commit is contained in:
14
0x49/contents/CVS/Entries
Normal file
14
0x49/contents/CVS/Entries
Normal file
@@ -0,0 +1,14 @@
|
||||
/about/1.1.1.1/Sat Jul 1 14:40:50 2000//
|
||||
/deutsch/1.1.1.1/Sat Jul 1 14:40:50 2000//
|
||||
/index/1.1.1.1/Sat Jul 1 14:40:50 2000//
|
||||
/installation/1.1.1.1/Sat Jul 1 14:40:50 2000//
|
||||
/license/1.1.1.1/Sat Jul 1 14:40:50 2000//
|
||||
/screenshots/1.1.1.1/Sat Jul 1 14:40:50 2000//
|
||||
/upgrade/1.1.1.1/Sat Jul 1 14:40:50 2000//
|
||||
/usage/1.1.1.1/Sat Jul 1 14:40:50 2000//
|
||||
/cvs/1.2/Sat Jul 1 14:55:31 2000//
|
||||
/menu/1.2/Sat Jul 1 14:58:41 2000//
|
||||
/changelog/1.2/Sun Jul 9 22:16:25 2000//
|
||||
/version/1.2/Sun Jul 9 22:16:43 2000//
|
||||
/download/1.4/Sun Jul 9 23:03:12 2000//
|
||||
D
|
||||
1
0x49/contents/CVS/Repository
Normal file
1
0x49/contents/CVS/Repository
Normal file
@@ -0,0 +1 @@
|
||||
NOTE/0x49/contents
|
||||
1
0x49/contents/CVS/Root
Normal file
1
0x49/contents/CVS/Root
Normal file
@@ -0,0 +1 @@
|
||||
zarahg@cvs.htnews.sourceforge.net:/cvsroot/htnews
|
||||
13
0x49/contents/about
Normal file
13
0x49/contents/about
Normal file
@@ -0,0 +1,13 @@
|
||||
<h2>about note and this page</h2>
|
||||
<p>
|
||||
The author of note is Thomas Linden. if you have any questions, suggestions, votes or even flames, please feel free to
|
||||
send me an <a href="tom at daemon.de">E-mail</a>!
|
||||
<p>
|
||||
This page is hosted by <a href="http://www.consol.de">ConSol* GmbH, Germany</a> - THANKS A LOT!
|
||||
<p>
|
||||
Powered by <a href="http://www.engelschall.com/sw/eperl/">ePerl</a> and <a href="http://www.vim.org">vi</a>.
|
||||
<p>
|
||||
<a href="http://www.kernel.org"><img src="images/linux.gif" border=0></a>
|
||||
<p>
|
||||
Logo created with:<br><a href="http://www.cooltext.com"><img src="http://www.cooltext.com/images/gfx_cool.gif" border=0></a>
|
||||
|
||||
294
0x49/contents/changelog
Normal file
294
0x49/contents/changelog
Normal file
@@ -0,0 +1,294 @@
|
||||
<h2>changelog</h2>
|
||||
|
||||
<hr><ul>
|
||||
1.0.8:
|
||||
<li><b>FIXED</b>:<br>
|
||||
typo in noterc shipped with package may caused confusion (BLOWFISH
|
||||
instead of Blowfish).
|
||||
<li><b>CHANGED</b>:<br>
|
||||
changed the way note manages temporary filez. It uses now a random
|
||||
string instead of just it's own PID. It does also change it's umask
|
||||
to 077 and, if applicable (on ext2 filesystems) issues "chattr +s"
|
||||
which will cause the ext2 inodes to be zero'd after file deletion.
|
||||
<li><b>ADDED</b>:<br>
|
||||
A new config option allows the user to specify her own temp-directory.
|
||||
The default is still /tmp.
|
||||
</ul>
|
||||
|
||||
<hr><ul>
|
||||
1.0.7:
|
||||
<li><b>FIXED</b>:<br> there was a bug in the search expression, use now \Q and \E.
|
||||
<li><b>ADDED</b>:<br> --config <file> allows one to use another config than the default.
|
||||
</ul>
|
||||
<hr><ul>
|
||||
1.0.6:
|
||||
<li><b>FIXED</b>:<br> Forgot "PreferredEditor" config-option in the new config format.
|
||||
<li><b>FIXED</b>:<br> the interactive "cd .." command has ignored the presence of a
|
||||
"DefaultLong" setting(and search too)... thx to Peter.
|
||||
<li><b>CHANGED</b>:<br> Optimized a little bit the output routine, now it is better to read.
|
||||
<li><b>ADDED</b>:<br> sub format and appropriate config-option for text formatting capabilities.
|
||||
<li><b>CHANGED</b>:<br> changed getconfig regexp, which allows now also to use Option = Param.
|
||||
<li><b>FIXED</b>:<br> was not possible to override config-options, which are set by default to
|
||||
something.
|
||||
<li><b>ADDED</b>:<br> note chacks now, if a database os actually really encrypted and exits with
|
||||
an error if it s and the user turned off encryption. This protects her from
|
||||
destroying it's own database ..
|
||||
|
||||
</ul><hr><ul>
|
||||
|
||||
1.0.5:
|
||||
<li><b>FIXED</b>:<br> the T (and t respectively) printed nothing out since 1.0.3! It does
|
||||
it now again...
|
||||
<li><b>ADDED</b>:<br> a new database backend added, NOTEDB::dbm, which uses DBM files for
|
||||
storage.
|
||||
<li><b>FIXED</b>:<br> &display-tree returns now, if there is no note, otherwise it
|
||||
would die because of an undefined refernce.
|
||||
<li><b>CHANGED</b>:<br> Changed the config file format completely. It is now no more a perl
|
||||
file, instead it is a simple plain text file which note parses.
|
||||
<li><b>CHANGED</b>:<br> Changed the way, note loads it database backend. It uses now the
|
||||
$dbdriver variable as module-name, which makes it possible easily
|
||||
to write your own backend without the need to change note itself.
|
||||
<li><b>FIXED</b>:<br> Removed Getopt::Long option "bundling", causes errors with perl
|
||||
5.6.0 and is not senceful.
|
||||
<li><b>FIXED</b>:<br> Added the Getopt::Long option "no_ignore_case". In 1.0.4 options
|
||||
were case insensitive causing -i to be interpreted as --import
|
||||
instead of --interactive ;-(((
|
||||
<li><b>ADDED</b>:<br> a new config option $DEFAULT_LIST, which causes note, \
|
||||
if turned to "LONG", to use long-listing as default. |
|
||||
But it will still be able to use short-listing if you |
|
||||
explicit specify that. | submitted by
|
||||
<li><b>FIXED</b>:<br> sub search prints now an appropriate error-message in |==> Peter Palmreuther
|
||||
case no searchstring was given instead of jumping to | thanks a lot!
|
||||
usage. |
|
||||
<li><b>CHANGED</b>:<br> Changed the text in the interactive help to reflect |
|
||||
changes of verion 1.0.3 (t and T). /
|
||||
|
||||
</ul><hr><ul>
|
||||
|
||||
1.0.4:
|
||||
<li><b>CHANGED</b>:<br> Moved from @ARGV-parsing to Getopt::Long, adding options is now
|
||||
much easier and I do now understand my own code ;-)
|
||||
<li><b>ADDED</b>:<br> --raw, the "Raw Mode", which turns off any formatting of output.
|
||||
|
||||
</ul><hr><ul>
|
||||
|
||||
1.0.3:
|
||||
<li><b>ADDED</b>:<br> "-" works also for --dump, but in the other direction. It causes
|
||||
note to dump to standard output instead into a file.
|
||||
<li><b>ADDED</b>:<br> you can specify - as filename for use with --import and if you want
|
||||
to create a new note. "-" stands for standardinput and it allows you
|
||||
tp pipe another commands output to note!
|
||||
<li><b>ADDED</b>:<br> you can now use an environment variable for the passphrase (when using
|
||||
encryption). If it is presen, note will not ask for a passphrase. This
|
||||
is very usefull in comination with the addition above, for use in
|
||||
scripts.
|
||||
<li><b>CHANGED</b>:<br> the interactive help screen is now coloured.
|
||||
<li><b>ADDED</b>:<br> -o commandline switch, which causes note to overwrite an existing
|
||||
database when importing data from a previous dump. Very handy if
|
||||
you want to re-initialize your db, i.e. if you changed the format.
|
||||
<li><b>ADDED</b>:<br> the long-tree-view (-T) displays now also the note-number of each
|
||||
note.
|
||||
|
||||
</ul><hr><ul>
|
||||
|
||||
1.0.2:
|
||||
<li><b>ADDED</b>:<br> Topic-Tree overview command (-t or -T).
|
||||
<li><b>ADDED</b>:<br> Enhanced list command in interactive mode, you can now specify
|
||||
a topic which notes you want to see.
|
||||
<li><b>CHANGED</b>:<br> updated the help and usage sections to reflect the additions above.
|
||||
|
||||
</ul><hr><ul>
|
||||
|
||||
1.0.1:
|
||||
<li><b>FIXED</b>:<br> fixed bug in NOTEDB::mysql, which caused note t store NULL values
|
||||
in db, if encryption was off. A really dump failure :-(
|
||||
|
||||
</ul><hr><ul>
|
||||
|
||||
1.0.0:
|
||||
<li><b>CHANGED</b>:<br> removed install.#!/bin/sh. use now a Makefile for installation.
|
||||
<li><b>ADDED</b>:<br> Encryption support. Note can now encrypt notes using IDEA
|
||||
or DES as encryption-protocols(symetric).
|
||||
|
||||
</ul><hr><ul>
|
||||
|
||||
0.9:
|
||||
<li><b>FIXED</b>:<br> There were many new bugs after my last changes *grrrrr*. fixed.
|
||||
Works now properly, with both backends!
|
||||
<li><b>FIXED</b>:<br> and another bug: recounting of numbers did not take care about
|
||||
the existing order! If you deleted note #12, then note #13 became
|
||||
not neccessarily #12! Instead it becames any other number (kind of
|
||||
randomly...).
|
||||
<li><b>CHANGED</b>:<br> NOTEDB::binary set_del function changed, it does no more require
|
||||
a temporary file for number recount. Instead it uses get_all and
|
||||
stores all notes in RAM and then rewrites the database.
|
||||
<li><b>FIXED</b>:<br> fixed the set_new call within note. It used 0 as the first param
|
||||
(number) which is not useful since we dont have support for auto-
|
||||
increment from all database backends.
|
||||
<li><b>FIXED</b>:<br> fixed the function set_recountnum in NITEDB::mysql, it was also
|
||||
incorrect :-((( 0.8 seemed to be a very bad early alpha...........
|
||||
<li><b>FIXED</b>:<br> there was a bug in NOTEDB::binary which caused not to recount note
|
||||
numbers after deleting one :-(
|
||||
|
||||
|
||||
</ul><hr><ul>
|
||||
|
||||
0.8:
|
||||
<li><b>ADDED</b>:<br> NOTEDB::binary. so now 0.8 is ready for shipping !
|
||||
<li><b>FIXED</b>:<br> regexp bug fixed. It was only possible to delete 2 items together
|
||||
separated by comma ("d 1,2,3,4" deleted only 1,2!).
|
||||
<li><b>ADDED</b>:<br> Some new config options which reflects the new module structure.
|
||||
So you can change your database backend without the need to
|
||||
replace the note script itself.
|
||||
<li><b>FIXED</b>:<br> the previously added feature "cd <topic>" didn't really work :-(
|
||||
<li><b>ADDED</b>:<br> NOTEDB::mysql added. Perlmodule, which I will use within
|
||||
note from now on instead of buildin functions for accessing the
|
||||
database. From now on I only need to maintain one version of
|
||||
note, since the module interface will be identical between the
|
||||
bin and sql version.
|
||||
<li><b>CHANGED</b>:<br> The SQL code does not use Mysql.pm anymore. Instead it is coded
|
||||
using the more portable DBI module. This allows one easily to
|
||||
switch to anther database, which is supported by DBI.
|
||||
<li><b>CHANGED</b>:<br> Locking. The db-table will now be locked before note accesses it.
|
||||
<li><b>FIXED</b>:<br> width of listings is now always the same independent of the string-
|
||||
length of a certain note.
|
||||
|
||||
|
||||
</ul><hr><ul>
|
||||
|
||||
0.7:
|
||||
<li><b>ADDED</b>:<br> one can now use the unix-like "cd" command to change to another
|
||||
topic, thus use "cd topicname" instead just typing "topicname"!
|
||||
<li><b>FIXED</b>:<br> there was a smal regex bug which maked it impossible to use such
|
||||
topics: "4 test", in such a case note just displayed note number 4
|
||||
instead of cd'ing to topic "4 test".
|
||||
<li><b>ADDED</b>:<br> a new config option "$KEEP_TIMESTAMP" allows a user to disable
|
||||
note's default behavior of updating the timestamp of a note after
|
||||
editing it.
|
||||
|
||||
|
||||
|
||||
</ul><hr><ul>
|
||||
|
||||
|
||||
0.6:
|
||||
<li><b>FIXED</b>:<br> oops - the new suptopic feature confused the commandline-mode of
|
||||
note! quickly corrected! so subtopics also available from command-
|
||||
line.
|
||||
<li><b>FIXED</b>:<br> a small bug fiyed, it was impossible to use -D or -I from command-
|
||||
line, if $ALWAYS_INT was turned on, now it is.
|
||||
<li><b>FIXED</b>:<br> fixed problem with local/global variable $time, which confused
|
||||
the script under certain circumstances, now $time is no more global,
|
||||
it will be read in (using &getdate) locally by &new and &edit.
|
||||
<li><b>CHANGED</b>:<br> The Topic separator is no longer hardcoded, one can customize
|
||||
it using the $TopicSep variable, the default is now /, the backslash
|
||||
will no mor work!
|
||||
<li><b>CHANGED</b>:<br> use perl buildin localtime() function instead of
|
||||
GNU date, which is possibly not installed on every target
|
||||
system (i.e. win32), therefore better portability!
|
||||
<li><b>CHANGED</b>:<br> use now the strict module
|
||||
<li><b>ADDED</b>:<br> Support for subtopics added (and sub-sub-..-topics).
|
||||
<li><b>CHANGED</b>:<br> Removed the "T" command, it is now obsolete.
|
||||
<li><b>CHANGED</b>:<br> behavior of list command changed, now shows topics as well as
|
||||
notes under the current topic(if there are some).
|
||||
<li><b>CHANGED</b>:<br> The ".." command takes you now one level higher in your topic-
|
||||
structure.
|
||||
<li><b>ADDED</b>:<br> A new config option $PreferredEditor, which you can use to
|
||||
specify your own choice of editor.
|
||||
<li><b>FIXED</b>:<br> A bug at line 769 causing single note where smaller than note-
|
||||
listings
|
||||
|
||||
|
||||
|
||||
</ul><hr><ul>
|
||||
|
||||
|
||||
|
||||
0.5:
|
||||
<li><b>ADDED</b>:<br> Topic support(requested). You can sort the various notes under
|
||||
different topics now.
|
||||
<li><b>FIXED</b>:<br> There was another bug, which caused the list command to display
|
||||
the notes with a too high value of $maxlen.
|
||||
|
||||
|
||||
|
||||
</ul><hr><ul>
|
||||
|
||||
|
||||
|
||||
0.4.2:
|
||||
<li><b>ADDED</b>:<br> If run in interactive mode, note will at first do a list command.
|
||||
<li><b>FIXED</b>:<br> A bug caused note to save bogus timestamps after editing a note.
|
||||
<li><b>CHANGED</b>:<br> It does no more print 3 newlines before the menu in interactive mode.
|
||||
<li><b>FIXED</b>:<br> Some more vars will be resetted during each loop in interactive mode.
|
||||
$ListType.
|
||||
|
||||
|
||||
|
||||
</ul><hr><ul>
|
||||
|
||||
|
||||
|
||||
0.4.1:
|
||||
<li><b>ADDED</b>:<br> The install.#!/bin/sh script for the mysql version is no able to install the
|
||||
required Mysql module directly from CPAN, thanks to David A. Bandel!
|
||||
<li><b>FIXED</b>:<br> The mysql version did not display notes (i.e.: "note 3" did nothing)
|
||||
<li><b>CHANGED</b>:<br> Again, the sql-format of the mysql database has been changed. Now
|
||||
there are only 3 fields, the number filed is the primary key, the id
|
||||
field in previous versions was a waste of diskspace...
|
||||
<li><b>CHANGED</b>:<br> The format of the dump-output has been changed.
|
||||
<li><b>ADDED</b>:<br> It is now possible to import previously dumped notes into the notedb
|
||||
(dumps from both versions are compatible with each other)
|
||||
<li><b>FIXED</b>:<br> the function num_bereich() had a bug, which caused ot to ignore under
|
||||
some circumstances one number (i.e. "note -d 4-13" did nothing).
|
||||
|
||||
|
||||
|
||||
</ul><hr><ul>
|
||||
|
||||
|
||||
|
||||
0.4:
|
||||
<li><b>CHANGED</b>:<br> ok, mysql support is back again (upon requests). therefore there
|
||||
are two different version of the script in the same time with
|
||||
the same features, one for mysql and the other one for the binary
|
||||
database.
|
||||
<li><b>ADDED</b>:<br> Dump to textfile capability. Later on I want to dump it into a
|
||||
palm readable format, any help is welcome!
|
||||
<li><b>ADDED</b>:<br> interactive mode.
|
||||
<li><b>CHANGED</b>:<br> Better modularity, better code.
|
||||
<li><b>CHANGED</b>:<br> note can now run without the need of a config file. If does not
|
||||
exist, it will try to work with default values.
|
||||
|
||||
<li><b>ADDED</b>:<br> sub num_bereich(), which allows one to specify more then one
|
||||
number for deletion or displaying (i.e.: "-d 1,4,7" or "-d 4-9")
|
||||
|
||||
|
||||
|
||||
</ul><hr><ul>
|
||||
|
||||
|
||||
|
||||
0.3:
|
||||
<li><b>CHANGED</b>:<br> it uses no more a mysql database, but a binary file instead.
|
||||
This is much faster!
|
||||
<li><b>ADDED</b>:<br> note can display the notes with colors, it is turned off by default
|
||||
|
||||
|
||||
</ul><hr><ul>
|
||||
|
||||
|
||||
0.2:
|
||||
<li><b>FIXED</b>:<br> now any occurence of ' will be masked with \' before storage
|
||||
to the mysql database.
|
||||
<li><b>FIXED</b>:<br> now numbers of notes will be recounted, if one delete one note,
|
||||
so the list of notes will everytime start with 1,2,3,...
|
||||
<li><b>CHANGED</b>:<br> the look of the list output has been changed, similar to a table
|
||||
|
||||
|
||||
</ul><hr>
|
||||
|
||||
0.1:
|
||||
INITIAL RELEASE.
|
||||
|
||||
|
||||
20
0x49/contents/cvs
Normal file
20
0x49/contents/cvs
Normal file
@@ -0,0 +1,20 @@
|
||||
<h2>CVS</h2>
|
||||
<p>
|
||||
|
||||
The whole note source tree is now maintained via CVS at <a href="http://sourceforge.net">sourceforge.net</a>.
|
||||
|
||||
You can browse the repository via the web:
|
||||
<br>
|
||||
<a target="newspot" href="http://cvs.sourceforge.net/cgi-bin/cvsweb.cgi/NOTE/?cvsroot=htnews">http://cvs.sourceforge.net/cgi-bin/cvsweb.cgi/NOTE/?cvsroot=htnews</a>.
|
||||
|
||||
<p>
|
||||
|
||||
Or you can use the <b>cvs</b> command:
|
||||
<br>
|
||||
<pre>
|
||||
cvs -d:pserver:anonymous@cvs.htnews.sourceforge.net:/cvsroot/htnews login
|
||||
|
||||
cvs -z3 -d:pserver:anonymous@cvs.htnews.sourceforge.net:/cvsroot/htnews co NOTE
|
||||
</pre>
|
||||
<br>
|
||||
When prompted for a password for anonymous, simply press the Enter key.
|
||||
19
0x49/contents/deutsch
Normal file
19
0x49/contents/deutsch
Normal file
@@ -0,0 +1,19 @@
|
||||
<h2>Hinweise für deutsche Besucher</h2>
|
||||
note ist ein Konsolenprogram, mit dem man einfach Notizen verwalten
|
||||
kann, <20>hnlich wie bei "knotes". Es ist in Perl geschrieben. Note
|
||||
verwendet externe (mitgelieferte!) Module als Speicher-Backend, um
|
||||
die Daten zu speichern. Momentan ist ein mysql-Modul dabei, sowie
|
||||
ein "binary"-Modul, note's eigenes Datenformat und seit 1.0.5 auch ein
|
||||
DBM modul. Das mysql Modul verwendet Perls Standard Modul DBI
|
||||
und ist damit f<>r alle g<>ngigen DBMS verwendbar.
|
||||
Seit Version 1.0.0 wird Verschl<68>sselung unterst<73>tzt(IDEA oder DES),
|
||||
man kann also durchaus auch sensible Daten speichern.
|
||||
<p>
|
||||
Die Dokumentation für <b>note</b> liegt leider nur in englisch vor. Trotzdem müssen Deutsche
|
||||
nicht ganz leer ausgehen :-)
|
||||
<p>
|
||||
Hannes Lau hat auf seiner <a href="http://home.debitel.net/user/hannes.lau/Linux-Text.htm#Notizen">Homepage</a> eine kurze Beschreibung bereitgestellt (Tausend Dank!).
|
||||
<p>
|
||||
Eine ausf<73>hrliche Beschreibung des Programmes ist ausserdem im
|
||||
<a href="http://www.linux-magazin.de">LinuxMagazin 5/2000</a> S. 106 erschienen (allerdings basierend auf einer
|
||||
<EFBFBD>lteren Version...)!<br> *stolzsei* ;-)
|
||||
17
0x49/contents/download
Normal file
17
0x49/contents/download
Normal file
@@ -0,0 +1,17 @@
|
||||
<h2>downloads</h2>
|
||||
<p>
|
||||
Here you can find the <b>note</b> package for free download. Follow the installation instructions in the
|
||||
README file provided with the package or read the <a href="install.html">online version</a>.
|
||||
<p>
|
||||
newest: <a href="ftp://ftp.daemon.de/pub/note/note-1.0.8.tar.gz">note-1.0.8.tar.gz</a><br>
|
||||
<a href="ftp://ftp.daemon.de/pub/note/note-1.0.7.tar.gz">note-1.0.7.tar.gz</a><br>
|
||||
<a href="ftp://ftp.daemon.de/pub/note/note-1.0.6.tar.gz">note-1.0.6.tar.gz</a><br>
|
||||
<a href="ftp://ftp.daemon.de/pub/note/note-1.0.5.tar.gz">note-1.0.5.tar.gz</a><br>
|
||||
<a href="ftp://ftp.daemon.de/pub/note/README.txt">read the README</a><br>
|
||||
<a href="ftp://ftp.daemon.de/pub/note/Changelog.txt">read the Changelog</a><br>
|
||||
|
||||
<hr>
|
||||
If you encounter any problems with the site above, try to use one of the following mirrors:<p>
|
||||
<a href="ftp://www.0x49.org/pub/scip/note/">ftp://www.0x49.org/pub/scip/note/</a>
|
||||
<br>
|
||||
<a href="http://sourceforge.net/project/filelist.php?group_id=656">http://sourceforge.net/project/filelist.php?group_id=656</a>
|
||||
49
0x49/contents/index
Normal file
49
0x49/contents/index
Normal file
@@ -0,0 +1,49 @@
|
||||
<h3>welcome to the homepage of <I>note</I> by <a href="mailto: tom at daemon.de">Thomas Linden</a></h3>
|
||||
<I>note</I> is a small console program written in perl, which allows
|
||||
you to manage notes similar to programs like "knotes" from
|
||||
commandline. Note can use different database-backends for
|
||||
notes-storage. It ships with a DBI-based mysql-module(which
|
||||
can also be used for other by DBI supported DBMS) and another
|
||||
module, which uses a binary file for storage and a DBM module.<br>
|
||||
Note supports since version 1.0.0 encryption(IDEA or DES)!<p>
|
||||
Here is a brief list of it's features:
|
||||
|
||||
<ul><li> Three different database backends, mysql(DBI), dbm, binary(bin file).
|
||||
</li><li> Commandline interface using the standard perl module
|
||||
Getopt::Long, which allows you to use short or long
|
||||
command-line options.
|
||||
</li><li> Interactive interface(pure ascii), the following functions
|
||||
are available in interactive mode: list, display, topic,
|
||||
delete, edit, help.
|
||||
</li><li> Highly confiurable using a perlish configfile ~/.noterc.
|
||||
although it is configurable it is not required, note can
|
||||
run without a configfile using useful default presets.
|
||||
</li><li> Colourized output is supported using ASCII Escape-Sequences.
|
||||
</li><li> The user can customize the color for each item.
|
||||
</li><li> Data can be stored in various different database backends,
|
||||
since all database access is excluded from the program itself
|
||||
in perl modules.
|
||||
</li><li> Notes can be deleted, edited and you can search trough your notes.
|
||||
</li><li> Notes can be categorized. Each category(topic) can contain multiple
|
||||
notes and even more sup-topics. There is no limitation about
|
||||
sub topics.
|
||||
</li><li> You can view all notes in a list and it is possible only to view
|
||||
notes under a certain topic.
|
||||
</li><li> There is a tree-view, which allows you to get an overview of your
|
||||
topic-hierarchy.
|
||||
</li><li> Notes can be encrypted using DES or IDEA algorythms and Crypt::CBC.
|
||||
</li><li> You can dump the contents of your note database into a plain text
|
||||
file, which can later be imported. Imports can be appended or it can
|
||||
</li><li>verwrite an existing database (-o).
|
||||
</li><li> Note has scripting capabilities, you can create a new note by piping
|
||||
another commands output to note, you can also import a notedump from
|
||||
stdin as well es duming to stdout instead a file. Additional, there
|
||||
is an option --raw available, which prints everything out completely
|
||||
without formatting.
|
||||
</li><li> It can be installed without root-privileges.
|
||||
</li><li> Last, a while ago a user stated: "... it simply does, what it says ..."
|
||||
</li></ul>
|
||||
|
||||
<p>
|
||||
<I>note</I> is released under the terms of the <a href="license.html"><b>Gnu Public License(GPL)</b></a>
|
||||
and is therefore free Software.
|
||||
42
0x49/contents/installation
Normal file
42
0x49/contents/installation
Normal file
@@ -0,0 +1,42 @@
|
||||
<h2>installation of note</h2>
|
||||
<p>
|
||||
Unpack the tar-ball and issue the command:<br>
|
||||
$ perl Makefile.PL<br>
|
||||
It will ask you a few questions about file destinations.
|
||||
The script will find itself the proper destinations for
|
||||
the files. So, if you agree with it, simply press ENTER.
|
||||
However, you may decide to use other destinations. In this
|
||||
case, enter it, when asked. This maybe usefull, if you are
|
||||
installing it in your ome-directory and if you are not root!
|
||||
<p>
|
||||
For installation instructions for the mysql database installation
|
||||
see mysql/README.
|
||||
<p>
|
||||
If want to use another SQL database, i.e. postgresql then set
|
||||
the option "DbDriver" to the name of the responding DBI-driver
|
||||
and create a symlink of this name like this:
|
||||
<br> /usr/lib/perl5/siteperl/NOTEDB $ ln -s mysql.pm oracle.pm
|
||||
<br> The functionality is the same, but not the name!
|
||||
<p>
|
||||
The default binary file backend does not need any special installation
|
||||
procedure, you need only to spceify a filename in your config file.
|
||||
<p>
|
||||
The DBM backend(NOTEDB::dbm) requires the existence of a directory,
|
||||
which you must specify in your config using the option "DbName".
|
||||
<p>
|
||||
|
||||
|
||||
<b>Configuration</b>
|
||||
|
||||
This version of note doesn't neccessarily need
|
||||
a configuration file. But you can have one and change
|
||||
some default values. Take a look to the file config/noterc
|
||||
provided with this tarball. There are detailed instructions
|
||||
about every available parameter.
|
||||
<br> Simply copy this file into your home-directory and name it
|
||||
.noterc
|
||||
If you decide not to use the default database backend (a binary
|
||||
file), you will *need* a configuration!
|
||||
|
||||
|
||||
|
||||
342
0x49/contents/license
Normal file
342
0x49/contents/license
Normal file
@@ -0,0 +1,342 @@
|
||||
<pre>
|
||||
GNU GENERAL PUBLIC LICENSE
|
||||
Version 2, June 1991
|
||||
|
||||
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
|
||||
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
|
||||
Everyone is permitted to copy and distribute verbatim copies
|
||||
of this license document, but changing it is not allowed.
|
||||
|
||||
Preamble
|
||||
|
||||
The licenses for most software are designed to take away your
|
||||
freedom to share and change it. By contrast, the GNU General Public
|
||||
License is intended to guarantee your freedom to share and change free
|
||||
software--to make sure the software is free for all its users. This
|
||||
General Public License applies to most of the Free Software
|
||||
Foundation's software and to any other program whose authors commit to
|
||||
using it. (Some other Free Software Foundation software is covered by
|
||||
the GNU Library General Public License instead.) You can apply it to
|
||||
your programs, too.
|
||||
|
||||
When we speak of free software, we are referring to freedom, not
|
||||
price. Our General Public Licenses are designed to make sure that you
|
||||
have the freedom to distribute copies of free software (and charge for
|
||||
this service if you wish), that you receive source code or can get it
|
||||
if you want it, that you can change the software or use pieces of it
|
||||
in new free programs; and that you know you can do these things.
|
||||
|
||||
To protect your rights, we need to make restrictions that forbid
|
||||
anyone to deny you these rights or to ask you to surrender the rights.
|
||||
These restrictions translate to certain responsibilities for you if you
|
||||
distribute copies of the software, or if you modify it.
|
||||
|
||||
For example, if you distribute copies of such a program, whether
|
||||
gratis or for a fee, you must give the recipients all the rights that
|
||||
you have. You must make sure that they, too, receive or can get the
|
||||
source code. And you must show them these terms so they know their
|
||||
rights.
|
||||
|
||||
We protect your rights with two steps: (1) copyright the software, and
|
||||
(2) offer you this license which gives you legal permission to copy,
|
||||
distribute and/or modify the software.
|
||||
|
||||
Also, for each author's protection and ours, we want to make certain
|
||||
that everyone understands that there is no warranty for this free
|
||||
software. If the software is modified by someone else and passed on, we
|
||||
want its recipients to know that what they have is not the original, so
|
||||
that any problems introduced by others will not reflect on the original
|
||||
authors' reputations.
|
||||
|
||||
Finally, any free program is threatened constantly by software
|
||||
patents. We wish to avoid the danger that redistributors of a free
|
||||
program will individually obtain patent licenses, in effect making the
|
||||
program proprietary. To prevent this, we have made it clear that any
|
||||
patent must be licensed for everyone's free use or not licensed at all.
|
||||
|
||||
The precise terms and conditions for copying, distribution and
|
||||
modification follow.
|
||||
|
||||
GNU GENERAL PUBLIC LICENSE
|
||||
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
|
||||
|
||||
0. This License applies to any program or other work which contains
|
||||
a notice placed by the copyright holder saying it may be distributed
|
||||
under the terms of this General Public License. The "Program", below,
|
||||
refers to any such program or work, and a "work based on the Program"
|
||||
means either the Program or any derivative work under copyright law:
|
||||
that is to say, a work containing the Program or a portion of it,
|
||||
either verbatim or with modifications and/or translated into another
|
||||
language. (Hereinafter, translation is included without limitation in
|
||||
the term "modification".) Each licensee is addressed as "you".
|
||||
|
||||
Activities other than copying, distribution and modification are not
|
||||
covered by this License; they are outside its scope. The act of
|
||||
running the Program is not restricted, and the output from the Program
|
||||
is covered only if its contents constitute a work based on the
|
||||
Program (independent of having been made by running the Program).
|
||||
Whether that is true depends on what the Program does.
|
||||
|
||||
1. You may copy and distribute verbatim copies of the Program's
|
||||
source code as you receive it, in any medium, provided that you
|
||||
conspicuously and appropriately publish on each copy an appropriate
|
||||
copyright notice and disclaimer of warranty; keep intact all the
|
||||
notices that refer to this License and to the absence of any warranty;
|
||||
and give any other recipients of the Program a copy of this License
|
||||
along with the Program.
|
||||
|
||||
You may charge a fee for the physical act of transferring a copy, and
|
||||
you may at your option offer warranty protection in exchange for a fee.
|
||||
|
||||
2. You may modify your copy or copies of the Program or any portion
|
||||
of it, thus forming a work based on the Program, and copy and
|
||||
distribute such modifications or work under the terms of Section 1
|
||||
above, provided that you also meet all of these conditions:
|
||||
|
||||
a) You must cause the modified files to carry prominent notices
|
||||
stating that you changed the files and the date of any change.
|
||||
|
||||
b) You must cause any work that you distribute or publish, that in
|
||||
whole or in part contains or is derived from the Program or any
|
||||
part thereof, to be licensed as a whole at no charge to all third
|
||||
parties under the terms of this License.
|
||||
|
||||
c) If the modified program normally reads commands interactively
|
||||
when run, you must cause it, when started running for such
|
||||
interactive use in the most ordinary way, to print or display an
|
||||
announcement including an appropriate copyright notice and a
|
||||
notice that there is no warranty (or else, saying that you provide
|
||||
a warranty) and that users may redistribute the program under
|
||||
these conditions, and telling the user how to view a copy of this
|
||||
License. (Exception: if the Program itself is interactive but
|
||||
does not normally print such an announcement, your work based on
|
||||
the Program is not required to print an announcement.)
|
||||
|
||||
These requirements apply to the modified work as a whole. If
|
||||
identifiable sections of that work are not derived from the Program,
|
||||
and can be reasonably considered independent and separate works in
|
||||
themselves, then this License, and its terms, do not apply to those
|
||||
sections when you distribute them as separate works. But when you
|
||||
distribute the same sections as part of a whole which is a work based
|
||||
on the Program, the distribution of the whole must be on the terms of
|
||||
this License, whose permissions for other licensees extend to the
|
||||
entire whole, and thus to each and every part regardless of who wrote it.
|
||||
|
||||
Thus, it is not the intent of this section to claim rights or contest
|
||||
your rights to work written entirely by you; rather, the intent is to
|
||||
exercise the right to control the distribution of derivative or
|
||||
collective works based on the Program.
|
||||
|
||||
In addition, mere aggregation of another work not based on the Program
|
||||
with the Program (or with a work based on the Program) on a volume of
|
||||
a storage or distribution medium does not bring the other work under
|
||||
the scope of this License.
|
||||
|
||||
3. You may copy and distribute the Program (or a work based on it,
|
||||
under Section 2) in object code or executable form under the terms of
|
||||
Sections 1 and 2 above provided that you also do one of the following:
|
||||
|
||||
a) Accompany it with the complete corresponding machine-readable
|
||||
source code, which must be distributed under the terms of Sections
|
||||
1 and 2 above on a medium customarily used for software interchange; or,
|
||||
|
||||
b) Accompany it with a written offer, valid for at least three
|
||||
years, to give any third party, for a charge no more than your
|
||||
cost of physically performing source distribution, a complete
|
||||
machine-readable copy of the corresponding source code, to be
|
||||
distributed under the terms of Sections 1 and 2 above on a medium
|
||||
customarily used for software interchange; or,
|
||||
|
||||
c) Accompany it with the information you received as to the offer
|
||||
to distribute corresponding source code. (This alternative is
|
||||
allowed only for noncommercial distribution and only if you
|
||||
received the program in object code or executable form with such
|
||||
an offer, in accord with Subsection b above.)
|
||||
|
||||
The source code for a work means the preferred form of the work for
|
||||
making modifications to it. For an executable work, complete source
|
||||
code means all the source code for all modules it contains, plus any
|
||||
associated interface definition files, plus the scripts used to
|
||||
control compilation and installation of the executable. However, as a
|
||||
special exception, the source code distributed need not include
|
||||
anything that is normally distributed (in either source or binary
|
||||
form) with the major components (compiler, kernel, and so on) of the
|
||||
operating system on which the executable runs, unless that component
|
||||
itself accompanies the executable.
|
||||
|
||||
If distribution of executable or object code is made by offering
|
||||
access to copy from a designated place, then offering equivalent
|
||||
access to copy the source code from the same place counts as
|
||||
distribution of the source code, even though third parties are not
|
||||
compelled to copy the source along with the object code.
|
||||
|
||||
4. You may not copy, modify, sublicense, or distribute the Program
|
||||
except as expressly provided under this License. Any attempt
|
||||
otherwise to copy, modify, sublicense or distribute the Program is
|
||||
void, and will automatically terminate your rights under this License.
|
||||
However, parties who have received copies, or rights, from you under
|
||||
this License will not have their licenses terminated so long as such
|
||||
parties remain in full compliance.
|
||||
|
||||
5. You are not required to accept this License, since you have not
|
||||
signed it. However, nothing else grants you permission to modify or
|
||||
distribute the Program or its derivative works. These actions are
|
||||
prohibited by law if you do not accept this License. Therefore, by
|
||||
modifying or distributing the Program (or any work based on the
|
||||
Program), you indicate your acceptance of this License to do so, and
|
||||
all its terms and conditions for copying, distributing or modifying
|
||||
the Program or works based on it.
|
||||
|
||||
6. Each time you redistribute the Program (or any work based on the
|
||||
Program), the recipient automatically receives a license from the
|
||||
original licensor to copy, distribute or modify the Program subject to
|
||||
these terms and conditions. You may not impose any further
|
||||
restrictions on the recipients' exercise of the rights granted herein.
|
||||
You are not responsible for enforcing compliance by third parties to
|
||||
this License.
|
||||
|
||||
7. If, as a consequence of a court judgment or allegation of patent
|
||||
infringement or for any other reason (not limited to patent issues),
|
||||
conditions are imposed on you (whether by court order, agreement or
|
||||
otherwise) that contradict the conditions of this License, they do not
|
||||
excuse you from the conditions of this License. If you cannot
|
||||
distribute so as to satisfy simultaneously your obligations under this
|
||||
License and any other pertinent obligations, then as a consequence you
|
||||
may not distribute the Program at all. For example, if a patent
|
||||
license would not permit royalty-free redistribution of the Program by
|
||||
all those who receive copies directly or indirectly through you, then
|
||||
the only way you could satisfy both it and this License would be to
|
||||
refrain entirely from distribution of the Program.
|
||||
|
||||
If any portion of this section is held invalid or unenforceable under
|
||||
any particular circumstance, the balance of the section is intended to
|
||||
apply and the section as a whole is intended to apply in other
|
||||
circumstances.
|
||||
|
||||
It is not the purpose of this section to induce you to infringe any
|
||||
patents or other property right claims or to contest validity of any
|
||||
such claims; this section has the sole purpose of protecting the
|
||||
integrity of the free software distribution system, which is
|
||||
implemented by public license practices. Many people have made
|
||||
generous contributions to the wide range of software distributed
|
||||
through that system in reliance on consistent application of that
|
||||
system; it is up to the author/donor to decide if he or she is willing
|
||||
to distribute software through any other system and a licensee cannot
|
||||
impose that choice.
|
||||
|
||||
This section is intended to make thoroughly clear what is believed to
|
||||
be a consequence of the rest of this License.
|
||||
|
||||
8. If the distribution and/or use of the Program is restricted in
|
||||
certain countries either by patents or by copyrighted interfaces, the
|
||||
original copyright holder who places the Program under this License
|
||||
may add an explicit geographical distribution limitation excluding
|
||||
those countries, so that distribution is permitted only in or among
|
||||
countries not thus excluded. In such case, this License incorporates
|
||||
the limitation as if written in the body of this License.
|
||||
|
||||
9. The Free Software Foundation may publish revised and/or new versions
|
||||
of the General Public License from time to time. Such new versions will
|
||||
be similar in spirit to the present version, but may differ in detail to
|
||||
address new problems or concerns.
|
||||
|
||||
Each version is given a distinguishing version number. If the Program
|
||||
specifies a version number of this License which applies to it and "any
|
||||
later version", you have the option of following the terms and conditions
|
||||
either of that version or of any later version published by the Free
|
||||
Software Foundation. If the Program does not specify a version number of
|
||||
this License, you may choose any version ever published by the Free Software
|
||||
Foundation.
|
||||
|
||||
10. If you wish to incorporate parts of the Program into other free
|
||||
programs whose distribution conditions are different, write to the author
|
||||
to ask for permission. For software which is copyrighted by the Free
|
||||
Software Foundation, write to the Free Software Foundation; we sometimes
|
||||
make exceptions for this. Our decision will be guided by the two goals
|
||||
of preserving the free status of all derivatives of our free software and
|
||||
of promoting the sharing and reuse of software generally.
|
||||
|
||||
NO WARRANTY
|
||||
|
||||
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
|
||||
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
|
||||
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
|
||||
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
|
||||
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
|
||||
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
|
||||
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
|
||||
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
|
||||
REPAIR OR CORRECTION.
|
||||
|
||||
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
|
||||
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
|
||||
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
|
||||
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
|
||||
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
|
||||
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
|
||||
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
|
||||
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
|
||||
POSSIBILITY OF SUCH DAMAGES.
|
||||
|
||||
END OF TERMS AND CONDITIONS
|
||||
|
||||
How to Apply These Terms to Your New Programs
|
||||
|
||||
If you develop a new program, and you want it to be of the greatest
|
||||
possible use to the public, the best way to achieve this is to make it
|
||||
free software which everyone can redistribute and change under these terms.
|
||||
|
||||
To do so, attach the following notices to the program. It is safest
|
||||
to attach them to the start of each source file to most effectively
|
||||
convey the exclusion of warranty; and each file should have at least
|
||||
the "copyright" line and a pointer to where the full notice is found.
|
||||
|
||||
<one line to give the program's name and a brief idea of what it does.>
|
||||
Copyright (C) 19yy <name of author>
|
||||
|
||||
This program is free software; you can redistribute it and/or modify
|
||||
it under the terms of the GNU General Public License as published by
|
||||
the Free Software Foundation; either version 2 of the License, or
|
||||
(at your option) any later version.
|
||||
|
||||
This program is distributed in the hope that it will be useful,
|
||||
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
||||
GNU General Public License for more details.
|
||||
|
||||
You should have received a copy of the GNU General Public License
|
||||
along with this program; if not, write to the Free Software
|
||||
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
|
||||
|
||||
|
||||
Also add information on how to contact you by electronic and paper mail.
|
||||
|
||||
If the program is interactive, make it output a short notice like this
|
||||
when it starts in an interactive mode:
|
||||
|
||||
Gnomovision version 69, Copyright (C) 19yy name of author
|
||||
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
|
||||
This is free software, and you are welcome to redistribute it
|
||||
under certain conditions; type `show c' for details.
|
||||
|
||||
The hypothetical commands `show w' and `show c' should show the appropriate
|
||||
parts of the General Public License. Of course, the commands you use may
|
||||
be called something other than `show w' and `show c'; they could even be
|
||||
mouse-clicks or menu items--whatever suits your program.
|
||||
|
||||
You should also get your employer (if you work as a programmer) or your
|
||||
school, if any, to sign a "copyright disclaimer" for the program, if
|
||||
necessary. Here is a sample; alter the names:
|
||||
|
||||
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
|
||||
`Gnomovision' (which makes passes at compilers) written by James Hacker.
|
||||
|
||||
<signature of Ty Coon>, 1 April 1989
|
||||
Ty Coon, President of Vice
|
||||
|
||||
This General Public License does not permit incorporating your program into
|
||||
proprietary programs. If your program is a subroutine library, you may
|
||||
consider it more useful to permit linking proprietary applications with the
|
||||
library. If this is what you want to do, use the GNU Library General
|
||||
Public License instead of this License.
|
||||
</pre>
|
||||
19
0x49/contents/menu
Normal file
19
0x49/contents/menu
Normal file
@@ -0,0 +1,19 @@
|
||||
<img src="images/note.jpg" border=0>
|
||||
<HR SIZE="1" NOSHADE="1">
|
||||
<a href="index.html">home</a><p>
|
||||
<a href="installation.html">installation</a><p>
|
||||
<a href="usage.html">usage</a><p>
|
||||
<a href="upgrade.html">upgrade</a><p>
|
||||
<a href="changelog.html">changelog</a><p>
|
||||
<a href="download.html">download</a><p>
|
||||
<a href="license.html">license</a><p>
|
||||
<a href="cvs.html">cvs</a><p>
|
||||
<a href="screenshots.html">screenshots</a><p>
|
||||
<a href="deutsch.html">deutsch</a><p>
|
||||
<a href="about.html">about</a><p>
|
||||
<HR SIZE="1" NOSHADE="1">
|
||||
<center><font size=-2>last updated 02.07.2000</font>
|
||||
<p>
|
||||
<img src="images/anybrow.gif" alt="best viewed with any browser">
|
||||
</center>
|
||||
|
||||
16
0x49/contents/screenshots
Normal file
16
0x49/contents/screenshots
Normal file
@@ -0,0 +1,16 @@
|
||||
<h2>screenshots</h2>
|
||||
|
||||
Yes there are also screenshots of note available :-)
|
||||
<br>
|
||||
Simply click on a tumbnail to enlarge the image!
|
||||
<p>
|
||||
<a href="images/note.gif">Linux</a>
|
||||
<br><a href="images/note-linux.gif"><img src="images/note_linux_small.png" border=0></a>
|
||||
<p>
|
||||
<a href="images/note-win32.gif">Win32</a>
|
||||
<br><a href="images/note-win32.gif"><img src="images/note_win32_small.png" border=0></a>
|
||||
<p>
|
||||
<a href="images/note-be.jpg">BeOS</a>
|
||||
<br><a href="images/note-be.jpg"><img src="images/note_be_small.png" border=0></a>
|
||||
<p>
|
||||
and finally here a <a href="http://home.debitel.net/user/hannes.lau/Desktop.htm">desktop</a> of a user with note running.
|
||||
45
0x49/contents/upgrade
Normal file
45
0x49/contents/upgrade
Normal file
@@ -0,0 +1,45 @@
|
||||
<h2>upgrade from previous version of note to 1.0.x</h2>
|
||||
<p>
|
||||
In any case: BACKUP your existing note database!!!!!!!
|
||||
The format has not changed, but some default values
|
||||
(see the new config file-sample). Use this command
|
||||
to save your note database with your *old* version
|
||||
of note:<br>
|
||||
"note -D"<br>
|
||||
This works with both the mysql and the binary version.
|
||||
<p>
|
||||
You need to reedit your configfile. Please refer to the
|
||||
sample config in config/noterc.
|
||||
<p>
|
||||
<hr>
|
||||
<p>
|
||||
This version of note has now encryption support build in.
|
||||
If you decide to use it, you need to re-initialize your
|
||||
note database. That's why, because your current database
|
||||
is unencrypted and *if* you want to secure your data, you
|
||||
need to secure everything. That means, your existing data
|
||||
must be encrypted before you can use this new capability!
|
||||
<p>
|
||||
Follow this steps:
|
||||
<ul>
|
||||
<li> backup existing db:
|
||||
<br> $ note -D
|
||||
<li> backup the db:
|
||||
<br> $ cp .notedb .notedb.save
|
||||
or (for mysql users!):
|
||||
<br> $ cp -r /usr/local/mysql/data/notedb ~/notedb.mysql.save
|
||||
<li> go into note and delete all existing notes:
|
||||
<br> $ note -d 1-20 (or however)
|
||||
<li> now upgrade your note installation:
|
||||
<br> $ perl Makefile.PL; make install
|
||||
<li> re-configure note. Turn $USE_CRYPT on by setting it
|
||||
to "YES".
|
||||
<li> re-initialize your database:
|
||||
<br> $ note -I note.dump.2323 (or whatever)<br>
|
||||
note will prompt you for a passphrase. It will be used
|
||||
by Crypt::CBC for encrypting your data.
|
||||
</ul>
|
||||
From now on, your data is encrypted. You will need the passphrase
|
||||
you set above for decrypting it! So - don't forget it!
|
||||
|
||||
|
||||
350
0x49/contents/usage
Normal file
350
0x49/contents/usage
Normal file
@@ -0,0 +1,350 @@
|
||||
<h2>usage of note</h2>
|
||||
<p>
|
||||
<a href="#desc">1. Description</a><p>
|
||||
<a href="#topics">2. Topics</a><p>
|
||||
<a href="#format">3. Formatting of note-text</a><p>
|
||||
<a href="#script">4. Scripting</a><p>
|
||||
<a href="#dbformat">5. Binary DB</a><p>
|
||||
<a href="#sqlformat">6. Mysql DB</a><p>
|
||||
<a href="#dumpformat">7. Dump Format</a><p>
|
||||
<a href="#security">8. Security</a><p>
|
||||
<hr>
|
||||
<p>
|
||||
<a name="#desc">
|
||||
<h4>Decription</h4>
|
||||
|
||||
If you don't know, how to run note, try "note -h" first.
|
||||
It will tell you all available commandline options.
|
||||
<p>
|
||||
To create a new note, simply run "note". You can enter
|
||||
the note (the length is by default limited to 4096 bytes,
|
||||
which you can change from your config file if you are using
|
||||
the binary backend, therwise there is no limitation).
|
||||
End by typing a . on a line itself. note will tell you the
|
||||
number of the note.
|
||||
<p>
|
||||
If you want to view the note, type "note 1", if the notenumber
|
||||
was 1.
|
||||
<p>
|
||||
If you want to get an overview of all notes, type "note -l".
|
||||
You will get a list of all notes, containing the number,
|
||||
the first line and the creation date. If topic-support is
|
||||
turned on (which is by default), then all subtopics under the
|
||||
current topic will be displayed first.
|
||||
<br> If you want to get a listing of all
|
||||
If you want to see the timestamps, use "-L" instead of "-l".
|
||||
Read more about topics below in the section "Topics".
|
||||
You can also specify the topic which notes you want to see:
|
||||
"-l mytopic" does the trick.
|
||||
<br> Additional, you might want to get an overview of your topic-
|
||||
strcture. You can use the command "-t" in this case, which
|
||||
will display a tree-view of your tpic-structure. You can
|
||||
use the command "-T" if you want to see the notes under each
|
||||
topic too. "-T" will also show the number of each note.
|
||||
<p>
|
||||
To edit a certain note, type "note -e 1". It will invoke your
|
||||
editor (vi or pico). You can edit it, after saving, note
|
||||
will store the changed note to the database.
|
||||
<p>
|
||||
Of course you can drop a certain note: "note -d 1" deletes
|
||||
note number 1. If a note in the middle or the beginning of
|
||||
the database will be deleted, note will recount the other
|
||||
existent notes. For example there are 3 notes, number 1, 2
|
||||
and 3. If you delete number 2, then number 3 will become
|
||||
number 2.
|
||||
<br> You can also make use of the extended delete-syntax:
|
||||
To delete note 1 and 2, use "-d 1,2"
|
||||
To delete note 1,2 and 3, use "-d 1-3".
|
||||
<p>
|
||||
If you cannot remember, which note you are looking for, you
|
||||
can use the search capability of note: "note -s <searchstring>".
|
||||
note will search the whole note database case insensitive for
|
||||
an occurence of this string and tell you the number and first-
|
||||
line it have.
|
||||
<p>
|
||||
Instead of using note from the commandline you can use the
|
||||
interactive mode. Run note with "note -i". If you need assistance
|
||||
type "?" or "h" at the ">" prompt. The interactive mode
|
||||
provides you the most functions of note.
|
||||
<p>
|
||||
You can also dump the contents of your note-database into a
|
||||
ASCII-textfile(-D). You can use this file later to import it into
|
||||
your note-database(-I). This is usefull, if you want quickly trans-
|
||||
fer your notes from one host to another (i.e. you could mail
|
||||
your note-dump form your office to home and import it there
|
||||
for further use).
|
||||
<br> The dumps from the two versions of note are in the same format.
|
||||
Using dumps it is also possible to reinitialize your database. You
|
||||
can use the "-o" switch whcih causes note to overwrite your existing
|
||||
database. This is very handy if you changed heavily your config. And
|
||||
it is required, if you changed: encryption, db-driver, (binary-format)
|
||||
and the password. You can use the following command for reinitializing:
|
||||
<br> $ note -D - | note -o -I -
|
||||
<br> What the hell, does it?! Step by step:
|
||||
<ul>
|
||||
<li> "note -D -" creates a note-database dump and prints it out
|
||||
to stantdard output.
|
||||
<li> "|" this is the shell's pipe command. It takes the output
|
||||
of the left program and gives it to the right program as standard
|
||||
input.
|
||||
<li> "note -o -I -" imports a note-database dump from standard input
|
||||
and overwrites an existing database.
|
||||
</ul>
|
||||
Before you use the "-o" switch, I consider yuo to make a backup!
|
||||
|
||||
<p>
|
||||
|
||||
<a href="#top">top</a><p><p><a name="topics">
|
||||
<h4>Topics</h4>
|
||||
|
||||
If topic-support is turned on (which is by default), the various
|
||||
notes are sorted under various topics. There is no special database
|
||||
field for the topic. Instead the topic will be stored right in the
|
||||
note.
|
||||
<br> If the first line of your note contains some text bordered by slashes
|
||||
(or whatever you prefer, set "TopicSeparator" in your config! default is slash),
|
||||
then note will consider it as the topic of this certain note. For examle:
|
||||
<br> /TodoList/
|
||||
<br> If you are using topics, no data after the topic is allowed, if there
|
||||
is any text, note will consider it as a subtopic! Therefore, don't for-
|
||||
get to put a newline after the topic-line.
|
||||
<p>
|
||||
If you are in interactive mode, you can "cd" to a different note simply
|
||||
by typing it's name at the command-prompt, or you can use the well-known
|
||||
syntax "cd topic".
|
||||
<br> The list-command will only show you notes under this topic. If you create
|
||||
a new note, it will automagically inserted under the current topic (note
|
||||
will prepend the string "/topicname/" to the text of your note).
|
||||
<p>
|
||||
You can create at any time from any point a new topic. Just create a new
|
||||
note and type the name of the new topic bordered by slashes (or TopicSeparator)
|
||||
at the first line of this note. After saving, there will be available a
|
||||
new topic with one note in it.
|
||||
<p>
|
||||
You can create as many subtopics as you like, the format is similar to a
|
||||
filesystem-path. An example, say, you want to create such a structure:
|
||||
<p>
|
||||
<pre>
|
||||
(root - top level)
|
||||
|
|
||||
|----test
|
||||
| |----subtopic
|
||||
| | |--note 1
|
||||
| | |--note 2
|
||||
| |
|
||||
| |--note 4
|
||||
|
|
||||
|--note 3
|
||||
</pre>
|
||||
<p>
|
||||
Then you may create those 4 new notes:
|
||||
<br>
|
||||
<pre>
|
||||
--- snip ---
|
||||
/test/subtopic/
|
||||
note 1
|
||||
--- snip ---
|
||||
/test/subtopic/
|
||||
note 2
|
||||
--- snip ---
|
||||
note 3
|
||||
--- snip ---
|
||||
/test/
|
||||
note 4
|
||||
--- snip ---
|
||||
</pre><br>
|
||||
I hope, you got the point ;-)
|
||||
<p>
|
||||
|
||||
|
||||
If a note does not contain the "magic" /topic/ construction on the first
|
||||
line, it will be listed under the "root" of note, that is the point you are
|
||||
at the startup of note.
|
||||
<p>
|
||||
You can subsequently move a note without a topic to a certain topic. Simply
|
||||
edit it and insert at the first line the above mentioned construction.
|
||||
<p>
|
||||
Note: Please don't forget the prepending and appending a slash of a topic.
|
||||
You will get strange results without it!
|
||||
|
||||
|
||||
<p>
|
||||
|
||||
<a href="#top">top</a><p><p><a name="format">
|
||||
<h4>Formatting of notes</h4>
|
||||
|
||||
Another very nice feature is the possibility to format the note-text (as much as
|
||||
shell allows it). First, you can use the note-internal "magic-strings" for color-
|
||||
izing. Those strings looks much like HTML:
|
||||
i<br> "<green>here is a green line of text</green> no more green."
|
||||
As you see, the beginning of another color starts with a tag(kinda) of the color
|
||||
<colorname> and ens with an end tag </colorname>.
|
||||
<p>
|
||||
The following colors are available:
|
||||
black, red, green, yellow, blue, magenta, cyan and white.
|
||||
<p>
|
||||
Beside colorizing text, you can also create bold or underlined text! If you decide
|
||||
to use this (additional) feature, you need to set the Config-Option "FormatNotes"
|
||||
to 1 which turns it on.
|
||||
<br> Usage is very straightforward, if a word (a word is defined as some text with at least
|
||||
one space surrounded) is between a magic mark-character. Here are the available
|
||||
things, you can do:
|
||||
<pre>
|
||||
bold: **word**
|
||||
underlined: __word__
|
||||
inverse: {{word}}
|
||||
</pre>
|
||||
The text will be formatted using the actually note-color.
|
||||
<p>
|
||||
|
||||
|
||||
<a href="#top">top</a><p><p><a name="script">
|
||||
<h4>Scripting</h4>
|
||||
|
||||
Since version 1.0.3 there are some additions which allows you to use note in
|
||||
scripts, without user-interaction. You might run a special script as cronjob,
|
||||
which adds a note under a certain topic every week. Or the like.
|
||||
<p>
|
||||
Here are the possibilies you have:
|
||||
<p>
|
||||
You can add a new note through a pipe, another commands output becomes
|
||||
note's input:
|
||||
<br> $ cat /var/spool/news/daily | note -
|
||||
<br> This command adds the content of a file "daily" as a new note. Note the dash.
|
||||
it stands for "Standard Input". Note will be completely silent and it will not
|
||||
ask for something.
|
||||
<p>
|
||||
Suppose you are using encryption. You might wonder, how note will get your
|
||||
passphrase? The solution: You need to set up an environment variable which
|
||||
contains the password:
|
||||
<br> $ export NOTE_PASSWD=secret
|
||||
<br> If the variable is present, note will not ask you for a passphrase!
|
||||
<p>
|
||||
Another thingy you might find useful is the -r (--raw) command-line flag. This
|
||||
turns note into raw mode , which means it will only print the
|
||||
data without any formatting. Raw mode is available for list and display,
|
||||
since it makes no sense, interactive mode doe not support raw mode.
|
||||
<p>
|
||||
|
||||
|
||||
|
||||
<a href="#top">top</a><p><p><a name="dbformat">
|
||||
<h4>Format of the notedb (binary backend)</h4>
|
||||
|
||||
The database where the notes are stored is a binary fixed record length file
|
||||
of the following format:
|
||||
It consists of three fixed length fields per entry. The fields
|
||||
have the following types:
|
||||
<ul>
|
||||
<li> Number: Integer (1 byte)
|
||||
<li> Note: String (default 1024 bytes)
|
||||
<li> Time: String (default 64 bytes)
|
||||
</ul>
|
||||
You can change the sizes of the fields "Note" and "Time" in
|
||||
the configfile "~/.noterc". If it does not exist, the above
|
||||
defaults will be used.
|
||||
<br> If the data to be stored is smaller then the size of the field,
|
||||
it will be filled with ZERO's ("\0"). The Note and the Time
|
||||
fields will be uuencoded before storage. Of course, this is
|
||||
no security, never mind...
|
||||
|
||||
<p>
|
||||
|
||||
<a href="#top">top</a><p><p><a name="sqlformat">
|
||||
<h4>The note-database (mysql backend)</h4>
|
||||
|
||||
The sql-database for the mysql version has the following design:
|
||||
<pre>
|
||||
+--------+---------+------+-----+---------+----------------+
|
||||
| Field | Type | Null | Key | Default | Extra |
|
||||
+--------+---------+------+-----+---------+----------------+
|
||||
| number | int(10) | | PRI | 0 | auto_increment |
|
||||
| note | text | YES | | NULL | |
|
||||
| date | text | YES | | NULL | |
|
||||
+--------+---------+------+-----+---------+----------------+
|
||||
</pre>
|
||||
|
||||
<p>
|
||||
|
||||
<a href="#top">top</a><p><p><a name="dumpformat">
|
||||
<h4>Format of the ASCII-dump file (note -D)</h4>
|
||||
|
||||
The dump of a note-database (if you use note -D) has the following
|
||||
format:
|
||||
<pre>
|
||||
--- snip ---
|
||||
Number: 1
|
||||
Timestamp: 14.01.2000 00:25:01
|
||||
This is a sample text
|
||||
in a sample note.
|
||||
|
||||
Number: 2
|
||||
Timestamp: 14.01.2000 02:37:40
|
||||
And this is another sample
|
||||
of a note.
|
||||
--- snip ---
|
||||
</pre>
|
||||
<p> You can reimport a dump into your note-database with "note -I <file>"
|
||||
Existing notes will not overwritten, note will append the imported
|
||||
data to your note-database.
|
||||
<p>
|
||||
|
||||
|
||||
<a href="#top">top</a><p><p><a name="security">
|
||||
<h4>Security</h4>
|
||||
|
||||
If you are using the MySQL driver, refer to the mysql
|
||||
manual for more informations about security of mysql databases:
|
||||
http://www.mysql.org/Manual_chapter/manual_Privilege_system.html
|
||||
<p>
|
||||
If you are using notes proprietary binary driver, then
|
||||
the permission 0600 of the file "~/.notedb" is strongly required!
|
||||
<p>
|
||||
Additional, you can turn on encryption from the config file.
|
||||
Simply set UseEncryption to 1. Please note, that you need
|
||||
to decide, if you want to use encryption before the first use
|
||||
of note! If have already a note database and want to "migrate"
|
||||
to encryption, I suggest you to follow the directions in the
|
||||
file UPGRADE!
|
||||
<p>
|
||||
You can choose from different encryption algorythms. The default
|
||||
is IDEA, but DES or BLOWFISH is also possible. You need to have
|
||||
installed the following additional perl-modules on your system:
|
||||
<ul>
|
||||
<li> MD5
|
||||
<li> Crypt::IDEA
|
||||
<li> Crypt::DES
|
||||
<li> Crypt::CBC
|
||||
</ul>
|
||||
After turning on encryption, note will ask you for a passphrase
|
||||
everytime it runs! It will *not* store this passphrase!
|
||||
So, don't forget it! Be careful!
|
||||
<p>
|
||||
Once note have encrypted some data using this passphrase, you
|
||||
cannot simply switch to another passphrase, because all data
|
||||
within the database needs to be encrypted using the same passphrase!
|
||||
If you want to change the passphrase for any reason, please read
|
||||
the file UPGRADE and follow it's directions!
|
||||
<br> Someday I will add a "change passwd" function, which will do all
|
||||
these things for you. Someday, I said...
|
||||
For now you can use the "re-initialze database" functionality, mentioned
|
||||
earlier in the "Usage" section (at the end of the section).
|
||||
<p>
|
||||
Note: To make sure, the encrypted data can be stored properly,
|
||||
it will be uuencoded after encryption.
|
||||
<p>
|
||||
Note: *If* you forgot your passphrase and *if* you don't have
|
||||
a backup of your database without encryption, PLEASE
|
||||
don't bother me with "helpme" emails! If you don't know
|
||||
the phrase, then the data can't be decrypted. Even if it
|
||||
is possible - I am not responsible for that!
|
||||
<p>
|
||||
Note: How does note know, if the passphrase was incorrect? It uses the
|
||||
specified phrase and encodes at least one note (the first one)
|
||||
and checks if the decrypted timestamp field matches the following
|
||||
expression: "^\d+\.\d+". Translated from perl to human:
|
||||
the timestamp must begin with minimum one digit (possibly more),
|
||||
followed by one dot, followed by minimum one digit (possibly more).
|
||||
Chances are bad, that a wrong passphrase will cause a timestamp
|
||||
matching the rule above. If you have other experiences, please
|
||||
drop me a mail!
|
||||
1
0x49/contents/version
Normal file
1
0x49/contents/version
Normal file
@@ -0,0 +1 @@
|
||||
1.0.8
|
||||
Reference in New Issue
Block a user