[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: "Use font-lock-support-mode rather than calling lazy-lock-mode"
From: |
Michael Welsh Duggan |
Subject: |
Re: "Use font-lock-support-mode rather than calling lazy-lock-mode" |
Date: |
Tue, 21 Nov 2006 02:41:15 -0500 |
User-agent: |
Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.91 (gnu/linux) |
ishikawa <address@hidden> writes:
> About 30 minutes ago, I tried (backtrace). It seems to me that to
> obtain a useful output and not interfering the normal operation of
> various modes, I need to create a separate buffer, say "*backtrace*"
> and then dump the contents of the output of (backtrace) there, and
> then resume the normal operation. (It seems to me that "edebug"
> package just does that, but I have not figured out exactly how to do
> it.)
>
> Without such a trick, backtrace seems to create output *somewhere*
> and normal operations such as electric-dired and others don't work
> anymore.
(with-output-to-temp-buffer "*Backtrace*"
(backtrace))
--
Michael Welsh Duggan
(address@hidden)
- "Use font-lock-support-mode rather than calling lazy-lock-mode", ishikawa, 2006/11/20
- Re: "Use font-lock-support-mode rather than calling lazy-lock-mode", Jason Rumney, 2006/11/20
- Re: "Use font-lock-support-mode rather than calling lazy-lock-mode", Richard Stallman, 2006/11/21
- Re: "Use font-lock-support-mode rather than calling lazy-lock-mode", ishikawa, 2006/11/22
- Re: "Use font-lock-support-mode rather than calling lazy-lock-mode", Richard Stallman, 2006/11/22
- Re: "Use font-lock-support-mode rather than calling lazy-lock-mode", ishikawa, 2006/11/24
- Re: "Use font-lock-support-mode rather than calling lazy-lock-mode", Richard Stallman, 2006/11/25
- Re: "Use font-lock-support-mode rather than calling lazy-lock-mode", ishikawa, 2006/11/27
- Re: "Use font-lock-support-mode rather than calling lazy-lock-mode", Eli Zaretskii, 2006/11/27
- Re: "Use font-lock-support-mode rather than calling lazy-lock-mode", ishikawa, 2006/11/28