procj TUTORL1 {tag str} {A0L1 eev/e/tutorial.e.html#$tag $str} htmlize {eev - main ideas} { [P (These notes are old - the file is dated 02dec2004)] [HLIST1 {The main ideas of the eev project} [HLIST2 {Saving the world} [J Sharing can be more natural than we think] [J We can learn more about our environment] [J We are part of our environment] [J The culture of the \"finished product\"] ] [HLIST2 {Sharing notes (and the deeper consequences of that)} [J Reusing your own notes] [J You won't be forced to share your notes, you can just use the ones written by others] [HLIST2 {All my notes are online (well, almost)} [A0L tourism.html A Brief Statement About (Computer) Tourism] [J My tourism package (the .tgz with most of my public files\; how to install it to create a copy of my environment)] [HLIST2 [J [NAME htmlization] How the text files are converted to HTML for the web version:] [J The `\")' hyperlinks: in [TUTORL lisp_hiperlinks Emacs], in [AL {TH/Generate test_links} HTML].] [J The `[anchorli2html {} ... {}]' anchors.] [J The red stars ([COLOR red [IT *]]) are generally used as [TUTORL delimited_blocks delimiters].] [J Other strange chars may look great in [AL eev/glyphs.el Emacs], especially in [A0L vtutil.html text mode with a changed font], but they may be impossible to convert to HTML.] ] ] ] [HLIST2 {A sort of point-and-click interface using the keyboard, in which:} [J A block of text can be interpreted as a block of commands in a computer language (actually in almost any computer language)] [J Certain lines can work as hyperlinks to pieces of information already in your computer (existing docs in essentially any format, source code, etc)] [J The hyperlink lines can be embedded in the blocks of commands, for any language that accepts comments] ] [HLIST2 {"Computers are machines for automating everything that can be automated"} [HLIST2 {This idea suits command-line interfaces much better than graphical interfaces} [J \"[LR http://kuoi.asui.uidaho.edu/~kamikaze/documents/beginning_CLI.html In the Beginning was the Command Line]\", by Neal Stephenson] ] [HLIST2 {The notion of "user" is artificial} [J I've written an (unfinished) essay called \"[A0L why-users.html Why Users Should Not Exist]\" on this.] ] [HLIST2 {Interactive programs with terminal-based interfaces can be automated easily} [J How that was used to make a demo for eev] ] ] [HLIST2 {Emacs becomes the main interface to the underlying system. Other advantages not mentioned before:} [J We get a standard way to edit commands (better than readline)] [J We keep the original interfaces of programs - no changes are required] [J Emacs is extensible and easy to study and to play with\; has tons of excellent source code in Lisp\; has truly great online manuals] [J Emacs is also a debugger] [J 25 years of knowledge and expertise built-in\; and this by a whole community] [J it's been [IT the] programmer editor (in parallel with vi) for most of that time] [J it can even emulate vi :)] ] [HLIST2 {What does it look like...} [J In pure-text interfaces] [J In graphical interfaces] ] [HLIST2 {Does it run on...?} [J Non-Debian *NIX-like systems? (Yes, and a few are tested)] [HLIST2 {Non-*NIX systems (e.g. Windows and Macs)?} [J Where to get Emacs for these systems] ] [J Other versions of Emacs besides GNU Emacs?] [J Other editors, like vi?] ] [HLIST2 {Current problems on which I'd like to have help:} [J Finding the directory where the \".el\"s for the current version of Emacs are] [J Finding the stem of the info files of the current Emacs (can be \"emacs\", \"emacs-e21\", etc)] [J I need an easy was to let the user install the Emacs manuals that are not present in the system] [J Porting to XEmacs] [J Bash's behaviour on here-documents in verbose mode is not so good as zsh's\; tcsh is even worse IIRC] [J Older Expects freak out on char 0's] ] ] }