From: jfkoenig@vipb.com (John F. Koenig)
Subject: Re: newbie tiny-tools question
Date: 20 Feb 2003 18:24:12 -0800 [thread overview]
Message-ID: <f1a388f1.0302201824.325ac5d9@posting.google.com> (raw)
In-Reply-To: f1a388f1.0302141407.40a0d7c9@posting.google.com
Desperately following up to my own post, ova'here. :)
Hopefully, by simplifying my post, my questions will be more readily
apparent. The author, jari, appears to be ignoring private e-mail that
might be regarded as support-related.
I was able to install tiny-tools such that the file "tinypath.el" gets
loaded -- which appears to load a large amount tiny-tools config code.
My simple questions:
1. Where in the tiny-tools heirarchy would one place the file
python-mode.el?
2. After installing python-mode.el in the proper location, must I
modify a load path? If so, what do I do and where?
3. Must I then make a config change to allow the autoloading of this
major mode?
4. And finally, what config changes must I make for the automatic file
associations ".py". I was hoping that there is a file in tiny-tools
for this purpose.
Thank you (anybody)
:)
####
jfkoenig@vipb.com (John F. Koenig) wrote in message news:<f1a388f1.0302141407.40a0d7c9@posting.google.com>...
> Hello,
>
> I finally "decoded" the disconnect between the installation paragraph
> in the README <http://tiny-tools.sourceforge.net/README.html#quick_install__personal>
> 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...
next prev parent reply other threads:[~2003-02-21 2:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 22:07 newbie tiny-tools question John F. Koenig
2003-02-21 2:24 ` John F. Koenig [this message]
2003-02-21 3:03 ` Unknown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f1a388f1.0302201824.325ac5d9@posting.google.com \
--to=jfkoenig@vipb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).