From: moueza <mouezapeter@gmail.com>
To: Help-gnu-emacs@gnu.org
Subject: scroll backtrace
Date: Wed, 15 Oct 2008 21:59:45 -0700 (PDT) [thread overview]
Message-ID: <20007149.post@talk.nabble.com> (raw)
Hi,
When my I've opened 2 files,in 2 frames:if I scroll the first one until the
end or beginning, then in the other frame,the second file is hidden by the
"Backtrace" buffer:
scroll-up()
byte-code("\300 \210\202 " [scroll-up] 1)
mwheel-scroll((double-mouse-5 (#<window 3 on *Customize Group: Scrolling*>
982 (458 . 139) 136690598 nil 982 (45 . 5) nil (458 . 56) (10 . 15)) 2))
call-interactively(mwheel-scroll)
And in options, neither
"Enter debugger on error"
nor "Enter debugger on Quit " are checked
So how can I prevent this backtrace buffer to occur and hide my file and
interrupting me in my work?
--
View this message in context: http://www.nabble.com/scroll-backtrace-tp20007149p20007149.html
Sent from the Emacs - Help mailing list archive at Nabble.com.
next reply other threads:[~2008-10-16 4:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 4:59 moueza [this message]
2008-10-16 8:59 ` scroll backtrace Peter Dyballa
2008-10-16 18:46 ` moueza
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=20007149.post@talk.nabble.com \
--to=mouezapeter@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.
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).