all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Larry Evans <cppljevans@suddenlink.net>
To: help-gnu-emacs@gnu.org
Subject: Re: (debug) backtrace: how to show source code at current location.
Date: Wed, 05 Jan 2011 22:50:12 -0600	[thread overview]
Message-ID: <ig3hm5$9ms$1@dough.gmane.org> (raw)
In-Reply-To: <F7100AC12DA445C69C4C3E4B760E4B57@us.oracle.com>

On 01/05/11 21:55, Drew Adams wrote:
>> I just have to figure out the corresponding correction for:
>> (define-key c++-mode-map 'iso-left-tab 'c-insert-my-shift-tab)
> 
> (define-key c++-mode-map [iso-left-tab] 'c-insert-my-shift-tab)
> 
> You need to learn how to fish.  The manual is your friend.
> C-h i
> m Elisp
> i define-key
> 
Thanks Drew.
Doing that got me to an info page with:

     If KEY is `[t]', this sets the default binding in KEYMAP.  When an
     event has no binding of its own, the Emacs command loop uses the
     keymap's default binding, if there is one.

but that doesn't tell me what are the possible values for t in `[t]'.
How did you know that "iso-left-tab" was a possible value for t?
As mentioned in my other post, I found grep.el had "backtab" instead
of "iso-left-tab".  I tried fishing through several info files after
the define-key one; however, none I viewed showed what the possible
values were for the t in [t].  Where is this information?

TIA.

  -regards,
  Larry





  reply	other threads:[~2011-01-06  4:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-05 18:07 (debug) backtrace: how to show source code at current location Larry Evans
2011-01-05 19:06 ` Drew Adams
2011-01-05 19:43   ` Larry Evans
2011-01-05 19:54     ` Larry Evans
2011-01-05 19:58     ` Drew Adams
     [not found]   ` <mailman.0.1294256637.13904.help-gnu-emacs@gnu.org>
2011-01-05 23:31     ` Tim X
2011-01-06  2:53       ` Larry Evans
2011-01-06  3:50         ` Larry Evans
2011-01-06  3:55         ` Drew Adams
2011-01-06  4:50           ` Larry Evans [this message]
2011-01-06 13:57             ` Drew Adams

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='ig3hm5$9ms$1@dough.gmane.org' \
    --to=cppljevans@suddenlink.net \
    --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.
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.