unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Karl Chen <quarl+dated+1085176814.c6e08d@hkn.eecs.berkeley.edu>,
	rms@gnu.org, emacs-devel@gnu.org
Subject: Re: python-mode (python.el): python-backspace
Date: 18 May 2004 14:28:13 -0400	[thread overview]
Message-ID: <m1fz9xa944.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <rzqr7thwtyp.fsf@albion.dl.ac.uk>

>> I'd suggest that if we start fiddling with such code, we introduce a
>> generic way to electrify backspace.  Otherwise people who want it
>> need to enable it separately (and differently) for each and every
>> major mode they use.

> But in general the `electric' behaviour will be different between
> modes, e.g. Python v. Lisp.

Then it's not what I have in mind.  What I have in mind is the kind of
"electric backspace" seen in python-mode or in cc-mode.  It can do
things like:
- delete hungrily all whitespace.
- delete to previous level of indentation.
Both of those are conceptually mode-independent (although the
implementation might be mode-dependent), just like M-; and others.
There is already the "untabify" version of backspace and I think we should
make it easier for people to change such things globally.


        Stefan

  reply	other threads:[~2004-05-18 18:28 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
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 [this message]
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=m1fz9xa944.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=quarl+dated+1085176814.c6e08d@hkn.eecs.berkeley.edu \
    --cc=rms@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).