From: Unknown <unknown@unknown.invalid>
Subject: Re: newbie tiny-tools question
Date: Fri, 21 Feb 2003 03:03:41 GMT [thread overview]
Message-ID: <hGg5a.30091$Zr%.8442@news01.bloor.is.net.cable.rogers.com> (raw)
In-Reply-To: f1a388f1.0302201824.325ac5d9@posting.google.com
John F. Koenig wrote:
> 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.
Why do you need tiny-tools. Seriously, it's been around a long time, I'm
interested in learning what are some killer features in it?
> My simple questions:
>
> 1. Where in the tiny-tools heirarchy would one place the file
> python-mode.el?
You don't. AFAIK, keep tiny tools in its own directory structure, install
your customizations else where.
> 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.
Your next three questions are explicitly addressed on the python.el
installation page. I suggest you look there.
hth.
--
Le
prev parent reply other threads:[~2003-02-21 3:03 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
2003-02-21 3:03 ` Unknown [this message]
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='hGg5a.30091$Zr%.8442@news01.bloor.is.net.cable.rogers.com' \
--to=unknown@unknown.invalid \
/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).