unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: wietse <wietse.j@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: indentation problem in python-mode
Date: Thu, 12 Apr 2007 18:14:17 +0200	[thread overview]
Message-ID: <461E5AD9.6030608@gmail.com> (raw)
In-Reply-To: <1176391813.893406.167770@n76g2000hsh.googlegroups.com>

wietse wrote:
> Hi,
> 
> I'm completely new to Emacs so plse bear with me.
> 
> I have a problem editing python files with emacs in that I'm unable to
> get the proper indentation after a ":" (I have to type in the spaces
> manually).
> When I type:
> 
> def my_func(parm):<RET> or <C-j>
> 
> emacs just never indents the next line.


I do not know python, but I tested with the python-mode that comes with 
Emacs 22 (in late beta test). RET does not indent next line, but C-j 
does in the example above

  reply	other threads:[~2007-04-12 16:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-12 15:30 indentation problem in python-mode wietse
2007-04-12 16:14 ` Lennart Borgman (gmail) [this message]
2007-04-12 18:02 ` Alexis Roda

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=461E5AD9.6030608@gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=wietse.j@gmail.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).