|
|
 Up |
|
|
  |
Author: Davin PearsonDavin Pearson Date: Sep 15, 2008 22:52
When I execute M-x find-file it says Find
File:
Why I press cursor left a few times and then try to press a key,
it
says: "Text is read only". Surely a more natural behavour would be
to
beep and not allow the user to type in that character in the first
place. What
gives?
|
| |
|
| | 6 Comments |
|
|
Author: Pascal J. BourguignonPascal J. Bourguignon Date: Sep 15, 2008 23:26
Davin Pearson gmail.com> writes:
> When I execute M-x find-file it says Find
> File:
>
> Why I press cursor left a few times and then try to press a key, it
> says: "Text is read only". Surely a more natural behavour would be
> to beep and not allow the user to type in that character in the
> first place. What gives?
--
__Pascal Bourguignon__ http://www.informatimago.com/
HEALTH WARNING: Care should be taken when lifting this product,
since its mass, and thus its weight, is dependent on its velocity
relative to the user.
|
| |
|
| | no comments |
|
|
Author: Daniel PittmanDaniel Pittman Date: Sep 16, 2008 00:29
> Davin Pearson gmail.com> writes:
>>> When I execute M-x find-file it says Find
>> File:
>>
>> Why I press cursor left a few times and then try to press a key, it
>> says: "Text is read only". Surely a more natural behavour would be
>> to beep and not allow the user to type in that character in the
>> first place. What gives?
This is a traditional default; try:
M-x customize-variable minibuffer-prompt-properties
Enable the "Don't Enter" option and save your changes, which will
implement what you expect. (Well, no beep, but you can't move over the
text any longer.)
|
| Show full article (1.02Kb) |
| no comments |
|
|
Author: Davin PearsonDavin Pearson Date: Sep 16, 2008 01:44
On Sep 16, 7:29 pm, Daniel Pittman rimspace.net> wrote:> This is a traditional default; try:
>
> M-x customize-variable minibuffer-prompt-properties
>
> Enable the "Don't Enter" option and save your changes, which will
> implement what you expect. (Well, no beep, but you can't move over the
> text any longer.)
The following code appears to work:
(setq minibuffer-prompt-properties (remove 'read-only minibuffer-
prompt-properties))
|
| |
| no comments |
|
|
Author: Lennart Borgman (gmail)Lennart Borgman (gmail) Date: Sep 16, 2008 01:57
> Davin Pearson gmail.com> writes:
> >> When I execute M-x find-file it says Find
>> File:
>>
>> Why I press cursor left a few times and then try to press a key, it
>> says: "Text is read only". Surely a more natural behavour would be
>> to beep and not allow the user to type in that character in the
>> first place. What gives?
I think that the message "Text is read-only" is a bit more helpful then
just beeping since just a beep would not distinguish between this case
and the case where just some letters are accepted. (A letter might be
bound to a command in sometimes.)
|
| |
| no comments |
|
|
Author: Daniel PittmanDaniel Pittman Date: Sep 16, 2008 06:11
Davin Pearson gmail.com> writes:> On Sep 16, 7:29 pm, Daniel Pittman rimspace.net> wrote:>> This is a traditional default; try:
>>
>> M-x customize-variable minibuffer-prompt-properties
>>
>> Enable the "Don't Enter" option and save your changes, which will
>> implement what you expect. (Well, no beep, but you can't move over the
>> text any longer.)
>
> The following code appears to work:
>
> (setq minibuffer-prompt-properties (remove 'read-only minibuffer-
> prompt-properties))
Ouch. That risks causing *serious* breakage:
`minibuffer-prompt-properties' is a plist, which means that it needs to
have an even number of elements.
|
| Show full article (1.24Kb) |
| no comments |
|
|
|
|
|
Author: XahXah Date: Sep 16, 2008 13:38
Davin Pearson asked:
Q: how to stop cursor moving over to prompt in minibuffer
Daniel Pittman wrote:
A:
M-x customize-variable minibuffer-prompt-properties
Enable the "Don't Enter" option and save your changes
Thanks a lot!
When i switched to emacs in about 2006 from 4 years of xemacs, i was
quite annoyed by this behavior. I remember i posted this question, i
got some silly responses from emacs regulars in comp.emacs, who says
that something to the effect that “sometimes you need to copy the
prompt”.
in my opinion, this is one of the usability problem, so obvious yet
some of the tech geekers dont seem to be able to see it.
i'm going to file a bug report now.
Xah
∑ http://xahlee.org/
☄
|
| |
| no comments |
|
|
