From: Eli Zaretskii <eliz@gnu.org>
To: Thomas de Beauchene <thomas.de.beauchene@gmail.com>
Cc: 33384@debbugs.gnu.org
Subject: bug#33384: [PATCH] Fix zone.el when window is at the bottom of the buffer
Date: Fri, 16 Nov 2018 16:42:05 +0200 [thread overview]
Message-ID: <838t1tuls2.fsf@gnu.org> (raw)
In-Reply-To: <CAK=xY6KH5Y4WQnNo3-vLx77CuGtmPnkMTTQoH4Sbe5TE2NTsLw@mail.gmail.com> (message from Thomas de Beauchene on Fri, 16 Nov 2018 12:04:39 +0100)
[Please keep the bug address on the CC list; use "Reply to All".
> From: Thomas de Beauchene <thomas.de.beauchene@gmail.com>
> Date: Fri, 16 Nov 2018 12:04:39 +0100
>
> Thanks for the swift response.
>
> It is an issue that I am facing since I started using zone, when they
> integrated it in Spacemacs a few month ago. Anytime the window is past the
> buffer end (like the end of the buffer in the middle of the window) instead
> of starting, Zone just throws an error:
>
> let: Args out of range: #<buffer zone.el.gz>, 21124, 22313
>
> When I investigated I pinpointed the error to this exact line that I'm
> patching. The numbers *do* correspond to the values of (window-start) and
> (window-end). I then started playing around with it in a scratch buffer,
> and (window-end) would always return the size of the buffer plus one, which
> would always make (buffer-substring) throw an error when I ran it in
> eval-expression.
>
> Again, I had this behaviour in Spacemacs, so with a lot of packages and
> code on top of Emacs. I will try today to figure out the exact conditions,
> why you don't reproduce while I do. Already I could reproduce in zone.el.gz
> but not in *Messages* today.
>
> Any idea of what could alter the return value of (window-end) ?
Some defadvice, perhaps?
next prev parent reply other threads:[~2018-11-16 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 15:48 bug#33384: [PATCH] Fix zone.el when window is at the bottom of the buffer deb0ch
2018-11-16 8:42 ` Eli Zaretskii
[not found] ` <CAK=xY6KH5Y4WQnNo3-vLx77CuGtmPnkMTTQoH4Sbe5TE2NTsLw@mail.gmail.com>
2018-11-16 14:42 ` Eli Zaretskii [this message]
[not found] ` <CAK=xY6+yTP8BeEQn6z4hFJYFVfVzcFhHsryHwwAzeAE10SHTKw@mail.gmail.com>
2018-11-16 19:53 ` Eli Zaretskii
[not found] ` <CAK=xY6K3SDCivYiadnAvxC_mrH6-hkQK+6VnOpt+QCRoDVGMsA@mail.gmail.com>
2018-11-18 19:43 ` Eli Zaretskii
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=838t1tuls2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33384@debbugs.gnu.org \
--cc=thomas.de.beauchene@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).