* can't open new frame
@ 2015-04-28 21:32 Hubert Chathi
2015-04-30 19:35 ` Michael Heerdegen
0 siblings, 1 reply; 3+ messages in thread
From: Hubert Chathi @ 2015-04-28 21:32 UTC (permalink / raw)
To: help-gnu-emacs
Sometimes, when I try to open a new frame (C-x 5 2), I get a "Wrong type
argument: number-or-marker-p, nil" message, and no frame opens. It
seems to work fine when I start emacs, but after a while, it stops
working, and won't work from then on until I restart emacs, so it may be
some mode or package that I'm using that's triggering this behaviour
when it gets loaded or run.
I tried "M-x toggle-debug-on-error RET C-x 5 2", but it doesn't give me
any information (the debug buffer doesn't show up).
Has anyone else seen this? Any ideas on how to debug this since
debug-on-error doesn't seem to be working?
--
Hubert Chathi - Email/Jabber: hubert@uhoreg.ca - http://www.uhoreg.ca/
PGP/GnuPG key: 4096R/113A1368 (Key available at pool.sks-keyservers.net)
Fingerprint: F24C F749 6C73 DDB8 DCB8 72DE B2DE 88D3 113A 1368
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: can't open new frame
2015-04-28 21:32 can't open new frame Hubert Chathi
@ 2015-04-30 19:35 ` Michael Heerdegen
2015-05-01 19:55 ` Hubert Chathi
0 siblings, 1 reply; 3+ messages in thread
From: Michael Heerdegen @ 2015-04-30 19:35 UTC (permalink / raw)
To: Hubert Chathi; +Cc: help-gnu-emacs
Hubert Chathi <hubert@uhoreg.ca> writes:
> Any ideas on how to debug this since debug-on-error doesn't seem to be
> working?
Try setting `debug-on-signal'. If that doesn't help, try with
`debug-on-message'.
If the error is reproducible once it occurs, you can also try to debug
using the build-in debugger, e.g. via `debug-on-entry'.
HTH,
Michael.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: can't open new frame
2015-04-30 19:35 ` Michael Heerdegen
@ 2015-05-01 19:55 ` Hubert Chathi
0 siblings, 0 replies; 3+ messages in thread
From: Hubert Chathi @ 2015-05-01 19:55 UTC (permalink / raw)
To: help-gnu-emacs
On Thu, 30 Apr 2015 21:35:43 +0200, Michael Heerdegen <michael_heerdegen@web.de> said:
> Hubert Chathi <hubert@uhoreg.ca> writes:
>> Any ideas on how to debug this since debug-on-error doesn't seem to
>> be working?
> Try setting `debug-on-signal'. If that doesn't help, try with
> `debug-on-message'.
> If the error is reproducible once it occurs, you can also try to debug
> using the build-in debugger, e.g. via `debug-on-entry'.
Thanks for the information. Unfortunately, I didn't manage to get
debug-on-signal or debug-on-message to work.
I did manage to figure it out, though, since I ended up having to
restart my emacs, and I tried doing C-x 5 2 every once in a while. It
turns out that it's somehow caused by jabber-activity-mode from
emacs-jabber. I've disabled it for now, and I'll be posting on the
emacs-jabber list to see if someone there can help out.
--
Hubert Chathi - Email/Jabber: hubert@uhoreg.ca - http://www.uhoreg.ca/
PGP/GnuPG key: 4096R/113A1368 (Key available at pool.sks-keyservers.net)
Fingerprint: F24C F749 6C73 DDB8 DCB8 72DE B2DE 88D3 113A 1368
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-05-01 19:55 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-04-28 21:32 can't open new frame Hubert Chathi
2015-04-30 19:35 ` Michael Heerdegen
2015-05-01 19:55 ` Hubert Chathi
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).