From mboxrd@z Thu Jan 1 00:00:00 1970 From: York Zhao Subject: Re: still seeing semi-regular lockups Date: Mon, 7 Jul 2014 11:10:22 -0400 Message-ID: References: <87siocrbyb.fsf@ericabrahamsen.net> <87k39hdf2o.fsf@tanger.home> <87ppj86elt.fsf@ericabrahamsen.net> <874n0kde2y.fsf@tanger.home> <87bnus4s5n.fsf@ericabrahamsen.net> <87egye7kx3.fsf@nicolasgoaziou.fr> <87a992mleu.fsf@ericabrahamsen.net> <87ha3425s3.fsf@ericabrahamsen.net> <87r428v4hn.fsf@ericabrahamsen.net> <87y4wdwmsy.fsf@nicolasgoaziou.fr> <87wqbw9ol5.fsf@nicolasgoaziou.fr> <87a98n3q0q.fsf@nicolasgoaziou.fr> <87d2dhybpr.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7b418441c5e28b04fd9bdffe Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47923) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X4AYj-00038S-6i for emacs-orgmode@gnu.org; Mon, 07 Jul 2014 11:10:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1X4AYh-0006hO-VU for emacs-orgmode@gnu.org; Mon, 07 Jul 2014 11:10:25 -0400 Received: from mail-vc0-x233.google.com ([2607:f8b0:400c:c03::233]:47451) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X4AYh-0006hK-Pe for emacs-orgmode@gnu.org; Mon, 07 Jul 2014 11:10:23 -0400 Received: by mail-vc0-f179.google.com with SMTP id id10so4132805vcb.10 for ; Mon, 07 Jul 2014 08:10:23 -0700 (PDT) In-Reply-To: <87d2dhybpr.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: York Zhao , emacs-orgmode --047d7b418441c5e28b04fd9bdffe Content-Type: text/plain; charset=UTF-8 >> + zfill-org-paragraph-boundary 7,240 0% > What is that, if I may ask? That's in my `zfill-mode' based on `refill-mode', and the function is part of the machinery to handle the automatic refilling of org paragraph. > + ac-handle-post-command 2985 56% > + timer-event-handler 1786 33% > + redisplay_internal (C function) 131 2% [...] > So I suspected the `auto-complete'. I tried M-x auto-complete to turn it off > which worked, the typing was fast again. M-x auto-complete to turn it back on > and typing became extremely slow again. > Indeed. auto-complete developers may be interested in your report. This is not > an Org bug, though. Yes, it is highly possible to be a bug in `auto-complete' and I will report it to the `auto-complete' developers as soon as I get a bit more time. And I totally understand if you decide not to spend time on this until I can further prove that this is still an org-mode problem. However, I think it might be too early to draw the conclusion at this point that this has nothing to do with org-mode. This is because `auto-complete' started to manifest the problem after doing a bunch of org-mode specific operations, more specifically, after running `org-drlll' on 8 `org-mode' buffers, which suggested the possibility of the leftover side effect introduced by org-mode operations. And the problem could be in `org-drlll', but also very possibly be in org-mode core because `org-drlll' uses the APIs provided by `org-mode' core. Anyways, the other one I reported yesterday seemed to be related to org-element cache stuff and I will follow your suggestion to try to reproduce it. But I may not have much time this week anymore. Will definitely try it this weekend for sure. Regards, York --047d7b418441c5e28b04fd9bdffe Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
>> + zfill-org-paragraph-boundary=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 7,240=C2=A0=C2=A0 0%
> What is that, i= f I may ask?

That's in my `zfill-mode' based on `refill-mode= ', and the function is part of
the machinery to handle the automatic refilling of org paragraph.

&g= t; + ac-handle-post-command=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 2985=C2=A0 56%
> + timer-e= vent-handler=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 1786=C2=A0 33%
> + redisplay_internal (C function)=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 131=C2=A0=C2=A0 2%
[...]

> So I suspected the `auto-com= plete'. I tried M-x auto-complete to turn it off
> which worked, = the typing was fast again. M-x auto-complete to turn it back on
> and typing became extremely slow again.

> Indeed. auto-compl= ete developers may be interested in your report. This is not
> an Org= bug, though.

Yes, it is highly possible to be a bug in `auto-comple= te' and I will report it
to the `auto-complete' developers as soon as I get a bit more time. And= I
totally understand if you decide not to spend time on this until I ca= n further
prove that this is still an org-mode problem. However, I think= it might be too
early to draw the conclusion at this point that this has nothing to do with=
org-mode. This is because `auto-complete' started to manifest the p= roblem after
doing a bunch of org-mode specific operations, more specifi= cally, after running
`org-drlll' on 8 `org-mode' buffers, which suggested the possibilit= y of the
leftover side effect introduced by org-mode operations. And the= problem could be
in `org-drlll', but also very possibly be in org-m= ode core because `org-drlll'
uses the APIs provided by `org-mode' core.

Anyways, the other on= e I reported yesterday seemed to be related to org-element
cache stuff a= nd I will follow your suggestion to try to reproduce it. But I may
not h= ave much time this week anymore. Will definitely try it this weekend for sure.

Regards,

York

--047d7b418441c5e28b04fd9bdffe--