From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Michael Welle <mwe012008@gmx.net>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: working with tables can be quite painful...
Date: Mon, 19 Sep 2016 15:23:45 +0100 [thread overview]
Message-ID: <87lgyoq87i.fsf@ucl.ac.uk> (raw)
In-Reply-To: <df2f3c4ad6a34890ad82cd1d0d557003@HE1PR01MB1898.eurprd01.prod.exchangelabs.com> (Michael Welle's message of "Mon, 19 Sep 2016 12:58:01 +0000")
On Monday, 19 Sep 2016 at 12:58, Michael Welle wrote:
[...]
> the output of your profiler run doesn't ring a bell, but a few years ago
> I had the problem that after some uptime (my Emacs uptime is typical
> several days, up to a few weeks) Org operations like building the agenda
> became sloooow. Restarting Emacs fixed that, until the problem occurred
> again after some time.
Interesting. The performance I was referring to last week was indeed in
an emacs that had been running for quite some time. I did close down
that emacs instance on Friday for unrelated reasons and the instance
this morning had only been running for minutes. Maybe the problem is
not org alone but relates to emacs as well.
> If I remember correctly I asked the list for advise. But it looked like
> one of these problems only I have ;). Maybe some other lisp package had
> its hands in the game, I don't know. Eventually, after some Emacs, Org
> and other updates the problem was gone.
Well, maybe it's a problem that others do have!
> As I said, I don't think, you suffer from the same problem. But you said
> you don't use the newest software versions, so just in case.
To clarify, when I said I wasn't using the latest version of org, it's
that I hadn't updated from git in a few weeks but I am using a snapshot
of emacs tracking the development version (and now I have org up to date).
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.1.50.1, Org release_8.3.6-1149-g582233
next prev parent reply other threads:[~2016-09-19 15:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 14:53 working with tables can be quite painful Eric S Fraga
2016-09-17 8:48 ` Nicolas Goaziou
2016-09-17 15:22 ` Adam Porter
2016-09-17 15:37 ` Michael Brand
[not found] ` <9ae6591e2754413885a96e19c2455472@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-09-19 8:33 ` Eric S Fraga
2016-09-19 12:58 ` Michael Welle
[not found] ` <df2f3c4ad6a34890ad82cd1d0d557003@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-09-19 14:23 ` Eric S Fraga [this message]
2016-09-19 17:54 ` Michael Welle
2016-09-22 19:52 ` Nicolas Goaziou
[not found] ` <61c781eee3b64613a40a39b95bc54e63@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-09-19 8:36 ` Eric S Fraga
2016-09-20 8:54 ` Jacob Nielsen
[not found] ` <b05decb709ba4f64932ba34835b08056@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-09-20 9:03 ` Eric S Fraga
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=87lgyoq87i.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=mwe012008@gmx.net \
/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.