all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: monnier@iro.umontreal.ca, 24205@debbugs.gnu.org
Subject: bug#24205: 25.1.50; Re-display issue (lag) when opening certain files [sml-mode]
Date: Thu, 11 Aug 2016 23:27:52 +0300	[thread overview]
Message-ID: <83twerdp9z.fsf@gnu.org> (raw)
In-Reply-To: <CAFyQvY2RbaqArJu+FTVfwmYiYW_a=L=_jNnmU5mFbCj-xE4RuA@mail.gmail.com> (message from Kaushal Modi on Thu, 11 Aug 2016 19:53:05 +0000)

> From: Kaushal Modi <kaushal.modi@gmail.com>
> Date: Thu, 11 Aug 2016 19:53:05 +0000
> Cc: bug-gnu-emacs@gnu.org, monnier@iro.umontreal.ca
> 
> The file has to contain just this sml comment:
> 
> =====
> (* ''a is a special equality type (it is not the same as the generic 'a type. It *) 
> ===== 
> 
> I cannot figure out what's special about this comment that freaks the re-display.

Most probably the unbalanced parentheses.  Something in sml-mode
causes the display engine to hit on that many times.

I will look into this.

>  Are you saying that just visiting this file exhibits the problem? 
> 
> Yes, in sml-mode.
> 
>  If
>  so, what modes should be turned on in the visiting buffer to see the
>  problem?
> 
> All my MWE is doing is:
> - Install sml-mode from GNU Elpa
> - Create a specific example file that causes this issue
> - Start profiler
> - Visit the file

I must explain something so that my requests don't sound arbitrary.
When I work on a problem, I usually run Emacs many times in different
ways, most of the times under a debugger.  Since the debugger (and
other tools) need to read my init files for working properly as I'm
used to, I cannot easily change my home directory, or mess with my
init files during the debugging session.  In addition, with 10-20 sec
delay I don't need a profiler to notice it.

So it is much more helpful to have a recipe that is as simple as
possible (so invoking it many times won't be painful), avoids
interfering with my init files and system configuration, and includes
only the stuff that is directly relevant to the bug reproduction.

A good recipe along the above lines could easily speed up a bugfix by
hours and even days.  So if you can afford that, please try to follow
these guidelines when you prepare a recipe.

I hope this clarifies the reason for my requests.

Thanks.





  reply	other threads:[~2016-08-11 20:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11 17:03 bug#24205: 25.1.50; Re-display issue (lag) when opening certain files [sml-mode] Kaushal Modi
2016-08-11 17:22 ` Eli Zaretskii
2016-08-11 17:30   ` Kaushal Modi
2016-08-11 17:45     ` Kaushal Modi
2016-08-11 18:19       ` Stefan Monnier
2016-08-11 19:42     ` Eli Zaretskii
2016-08-11 19:53       ` Kaushal Modi
2016-08-11 20:27         ` Eli Zaretskii [this message]
2016-08-11 20:58           ` Andreas Schwab
2016-08-11 21:15           ` Kaushal Modi
2016-08-11 22:21             ` Stefan Monnier
2016-08-14 13:26               ` Stefan Monnier
2016-08-14 23:14                 ` 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=83twerdp9z.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24205@debbugs.gnu.org \
    --cc=kaushal.modi@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    /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.