unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Gary Wessle <phddas@yahoo.com>
Subject: Re: python mode
Date: 23 Apr 2006 21:53:38 +1000	[thread overview]
Message-ID: <87lktwjynx.fsf@localhost.localdomain> (raw)
In-Reply-To: mailman.790.1145740262.9609.help-gnu-emacs@gnu.org

Peter Dyballa <Peter_Dyballa@Web.DE> writes:

> Am 22.04.2006 um 22:08 schrieb Gary Wessle:
> 
> > in my debian testing system
> > # locate python.el
> > /usr/share/emacs/site-lisp/semantic/wisent/wisent-python.el
> 
> So try this! If it's not sufficient get GNU Emacs source and compile,
> if you can't find a useful deb package! Check load-path whether it
> contains /usr/share/emacs/site-lisp/semantic/wisent, otherwise you
> would need add this component. ( (add-to-list 'load-path "...") )
> 
> BTW, you've located the wisent-python.el file in the site-lisp tree.
> So this is definitely not a GNU Emacs file, but something specific to
> your system. The GNU Emacs one would be in /usr/local/share/emacs/
> <version number>/lisp/progmodes ...

the one that comes close is  "/usr/share/emacs/21.4/lisp/progmodes"
in it there is no file about python-mode.elc or any thing for python
for that matter. with debian, I'd rather not start compiling my own
emacs from source because my in-ability to understand how the rest of
the system interact with emacs and visa-versa and how to satisfy that
not to have any future problems. I got python-mode-1.0.tar.gz and in
it there is 
doctest-mode.el  
pycomplete.el	
pycomplete.py  
python-mode.el
semantic.cache

should I just move python-mode.el to ../progmodes/ and compile? as it
said in the installation instruction in python-mode.el?
if so, could you tell me how to compile the file so that it is .elc
like all the other files in progmodes?

thank you

  parent reply	other threads:[~2006-04-23 11:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-22  8:28 python mode Gary Wessle
2006-04-22  9:03 ` Peter Dyballa
     [not found] ` <mailman.763.1145696607.9609.help-gnu-emacs@gnu.org>
2006-04-22  9:28   ` Gary Wessle
2006-04-22 10:18     ` Peter Dyballa
     [not found]     ` <mailman.764.1145701120.9609.help-gnu-emacs@gnu.org>
2006-04-22 10:34       ` Gary Wessle
2006-04-22 11:11         ` Peter Dyballa
     [not found]         ` <mailman.767.1145704577.9609.help-gnu-emacs@gnu.org>
2006-04-22 20:08           ` Gary Wessle
2006-04-22 21:10             ` Peter Dyballa
     [not found]             ` <mailman.790.1145740262.9609.help-gnu-emacs@gnu.org>
2006-04-23 11:53               ` Gary Wessle [this message]
2006-04-23 12:54                 ` Peter Dyballa
2006-04-24  8:48 ` Stefan Monnier
2006-04-24 10:11   ` Tim X
2006-04-25  8:27     ` tomás zerolo
2006-04-25 11:32     ` Gary Wessle
2006-04-25 21:50       ` maru dubshinki
2006-04-25 22:10       ` Tim X
2006-04-26  8:25       ` tomás zerolo

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=87lktwjynx.fsf@localhost.localdomain \
    --to=phddas@yahoo.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).