![[Picture. Emacs 21.2 tinytf.el package in action]](pic/emacs-tinytf.jpg)
| Emacs Tiny Tools Project |
The most up to date version is in CVS. See instructions at the end of this page.
Are these tools hard to install or use? The project may seem huge and difficult to install for those who do not have much previous experience on Emacs configuration and package installation. That's only surface and the impression that you may get from the size of the project. Things are much easier that you expect: even a novice Emacs user can install the tools. At minimum you can install the project within 5-10 minutes with the help of the install document above.
|
|
| White paper management package, tinytf.el, in action (photo from Windows native Emacs 21.2). Many pages in this site have been created with it. |
![[Picture. Emacs 21.2 tinypath.el package in action]](pic/emacs-tinypath.jpg)
|
| File monitoring package, tinypath.el, in action (photo from Windows native Emacs 21.2). You can separate lisp package files to separate directories and there is no need to manually update variables load-path and Info-default-directory-list. Install new packages and run M-x tinypath-cache-regenerate and your Emacs is up to date. The Cache also speeds up loading packages with require, load, load-library, load-file. Refer to above link install for more information. |
2002-09: Emacs 21.x compatibility issues are under work. library cleanup is now done. XEmacs compatibility is under testing.
2001-12: The CVS structure and package's directory structure has been redesigned. The HTML documentation is now bundled as well as the plain/text source. The namespace cleanup work has been finished and kit should now be free of any possible clashing functions. The setup center tiny-setup.el has been made better and more automatic. More features are now enabled. There are no known Emacs 21.1 compatibility problems.
2001-07: a "namespace-cleanup" work was started to ensure that all custom functions contain a proper library prefix. This cleanup work is necessary to isolate the tools from other, possibly conflicting, namespaces. It has no user visible chnages, but due to massive work that it needs, expect to see weird bugs in snapshots stamped after this date. Work is in progress to polish package build and release methods so that everything would be automatic. Latest releases of the code can be found only from CVS.
Next goal: Make all package to comply XEmacs packaging system and possibly include them into XEmacs. If you know XEmacs packaging system, please contact the author to get the work packaged properly.
Future goal: Provide Debian (.deb) packages for easy upgrade in Linux systems. Anyone who is familiar with the Debian packaging system is welcomed to send email to the address found in Developer list section.
Emacs 20.1+ ( 20.7+ preferred )
XEmacs: 20.4+ ( 21.1+ preferred )
The release MAY WORK FINE in older Emacs releases and if you submit bug
report, support for older versions can be considered unless there is
too much work. The current development is done and tested using these
versions of Win32 Emacs:
Emacs 20.7.3
XEmacs 21.2.20
Jari Aalto
jari.aalto@poboxes.com
Usually on-line @700 BMT or UTC+2 18:00 local time.
ICQ identification jari-aalto 82313129
Richard Kim
ryk@dspwiz.com
Co-Developer.
There is mailing list for the project, where you can send
questions and bug reports. The list is open (you do not have to be
a subscribed member to post), so prefer sending bug reports to the
list instead of directly to the maintainer, because the the problem
will get wider audience. The list opened 2000-01. See WWW interface at
http://lists.sourceforge.net/lists/listinfo/tiny-tools-users
or use Mail interface:
subscribe [address=address]
In addition to SF archive, there is
http://marc.theaimsgroup.com/?l=tiny-tools-user&r=1&w=2
Mailing list information
Send a message with the word help as subject or
in the body , to:
tiny-tools-users-request@lists.sourceforge.net
unsubscribe [address]
CVS update method
CVS is an excellent tool to keep up with the latest updates, fixes
and new features. CVS for Unix is available at
http://www.cvshome.com/
For win32 platform, the CVS comes with the cygwin kit available at
http://www.cygwin.org/
(See link at the right hand corner and download setup.exe)
If you want hassle-free and easy CVS binary for Win32 and not the
whole Cygwin bundle, grab cvs binary from
http://www.cvshome.org/dev/codewindow.html
$ cvs -d :pserver:anonymous@cvs.tiny-tools.sourceforge.net:/cvsroot/tiny-tools login
password: [RET]
$ cvs -z6 -d :pserver:anonymous@cvs.tiny-tools.sourceforge.net:/cvsroot/tiny-tools co tiny-tools
After the above initial checkout procedure, all you have to do is
to issue this command from time to time to read the updates:
$ cd tiny-tools
$ cvs update
A mall glitch concerning codewindow cvs binary reported by
david x callaway dxc@xprt.net:
I have found one funny bug with it, on nt. you can "cvs edit XyZ.c"
even though the file is "xyz.c" with no complaint. this is ok, sort
of, since the stupid win32 file system doesn't care, but the problem
is when you later try to check it in the server complains that "XyZ.c"
doesn't exist or some such. you end up having to edit CVS/Entries to
fix it. the funny thing is you can "cvs status xyz.c" or "cvs status
XyZ.c" and it will work fine either way.
$Docid: 2002-09-14 Jari Aalto $ Copyright (C) Jari Aalto. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, v1.0 or later (the latest version is presently available at http://www.opencontent.org/). Distribution of the work or derivative of the work for commercial purposes in any form is prohibited unless prior permission is obtained from the copyright holder. (VI.B LICENSE OPTIONS)
|
|
This site, as well as many other opensource projects sites, is hosted by sourceforge.net. |
| Emacs Web Ring site (3) [Previous] [Next] [Skip Previous site] [Skip next Site] [List Sites] [Home] |