all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Chris Moore" <dooglus@gmail.com>
To: "Stefan Monnier" <monnier@iro.umontreal.ca>
Cc: emacs-pretest-bug@gnu.org, rms@gnu.org
Subject: Re: hexl: doesn't play nicely with dynamic-completion-mode
Date: Mon, 10 Sep 2007 20:43:50 +0200	[thread overview]
Message-ID: <a9691ee20709101143i48439faapb0f788e659f1581a@mail.gmail.com> (raw)
In-Reply-To: <jwvfy1m8v7n.fsf-monnier+emacs@gnu.org>

On 9/10/07, Stefan Monnier <monnier@iro.umontreal.ca> wrote:

> hexl-mode should probably install a before-change-function that checks that
> this-command is among the supported ones.  This won't fix those problems,
> but will at least catch them before they corrupt the buffer.

Is there some way for a before-change-function to prevent a change?
It can call 'error to prevent the change once, but this clears the
before-change-function handler, so the 'bad' key won't be caught a 2nd
time.  Also, I notice that 'this-command is
'completion-separator-self-insert-command rather than
'self-insert-command in the hexl-mode before-change-function (after
applying Richard's fix), so hexl-mode would need to know about all the
modes which remap self-insert-command.

  reply	other threads:[~2007-09-10 18:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m2r6tcu25g.fsf@gmail.com>
2007-09-08 14:47 ` hexl: doesn't play nicely with dynamic-completion-mode Chris Moore
     [not found]   ` <E1IUCIj-0000B4-Rz@fencepost.gnu.org>
2007-09-09 18:01     ` Chris Moore
2007-09-10  1:13       ` Richard Stallman
2007-09-10 11:35         ` Chris Moore
2007-09-10 14:14           ` Stefan Monnier
2007-09-10 18:43             ` Chris Moore [this message]
2007-09-10 20:20               ` Stefan Monnier
2007-09-13  8:26                 ` Johan Bockgård

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a9691ee20709101143i48439faapb0f788e659f1581a@mail.gmail.com \
    --to=dooglus@gmail.com \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.