unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kaushal <kaushal.modi@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>,
	20660@debbugs.gnu.org, m2ym.pub@gmail.com
Subject: bug#20660: 25.0.50; Window pops now issue "Args out of range" with popwin mode enabled
Date: Tue, 26 May 2015 17:03:14 +0000	[thread overview]
Message-ID: <CAFyQvY0r+0AAPAmOtNuOdbipkrEJTLboUn7egq1o-isF7h_COw@mail.gmail.com> (raw)
In-Reply-To: <5564856E.3030401@yandex.ru>

[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]

Also,to add to what I posted originally, `toggle-debug-on-error` does not
help  in this case as all I get in the *Backtrace* is:

Debugger entered--Lisp error: (args-out-of-range 1519)

Here's some new info:
- The Args out of range error seems to appear randomly.. I repeated doing
`C-h v save-place-mode`. At times the errors happened and at times it
didn;t.
- Also the integer in the argument to `args-out-of-range` showed up to be
different every time the error happened on doing C-h v on the same variable.

And "(setq debug-on-message "Args out of range")" does not trigger the
debug.
Is that because that message is printed by a C function?

On Tue, May 26, 2015 at 10:38 AM Dmitry Gutov <dgutov@yandex.ru> wrote:

> On 05/26/2015 05:31 PM, Kaushal wrote:
>
> > I don't get these Args out of range messages if I do not load popwin;
> > but also these messages did not appear a week ago with popwin enabled.
>
> Same here, but I don't use popwin. 'emacs -Q' doesn't show these errors,
> so it must be some other package I have installed.
>
> I haven't investigated yet which one it is.
>

[-- Attachment #2: Type: text/html, Size: 1491 bytes --]

  reply	other threads:[~2015-05-26 17:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26 14:31 bug#20660: 25.0.50; Window pops now issue "Args out of range" with popwin mode enabled Kaushal
2015-05-26 14:38 ` Dmitry Gutov
2015-05-26 17:03   ` Kaushal [this message]
2015-06-11 15:10     ` Kaushal
2015-06-11 15:56       ` Eli Zaretskii
2019-09-29 23:50 ` Stefan Kangas

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=CAFyQvY0r+0AAPAmOtNuOdbipkrEJTLboUn7egq1o-isF7h_COw@mail.gmail.com \
    --to=kaushal.modi@gmail.com \
    --cc=20660@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=m2ym.pub@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).