From: Kaushal Modi <kaushal.modi@gmail.com>
To: 25941@debbugs.gnu.org, Vibhav Pant <vibhavp@gmail.com>,
Oleh Krehel <ohwoeowho@gmail.com>
Subject: bug#25941: 26.0.50; Different code behavior between using the auto-compiled and evaled versions
Date: Thu, 09 Mar 2017 16:31:26 +0000 [thread overview]
Message-ID: <CAFyQvY1m0vmpqpM8QLLnz0fDqyE=FjLq6aaSXR3YC-BZwbJajw@mail.gmail.com> (raw)
In-Reply-To: <CAFyQvY1CL0tFqTryDfV=OLWBi+sFzG2WcHnXwb4kOJVBoadxWA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]
Hi Vibhav,
This issue seems to be related to the switch bytecode change.
Can you please review it.
The code snippet in
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25941#5 returns
t on emacs 25.2 but nil on emacs master. That is messing up the
avy-goto-line function (avy package).
avy--process does contain the cond form which is affected by the switch
bytecode change.
If I delete the .elc, the issue goes away.
On Fri, Mar 3, 2017 at 7:12 AM Kaushal Modi <kaushal.modi@gmail.com> wrote:
> Here's a set of updates that could probably help trace the problem:
>
> - I rebuilt emacs from master using make bootstrap, but the problem
> persists.
> - I see the problem when I do "M-x avy-goto-line 10" but not when I do
> "M-: (avy-goto-line 10)". So the bug triggers only during interactive
> execution?
>
> A workaround for now is to delete the avy.elc file.
>
> Does the avy--process code not work well with the recently byte compiler
> incompatibility in the master branch?
> --
>
> Kaushal Modi
>
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 2004 bytes --]
next prev parent reply other threads:[~2017-03-09 16:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 23:43 bug#25941: 26.0.50; Different code behavior between using the auto-compiled and evaled versions Kaushal Modi
2017-03-03 12:12 ` Kaushal Modi
2017-03-09 16:31 ` Kaushal Modi [this message]
2017-03-09 18:23 ` Vibhav Pant
2017-03-09 18:28 ` Kaushal Modi
2017-03-09 19:15 ` Kaushal Modi
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFyQvY1m0vmpqpM8QLLnz0fDqyE=FjLq6aaSXR3YC-BZwbJajw@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=25941@debbugs.gnu.org \
--cc=ohwoeowho@gmail.com \
--cc=vibhavp@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.