New user questions ... be gentle

[Quasimodo]

File Association in Windows:

(Extract from Windows help topic: "file association")
1) In My Computer or Windows Explorer, on the View menu, click Folder
Options.
2) Click the File Types tab, and then click New Type.
3) In Description of type, type the appropriate information for the new file
type.
4) In Associated extension, type the extension you want for the new file
type.
5) Click New.
6) In Action, enter the action that you want to define (such as Open or
Print).
7) In Application used to perform action, enter the command that you want to
complete this action, and then click OK.
8) Repeat steps 6 and 7 for as many actions as you want to define for this
file type.
Note
Creating a file type is similar to associating a file, but when you create a
file type, you can specify actions for more than just opening the file, such
as the program to be used for printing the document.

Hope that helps.

Jose

"Steve Marx" <sm004i at mail.rochester.edu> wrote in message
news:8np2ql$6qe1 at biko.cc.rochester.edu...
> In the Windows world it's typically done by "associating" the .tcl
extension
> to a specific application (your Python interpreter).  This is similar to
the
> way that HTML files and text files can be double-clicked and load in the
> right application.  Most installations should make this assocation for
> you... don't recall how to do it by hand, but it's not hard.
>
>         Steve
>
> Grant Edwards <nobody at nowhere.nohow> wrote in message
> news:7PTn5.6771$6E.1644550 at ptah.visi.com...
> > On 20 Aug 2000 09:41:28 -0400, François Pinard <pinard at iro.umontreal.ca>
> wrote:
> >
> > >> I may be wrong on this but some scripts look as thought they are
> > >> executable like .exe files.  How is this done?
> > >
> > >From your question, I presume you work on Windows, while my culture is
> > >more on the Unix side.  I'm sure this is quite doable on both
platforms.
> > >On Linux, you just mark your script as executable (with `chmod +x
FILE')
> > >and ensure it starts with the line `#/usr/bin/env python'.
> >
> > that should be #!/usr/bin/...
> >
> > --
> > Grant Edwards                   grante             Yow!  Let me do my
> TRIBUTE
> >                                   at               to FISHNET
STOCKINGS...
> >                                visi.com
>
>