all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: bolega <gnuist006@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: An instructive example of trace-function and some example of  debugging
Date: Sat, 12 Jun 2010 10:42:14 -0700 (PDT)	[thread overview]
Message-ID: <ca944095-b2d2-46a0-93cc-44008c579560@a30g2000yqn.googlegroups.com> (raw)
In-Reply-To: 1af7c938-1f8d-414c-8970-f82961c8b0cd@y11g2000yqm.googlegroups.com

On Jun 10, 1:27 pm, bolega <gnuist...@gmail.com> wrote:
> An instructive example of trace-function and some example of
> debugging, for example, some of the error that pops up in lower window
> of emacs and how to read/interpret it. Alternatively, a link to some
> page or elisp manual but I am sure an expert here would have a
> superior instruction as many replies here have shown.
>
> Thanks
> Bolega
>
> trace-function is an interactive autoloaded Lisp function in `trace'.
> [Arg list not available until function definition is loaded.]
>
> Traces FUNCTION with trace output going to BUFFER.
> For every call of FUNCTION Lisp-style trace messages that display
> argument
> and return values will be inserted into BUFFER. This function
> generates the
> trace advice for FUNCTION and activates it together with any other
> advice
> there might be!! The trace BUFFER will popup whenever FUNCTION is
> called.
> Do not use this to trace functions that switch buffers or do any other
> display oriented stuff, use `trace-function-background' instead.

Sometimes, in emacs, error takes places and the mode gets nested
inside many brackets.

[(((.lisp...)))]

above line recalling from memory

what does it mean ? C-g does not get out of it.

What to do ?





  reply	other threads:[~2010-06-12 17:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-10 20:27 [REQ] An instructive example of trace-function and some example of debugging bolega
2010-06-12 17:42 ` bolega [this message]
     [not found] ` <d48c2b9e-0853-448e-9992-d71e87fcccd0@j4g2000yqh.googlegroups.com>
2010-06-13 15:07   ` Icarus Sparry
2010-06-13 20:31     ` bolega
2010-06-14  7:14       ` Icarus Sparry

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=ca944095-b2d2-46a0-93cc-44008c579560@a30g2000yqn.googlegroups.com \
    --to=gnuist006@gmail.com \
    --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.