From: Guido Van Hoecke <guivho@gmail.com>
To: Fabrice Niessen <fni-news@pirilampo.org>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: porting crufty old init.el to package management
Date: Mon, 24 Mar 2014 21:01:32 +0100 [thread overview]
Message-ID: <CAEySM9GoBkSER5+0yS9-aQKeDGqSQWBwADRGdwDuS5DBj93q=w@mail.gmail.com> (raw)
In-Reply-To: <86ob0vy9aj.fsf@somewhere.org>
Hi Fabrice,
Oops, I write 'one single down error' but meant 'one single down key',
i.e. just hit the arrow key to descend to the next line. I don't get
errors, it is just not workable at that speed.
Using GNU Emacs 24.3.1 (x86_64-apple-darwin, NS apple-appkit-1187.37)
of 2013-05-18 and Org-mode version 8.2.5h (release_8.2.5h-830-gb3a10b
@ /Users/guivho/.emacs.d/org-mode/lisp/)
I just do not understand why it is that slow...
Guido.
On 24 March 2014 15:13, Fabrice Niessen <fni-news@pirilampo.org> wrote:
> Hi Guido,
>
>> Fabrice Niessen <fni-news@pirilampo.org> writes:
>>>
>>> My example? Follow http://www.pirilampo.org/emacs/dot-emacs.html [1].
>>
>> My emacs needs eleven seconds to process one single down error while
>> still in the opening comments area of emacs-leuven.txt.
>>
>> This is on an iMac 27-Inch, late 2009, with
>> - Processor: 2,66 GHz Intel Core i5
>> - Memory: 8 GB 1067 MHz DDR3
>>
>> Not the latest nor the fastest, but still, not a simple toy neither.
>>
>> What behemoth are you using to edit emacs-leuven.txt?
>
> I do have a 1y old laptop (i7 @ 2.4 GHz, 4 GB RAM).
>
> But, before, I had a 5y old laptop, and did not experience any trouble,
> except that everything was _a bit_ slower.
>
> Do you get a backtrace of the error? With which Emacs (I'm using
> 24.3.50.1).
>
> Please note that I associated every .txt file with Org mode:
>
> (add-to-list 'auto-mode-alist '("\\.txt\\'" . org-mode))
>
> Best regards,
> Fabrice
>
> --
> Fabrice Niessen
> Leuven, Belgium
> http://www.pirilampo.org/
next prev parent reply other threads:[~2014-03-24 20:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.17994.1395617870.10748.help-gnu-emacs@gnu.org>
2014-03-24 10:10 ` porting crufty old init.el to package management Fabrice Niessen
2014-03-24 12:41 ` Guido Van Hoecke
[not found] ` <mailman.18031.1395664909.10748.help-gnu-emacs@gnu.org>
2014-03-24 14:13 ` Fabrice Niessen
2014-03-24 20:01 ` Guido Van Hoecke [this message]
[not found] ` <mailman.18082.1395691327.10748.help-gnu-emacs@gnu.org>
2014-03-24 20:05 ` Fabrice Niessen
2014-03-24 20:39 ` Guido Van Hoecke
[not found] ` <mailman.18086.1395693586.10748.help-gnu-emacs@gnu.org>
2014-03-24 22:38 ` Fabrice Niessen
2014-03-25 2:01 ` Stefan
2014-03-25 10:27 ` Guido Van Hoecke
2014-04-18 6:57 ` Brady Trainor
2014-03-26 3:42 ` Rusi
2014-03-26 11:22 ` Neal Becker
2014-03-26 17:55 ` jpkotta
2014-04-18 6:47 ` Brady Trainor
2014-03-24 22:30 Barry OReilly
2014-03-25 18:10 ` Zhen Sun
-- strict thread matches above, loose matches on Subject: below --
2014-03-23 23:37 Tom Roche
2014-03-24 3:01 ` Marcin Borkowski
2014-03-24 8:25 ` Thorsten Jolitz
2014-03-24 12:42 ` Alan Schmitt
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='CAEySM9GoBkSER5+0yS9-aQKeDGqSQWBwADRGdwDuS5DBj93q=w@mail.gmail.com' \
--to=guivho@gmail.com \
--cc=fni-news@pirilampo.org \
--cc=help-gnu-emacs@gnu.org \
/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.
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).