From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: "Lennart Borgman \(gmail\)" <lennart.borgman@gmail.com>
Cc: help-gnu-emacs@gnu.org, weber <hugows@gmail.com>
Subject: Re: LISP routines for commenting
Date: Sat, 09 Aug 2008 19:04:05 +0200 [thread overview]
Message-ID: <87ljz66ry2.fsf@tux.homenetwork> (raw)
In-Reply-To: <489DC909.2080603@gmail.com> (Lennart Borgman's message of "Sat, 09 Aug 2008 18:42:49 +0200")
"Lennart Borgman (gmail)" <lennart.borgman@gmail.com> writes:
> Thierry Volpiatto wrote:
>> Python-mode provide a command for indenting that is bind to:
>>
>> C-c # ==> comment
>> C-u C-c # ==> uncomment
>> The command is: `py-comment-region'
>>
>> It is better to comment with that instead of the usual M-;
>> because it don't affect indentation after a block of commented code.
>
>
> Do you mean that this is a bug in the support for M-; in phyton-mode?
> Or is it a bug in M-;
>
I don't think it's a bug, it's just better to comment with the proper
function in python, especially if there is complex level of indentation
(loop followed with other loop and if if if...etc).
However M-; work in most cases.
So if it's a bug, it come from python-mode, because M-; normally have to
be used with python.el (is it working with python.el ?) because it is
the normal mode to use in emacs with python even if IMHO python-mode is
much better.
--
A + Thierry Volpiatto
Location: Saint-Cyr-Sur-Mer - France
next prev parent reply other threads:[~2008-08-09 17:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 8:36 LISP routines for commenting Alex Gusarov
2008-08-09 1:43 ` Joel J. Adamson
[not found] ` <mailman.16147.1218246548.18990.help-gnu-emacs@gnu.org>
2008-08-09 14:43 ` weber
2008-08-09 16:33 ` Thierry Volpiatto
2008-08-09 16:42 ` Lennart Borgman (gmail)
2008-08-09 17:04 ` Thierry Volpiatto [this message]
2008-08-09 17:11 ` Lennart Borgman (gmail)
2008-08-09 17:19 ` Thierry Volpiatto
2008-08-09 17:38 ` Lennart Borgman (gmail)
2008-08-09 18:29 ` Thierry Volpiatto
2008-08-14 8:07 ` Alex Gusarov
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=87ljz66ry2.fsf@tux.homenetwork \
--to=thierry.volpiatto@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=hugows@gmail.com \
--cc=lennart.borgman@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).