unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dave Love <d.love@dl.ac.uk>
Cc: Emacs Developement List <emacs-devel@gnu.org>
Subject: Re: python-mode (python.el): python-backspace
Date: Mon, 17 May 2004 18:12:33 +0100	[thread overview]
Message-ID: <rzqbrkn0ygu.fsf@albion.dl.ac.uk> (raw)
In-Reply-To: <quack.20040516T1500.87n048c9sk@v-woof.quarl.org> (Karl Chen's message of "Sun, 16 May 2004 15:00:11 -0700")

Karl Chen <quarl@hkn.eecs.berkeley.edu> writes:

> Python.el's python-backspace:
>     Close the current block
>
>     Counter-intuitive in many cases, such as if point is already
>     left of where python-backspace moves indents to (backspace
>     moves the cursor rightward?!)

I don't understand that.

> I suggest python-backspace's behavior be changed so that: if point
> is <= where the current behavior would have indented to, then
> unindent by 1 python-indent level

I don't remember whether the behaviour was intended to be the same as
python-mode.el or not.  Anyhow, I don't object if someone cares to
change it.

I see the `python-backspace' doc string is unclear/incorrect.  I'd
suggest changing it to something like this for the current
implementation:

  "Maybe delete a level of indentation on the current line.
Do so if point is at the end of line's indentation.
Otherwise, just call `backward-delete-char-untabify'.
With ARG, repeat that many times."

  reply	other threads:[~2004-05-17 17:12 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-16 22:00 python-mode (python.el): python-backspace Karl Chen
2004-05-17 17:12 ` Dave Love [this message]
2004-05-17 17:38   ` Karl Chen
2004-05-18 16:51     ` Dave Love
2004-05-17 22:57 ` Richard Stallman
2004-05-18  6:19   ` Karl Chen
2004-05-19  1:25     ` Richard Stallman
2004-05-19 14:53       ` Stefan Monnier
2004-05-18 13:40   ` Stefan Monnier
2004-05-18 14:09     ` David Kastrup
2004-05-18 16:13       ` Andreas Schwab
2004-05-18 17:01     ` Dave Love
2004-05-18 18:28       ` Stefan Monnier
2004-05-27 14:21         ` Dave Love
2004-05-27 18:24           ` Stefan Monnier
2004-05-28 14:20             ` Richard Stallman
2004-05-29 11:33               ` Kai Grossjohann
2004-05-30 14:30                 ` Richard Stallman
2004-05-30 21:17                   ` Stefan Monnier
2004-06-01 14:57                     ` Richard Stallman
2004-06-04 15:44               ` Dave Love
2004-06-04 15:41             ` Dave Love
2004-06-05 13:48               ` Richard Stallman
2004-06-11 14:19                 ` Dave Love
2004-06-12  9:45                   ` Richard Stallman
2004-06-21 17:28                     ` Dave Love
2004-05-18 18:08     ` Karl Chen
2004-05-19  1:26     ` Richard Stallman
2004-05-19  1:26     ` Richard Stallman
2004-05-18 16:57   ` Dave Love
2004-05-19 13:45     ` Richard Stallman
2004-05-19 16:28       ` Karl Chen
2004-05-20 21:53       ` Dave Love
2004-05-21  6:03         ` Karl Chen
2004-05-23 18:28         ` Richard Stallman
2004-05-24  1:40           ` Miles Bader
2004-05-25 16:08             ` Dave Love

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=rzqbrkn0ygu.fsf@albion.dl.ac.uk \
    --to=d.love@dl.ac.uk \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).