From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: jfkoenig@vipb.com (John F. Koenig) Newsgroups: gmane.emacs.help Subject: newbie tiny-tools question Date: 14 Feb 2003 14:07:29 -0800 Organization: http://groups.google.com/ Sender: help-gnu-emacs-bounces+gnu-help-gnu-emacs=m.gmane.org@gnu.org Message-ID: NNTP-Posting-Host: main.gmane.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: main.gmane.org 1045260610 28092 80.91.224.249 (14 Feb 2003 22:10:10 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Fri, 14 Feb 2003 22:10:10 +0000 (UTC) Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 18jo20-0007Ie-00 for ; Fri, 14 Feb 2003 23:10:04 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18jo2r-0007n1-01 for gnu-help-gnu-emacs@m.gmane.org; Fri, 14 Feb 2003 17:10:57 -0500 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!postnews1.google.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 49 Original-NNTP-Posting-Host: 128.3.132.218 Original-X-Trace: posting.google.com 1045260449 31628 127.0.0.1 (14 Feb 2003 22:07:29 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: 14 Feb 2003 22:07:29 GMT Original-Xref: shelby.stanford.edu gnu.emacs.help:110219 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: help-gnu-emacs-bounces+gnu-help-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.help:6721 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:6721 Hello, I finally "decoded" the disconnect between the installation paragraph in the README and what was actually required... Actually not that confusing once one realizes that the path refers to the file ending in tinypath.el; not a "directory root" of the tiny-tools package. Maybe the problem that emacs novices have when they first encounter the tiny-tools installation instructions is this... possibly because they are not familiar with the emacs lisp load construct and they fact that "tinypath" refers to a file (ending in '.el' which is not to be expressed), not a directory. Mine looks something like this: (load "/Full-Path-To-My-Home-Dir/elisp/packages/tiny-tools-cvs/lisp/tiny/tinypath") If the above is wrong or otherwise misguided please tell me. :) For example, is the tiny-tools directory, in a sense, the tiny-tools package? And hence it should go into the package directory along-side the other packages that will inevitably be downloaded via something like perl-webget. I was considering looking into that tool for more insight into what Jaari is intending... My other significant question is where does a major-mode such as python-mode.el go? Does it go here: "/Full-Path-To-My-Home-Dir/elisp/packages" That seems reasonable... as it would be counter-productive to put it inside the tiny-tools distribution... wihch, BTW, the contents of which are being copied from the SourceForge (tinytools) CVS repository. So with that, what tweak do I need to make to the tiny-tools configuration to cause the python-mode to be invoked when I load a file with \*.py ? I see the instructions at the python-mode page indicating one needs to set the mode path and make file associations... Is it recommended to put the same sort of emacs lisp instructions when using tiny-tools? I was kinda hoping for something sort of automatic... when I placed the python-mode.el file somewhere and restarted emacs. (I am using version 21.2.1 and 21.1.1 on Linux and OS X, respectively.) ## Some hand-holding would be much appreciated... :))) Thanks and happy friday...