unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org, rms@gnu.org, kifer@cs.sunysb.edu,
	"Kim F. Storm" <storm@cua.dk>
Subject: Re: How to avoid insert anything without switching to read only
Date: Mon, 11 Jul 2005 01:05:26 +0200	[thread overview]
Message-ID: <851x66b6tl.fsf@lola.goethe.zz> (raw)
In-Reply-To: <42D1A191.6050509@student.lu.se> (Lennart Borgman's message of "Mon, 11 Jul 2005 00:30:41 +0200")

Lennart Borgman <lennart.borgman.073@student.lu.se> writes:

> Kim F. Storm wrote:
>
>>"Richard M. Stallman" <rms@gnu.org> writes:
>>
>>>What you should do is rebind those characters to run
>>>another command, one that does your special thing
>>>and calls self-insert.
>>>    
>>>
>>
>>Or use the command remap feature.
>>
> Thanks, but I am not able to understand how to apply any of your
> suggestions in a case like this. The problem is that the keyboard
> keys to change are all those that are outside a set of those defined
> to useful things (say a-z for simplicity). All other keys should be
> defined to do nothing. There are plenty of potential keys (65K). It
> does not seem to be possible to handle them all separately.
>
> Can you please explain a little bit more in detail how you think
> this could be done? Could the actual available keyboard keys in a
> specific situation in some way be listed?

I don't understand why it is worth doing in the first place.  Why not
just let those characters self-insert?  They don't have any other
meaning in vi.  What use is it to have them beep?

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2005-07-10 23:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-09  8:43 How to avoid insert anything without switching to read only Lennart Borgman
2005-07-10  5:19 ` Richard M. Stallman
2005-07-10 22:09   ` Kim F. Storm
2005-07-10 22:30     ` Lennart Borgman
2005-07-10 23:05       ` David Kastrup [this message]
2005-07-10 23:32         ` Lennart Borgman
2005-07-11  8:09       ` Kim F. Storm
2005-07-11 13:37 ` Stefan Monnier
2005-07-11 13:52   ` Lennart Borgman

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=851x66b6tl.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=kifer@cs.sunysb.edu \
    --cc=rms@gnu.org \
    --cc=storm@cua.dk \
    /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).