From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eric Abrahamsen Newsgroups: gmane.emacs.help Subject: Re: Speeding up Emacs load time Date: Sat, 29 Jun 2013 13:04:05 +0800 Message-ID: <87txkhmrsq.fsf@ericabrahamsen.net> References: <87y59urnfn.fsf@VLAN-3434.student.uu.se> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1372482256 3430 80.91.229.3 (29 Jun 2013 05:04:16 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 29 Jun 2013 05:04:16 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Jun 29 07:04:16 2013 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UsnKY-0003nR-6X for geh-help-gnu-emacs@m.gmane.org; Sat, 29 Jun 2013 07:04:14 +0200 Original-Received: from localhost ([::1]:40379 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UsnKX-0005fx-Ps for geh-help-gnu-emacs@m.gmane.org; Sat, 29 Jun 2013 01:04:13 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37913) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UsnKM-0005fr-Ne for help-gnu-emacs@gnu.org; Sat, 29 Jun 2013 01:04:05 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UsnKK-0000PX-Az for help-gnu-emacs@gnu.org; Sat, 29 Jun 2013 01:04:02 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:39571) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UsnKK-0000PF-4z for help-gnu-emacs@gnu.org; Sat, 29 Jun 2013 01:04:00 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UsnKG-0003Uh-Iv for help-gnu-emacs@gnu.org; Sat, 29 Jun 2013 07:03:56 +0200 Original-Received: from 114.252.251.64 ([114.252.251.64]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 29 Jun 2013 07:03:56 +0200 Original-Received: from eric by 114.252.251.64 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 29 Jun 2013 07:03:56 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 29 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 114.252.251.64 User-Agent: Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:262ayk7mlPrnL9z8Lvcv9Sc7CUI= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:91842 Archived-At: Emanuel Berg writes: > Bob Proulx writes: > >> I looked at your .emacs file. It is rather extensive. Time >> consuming parts are usually anytime you (require 'foo) or (load >> "foo"). Do you really need all of those executed each and every >> time you start emacs? Probably not. > > OK, this is one way to think. There is another way to think. The > other way to think is: one second at x does not equal one second > at y. When you start Emacs, you are not in a rush. You make sure > you work place is organized. You fetch water, books. You relax you > shoulders. Whatever. Here, you do have time to wait. However, when > you are attentively at work, and you have one million thoughts in > your head at once, you just need to bring up some Emacs > functionality with a minimal delay. Here, time is much more > important. It is like the super-focused people playing ice hockey > or sparring for a boxing fight - for them, 10 seconds is like an > eternity. When you, as a programmer, reaches that highest peak of > productivity/focus, you don't want to load any modules, possible > creating havoc, that (at worst) could take you from what you were > doing. Super-focus, once lost, cannot easily be recovered. So, my > piece of advice: be safe, first load everything safe and sound, > then do your worst to the actual problem you try so solve, with > minimal interference. +1 -- I used to do a bunch of autoload/eval-after-load stuff, but later came to the same conclusion.