unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Pawel <paulino90@tenbit.pl>
To: emacs mailing list <help-gnu-emacs@gnu.org>
Subject: abbrevs are not expanded with <SPC> in debugger(gud) mode
Date: Wed, 11 Jul 2007 18:14:44 +0200	[thread overview]
Message-ID: <18069.500.587850.602026@localhost.localdomain> (raw)

Hallo group members.
I added the following abbrev to debugger (gud) mode.

(define-abbrev gud-mode-abbrev-table "ir" "info reg ")

It is expanded using C-x a e, so it got "installed" properly.

Unfortunatelly <SPC> does not expand it.

Just to compare, I added the same abbrev to c-mode and expansion with <SPC> works fine there.

In both the modes, <SPC> key is handled by:
self-insert-command

In both the modes, <SPC> belongs to " " class ( Command:(string (char-syntax ?\ )), returns " " for both the modes).

Have You got idea what is the reason?

Regards,
Pawel.

             reply	other threads:[~2007-07-11 16:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-11 16:14 Pawel [this message]
2007-07-11 16:22 ` abbrevs are not expanded with <SPC> in debugger(gud) mode Pawel

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=18069.500.587850.602026@localhost.localdomain \
    --to=paulino90@tenbit.pl \
    --cc=help-gnu-emacs@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.
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).