* get backtrace of handle-switch-frame
@ 2019-03-24 18:21 Amos Bird
2019-03-24 18:43 ` রে: " Ghosh, Partha
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: Amos Bird @ 2019-03-24 18:21 UTC (permalink / raw)
To: Help Gnu Emacs mailing list
Hello, is it possble to get the backtrace of function
`handle-switch-frame` so that I can find out the cause of an
unexpected frame switch event?
regards,
--
Amos Bird
amosbird@gmail.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* রে: get backtrace of handle-switch-frame
2019-03-24 18:21 get backtrace of handle-switch-frame Amos Bird
@ 2019-03-24 18:43 ` Ghosh, Partha
2019-03-24 18:51 ` Eli Zaretskii
2019-03-25 12:24 ` Stefan Monnier
2 siblings, 0 replies; 6+ messages in thread
From: Ghosh, Partha @ 2019-03-24 18:43 UTC (permalink / raw)
To: Amos Bird, Help Gnu Emacs mailing list
[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]
Dear Amos,
Please excuse my ignorance.....
I do not know how to get the backtrace of function
`handle-switch-frame`
When I tried it on the emacs window as M-x handle-switch-frame, it told me that handle-switch-frame must be bound to an event with parameters.
If possible, please can you tell me what should I do, and then I shall surely revert back.
With all the very best wishes and regards,
partha
------
পার্থ প্রতিম ঘোষ
[cid:81b610c9-3c4c-41cf-a099-dd9bef3d762b]
________________________________
থেকে: Amos Bird <amosbird@gmail.com>-এর পক্ষ থেকে help-gnu-emacs <help-gnu-emacs-bounces+ghoshpp=unisa.ac.za@gnu.org>
পাঠান: 24 মার্চ 2019 20.21
প্রতি: Help Gnu Emacs mailing list
বিষয়: get backtrace of handle-switch-frame
Hello, is it possble to get the backtrace of function
`handle-switch-frame` so that I can find out the cause of an
unexpected frame switch event?
regards,
--
Amos Bird
amosbird@gmail.com
[-- Attachment #2: Outlook-cotl01sx.jpg --]
[-- Type: image/jpeg, Size: 64417 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: get backtrace of handle-switch-frame
2019-03-24 18:21 get backtrace of handle-switch-frame Amos Bird
2019-03-24 18:43 ` রে: " Ghosh, Partha
@ 2019-03-24 18:51 ` Eli Zaretskii
2019-03-24 19:39 ` রে: " Ghosh, Partha
2019-03-25 12:24 ` Stefan Monnier
2 siblings, 1 reply; 6+ messages in thread
From: Eli Zaretskii @ 2019-03-24 18:51 UTC (permalink / raw)
To: help-gnu-emacs
> From: Amos Bird <amosbird@gmail.com>
> Date: Mon, 25 Mar 2019 02:21:32 +0800
>
> Hello, is it possble to get the backtrace of function
> `handle-switch-frame` so that I can find out the cause of an
> unexpected frame switch event?
I think you should be able to use debug-on-entry for that purpose.
^ permalink raw reply [flat|nested] 6+ messages in thread
* রে: get backtrace of handle-switch-frame
2019-03-24 18:51 ` Eli Zaretskii
@ 2019-03-24 19:39 ` Ghosh, Partha
2019-03-24 19:54 ` Eli Zaretskii
0 siblings, 1 reply; 6+ messages in thread
From: Ghosh, Partha @ 2019-03-24 19:39 UTC (permalink / raw)
To: Eli Zaretskii, help-gnu-emacs@gnu.org
[-- Attachment #1: Type: text/plain, Size: 1515 bytes --]
Dear Eli,
I did not get any input on the *Backtrace* buffer after I entered M-x debug-on-entry RET handle-switch-frame RET
Please find the output from emacs --debug-init:
********* output from emacs --debug-init**************
Debugger entered--Lisp error: (file-missing "Cannot open load file" "No such file or directory" "e2wm")
require(e2wm)
eval-buffer(#<buffer *load*> nil "/home/partha/.emacs" nil t) ; Reading at buffer position 697
load-with-code-conversion("/home/partha/.emacs" "/home/partha/.emacs" t t)
load("~/.emacs" t t)
#f(compiled-function () #<bytecode 0x255119>)()
command-line()
normal-top-level()
*******************************************************************
With all the very best wishes and regards,
partha
------
পার্থ প্রতিম ঘোষ
[cid:1c75408b-925b-44ac-81a4-173726b843f1]
________________________________
থেকে: Eli Zaretskii <eliz@gnu.org>-এর পক্ষ থেকে help-gnu-emacs <help-gnu-emacs-bounces+ghoshpp=unisa.ac.za@gnu.org>
পাঠান: 24 মার্চ 2019 20.51
প্রতি: help-gnu-emacs@gnu.org
বিষয়: Re: get backtrace of handle-switch-frame
> From: Amos Bird <amosbird@gmail.com>
> Date: Mon, 25 Mar 2019 02:21:32 +0800
>
> Hello, is it possble to get the backtrace of function
> `handle-switch-frame` so that I can find out the cause of an
> unexpected frame switch event?
I think you should be able to use debug-on-entry for that purpose.
[-- Attachment #2: Outlook-3aql21gp.jpg --]
[-- Type: image/jpeg, Size: 64417 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: রে: get backtrace of handle-switch-frame
2019-03-24 19:39 ` রে: " Ghosh, Partha
@ 2019-03-24 19:54 ` Eli Zaretskii
0 siblings, 0 replies; 6+ messages in thread
From: Eli Zaretskii @ 2019-03-24 19:54 UTC (permalink / raw)
To: help-gnu-emacs
> From: "Ghosh, Partha" <Ghoshpp@unisa.ac.za>
> Date: Sun, 24 Mar 2019 19:39:31 +0000
>
> I did not get any input on the *Backtrace* buffer after I entered M-x debug-on-entry RET handle-switch-frame
> RET
>
> Please find the output from emacs --debug-init:
> ********* output from emacs --debug-init**************
> Debugger entered--Lisp error: (file-missing "Cannot open load file" "No such file or directory" "e2wm")
> require(e2wm)
> eval-buffer(#<buffer *load*> nil "/home/partha/.emacs" nil t) ; Reading at buffer position 697
> load-with-code-conversion("/home/partha/.emacs" "/home/partha/.emacs" t t)
> load("~/.emacs" t t)
> #f(compiled-function () #<bytecode 0x255119>)()
> command-line()
> normal-top-level()
> *******************************************************************
What do you mean by "get any input"? What kind of input did youwant
or expect to get?
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: get backtrace of handle-switch-frame
2019-03-24 18:21 get backtrace of handle-switch-frame Amos Bird
2019-03-24 18:43 ` রে: " Ghosh, Partha
2019-03-24 18:51 ` Eli Zaretskii
@ 2019-03-25 12:24 ` Stefan Monnier
2 siblings, 0 replies; 6+ messages in thread
From: Stefan Monnier @ 2019-03-25 12:24 UTC (permalink / raw)
To: help-gnu-emacs
> Hello, is it possble to get the backtrace of function `handle-switch-frame`
> so that I can find out the cause of an unexpected frame switch event?
I'm not completely sure what you mean by "the backtrace of function
<...>", but I assume you want to get the backtrace at the point where
the function is called.
`M-x debug-on-entry RET handle-switch-frame RET` should do just that.
But I think you'll be very disappointed with the result: this is
a function bound to an event, and these are decoupled from the code that
generates/triggers the event by a buffer (this is the buffer that's used
to remember the keys you pressed while a long-running command is still
ongoing).
So the backtrace will likely tell you very little and specifically it
will not tell you the cause of the unexpected frame switch event.
Stefan
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2019-03-25 12:24 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-03-24 18:21 get backtrace of handle-switch-frame Amos Bird
2019-03-24 18:43 ` রে: " Ghosh, Partha
2019-03-24 18:51 ` Eli Zaretskii
2019-03-24 19:39 ` রে: " Ghosh, Partha
2019-03-24 19:54 ` Eli Zaretskii
2019-03-25 12:24 ` Stefan Monnier
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).