[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
`*' interactive spec in some text-killing functions
From: |
Juanma Barranquero |
Subject: |
`*' interactive spec in some text-killing functions |
Date: |
Wed, 27 Jun 2007 15:39:52 +0200 |
The following functions from simple.el do not have the `*' interactive
spec: zap-to-char, kill-line, kill-whole-line, kill-word,
backward-kill-word. (They don't have a call to
`barf-if-buffer-read-only', either).
Using any of them in a read-only buffer does not delete text, but it
moves the point forward (or backward, in the case of
`backward-kill-word'), which is weird.
Is that intended, or should they have `*' in the interactive spec?
Additionally, `overwrite-mode' and `binary-overwrite-mode' do not have
`*' either. It is customary not to do so for minor modes, it is an
oversight, or it is really preferred not to get an error message in
interactive uses of the overwrite modes?
Juanma
- `*' interactive spec in some text-killing functions,
Juanma Barranquero <=
- Re: `*' interactive spec in some text-killing functions, David Kastrup, 2007/06/27
- Re: `*' interactive spec in some text-killing functions, Juanma Barranquero, 2007/06/27
- Re: `*' interactive spec in some text-killing functions, Andreas Schwab, 2007/06/27
- Re: `*' interactive spec in some text-killing functions, Juanma Barranquero, 2007/06/27
- Re: `*' interactive spec in some text-killing functions, David Kastrup, 2007/06/27
- Re: `*' interactive spec in some text-killing functions, Juanma Barranquero, 2007/06/27
- Re: `*' interactive spec in some text-killing functions, David Kastrup, 2007/06/27
- Re: `*' interactive spec in some text-killing functions, Juanma Barranquero, 2007/06/27