From: Kaushal Modi <kaushal.modi@gmail.com>
To: Gemini Lasswell <geminilasswell@runbox.com>
Cc: 29919@debbugs.gnu.org
Subject: bug#29919: 26.0.90; Incorrect Edebug spec for cl-macrolet
Date: Wed, 25 Jul 2018 18:24:09 -0400 [thread overview]
Message-ID: <CAFyQvY0ABcb-mpb0PXbxzaG5MRpkyKUcyNagZDBaccwJS2e=rQ@mail.gmail.com> (raw)
In-Reply-To: <87k1pkqkz9.fsf@runbox.com>
[-- Attachment #1: Type: text/plain, Size: 938 bytes --]
On Tue, Jul 24, 2018 at 7:21 PM Gemini Lasswell <geminilasswell@runbox.com>
wrote:
>
> Kaushal, I was able to step through org-export-data with this patch in
> place. Let me know if you are able to give it a try.
>
Hello,
Thanks for pinging me to try this out.
I am currently on
Emacs version: GNU Emacs 27.0.50 (build 3, x86_64-pc-linux-gnu, GTK+
Version 2.24.23)
of 2018-07-24, built using commit 0ed21b7b3e71303d7858192246012f4b26438ad8.
.. and looks like that sluggishness on edebug of Org exporter functions due
to info already got resolved with one of the commits on master branch since
I last responded in this thread.
Because even without your patch, the edebug of info var is quite snappy.
I can though confirm that even after applying your patch (I don't
understand exactly what it's doing as I haven't yet learnt about
cl-macrolet), the edebug of Org export functions with info var is still
snappy.
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 1474 bytes --]
next prev parent reply other threads:[~2018-07-25 22:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-31 21:36 bug#29919: 26.0.90; Incorrect Edebug spec for cl-macrolet Gemini Lasswell
2018-07-24 23:20 ` Gemini Lasswell
2018-07-25 22:24 ` Kaushal Modi [this message]
2018-07-27 19:10 ` Gemini Lasswell
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='CAFyQvY0ABcb-mpb0PXbxzaG5MRpkyKUcyNagZDBaccwJS2e=rQ@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=29919@debbugs.gnu.org \
--cc=geminilasswell@runbox.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).