Bare in mind that I have the ls (list) command aliased to include the -FGH switches on FreeBSD (basically use colours and append a symbol to the end of each file, e.g. dir/ and exe* instead of dir and exe).
~/code is basically made up of a directory per language with room for a little growth. The only languages I actively use are C, Ruby, and BourneShell. But I'm familiar with most in the directory and have made room for some of my 'to learn' list. Each directory essentially consists of a simple pattern.
- Documentation, as seen in ~/code/C/doc/ I have a few old tutorials saved, references, an indent(1) profile in case I need it, and a copy of the Lions Book and Code listings amon the PDF's.
- A place to put common bits of code
- A spot for ready to use code in library form
- Ready made makefile templates for feeding through the make program and similar tools
- Where to stuff manual pages for now
- The source directory contains source code files, in ~/code/C/src/ resides a copy in HTML and Source form of the UNIX Version 6 Kernels Source Code for reference and reading pleasure. In ~/code/Ruby/src/ it shows that I've made directories in the src folders for various libraries and toolkits where necessary. If it's not some thing I wrote when I started learning the language or a quickie I usually use a directory per program.
- A spot to put them when I feel like writing them, I find it most useful for HTML/XHTML
The content various by language but it's the style I've tried to arrange.
The rest of my home directory is also nicely organised for the most part.
Terry@Dixie$ ls ~/|grep '/' | sed 's/\///g' 7:45 Desktop Documents Music Pictures Videos code logs sh Terry@Dixie$ ls ~/Documents 7:45 Computers/ Personal/ Work/ Games/ School/ [SAS]/ Lyrics of Dixie.txt Shakespeare/ misc_dot_files.tar.gz Terry@Dixie$ 7:46
I'm glad to have a copy of R^5RS (PDF & PS) on hand so I can work on learning Scheme if I get some vacation time next week.