From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/18722 Path: news.gmane.org!.POSTED!not-for-mail From: Tim Cross Newsgroups: gmane.emacs.orgmode,gmane.emacs.gnus.user Subject: Re: (gnus-icalendar-org-setup) not evaluated in .emacs? Date: Wed, 20 Sep 2017 08:11:19 +1000 Message-ID: <87lglabapk.fsf@gmail.com> References: <87a81x3e8n.fsf@hornfels.zedat.fu-berlin.de> <87wp517kut.fsf@t3610> <871sn91iqc.fsf@hornfels.zedat.fu-berlin.de> <877ewvdpmz.fsf@pinto.chemeng.ucl.ac.uk> <87mv5rkodt.fsf@hornfels.zedat.fu-berlin.de> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1505859243 3444 195.159.176.226 (19 Sep 2017 22:14:03 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 19 Sep 2017 22:14:03 +0000 (UTC) User-Agent: mu4e 0.9.18; emacs 25.3.1 Cc: info-gnus-english@gnu.org, emacs-orgmode@gnu.org To: Loris Bennett Original-X-From: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Wed Sep 20 00:13:59 2017 Return-path: Envelope-to: geo-emacs-orgmode@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1duQmE-0000cw-OZ for geo-emacs-orgmode@m.gmane.org; Wed, 20 Sep 2017 00:13:59 +0200 Original-Received: from localhost ([::1]:45682 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1duQmM-00014E-1k for geo-emacs-orgmode@m.gmane.org; Tue, 19 Sep 2017 18:14:06 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54128) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1duQjr-0008Fi-R3 for emacs-orgmode@gnu.org; Tue, 19 Sep 2017 18:11:32 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1duQjq-0001fU-Kg for emacs-orgmode@gnu.org; Tue, 19 Sep 2017 18:11:31 -0400 Original-Received: from mail-pf0-x235.google.com ([2607:f8b0:400e:c00::235]:54724) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1duQjn-0001az-Ri; Tue, 19 Sep 2017 18:11:27 -0400 Original-Received: by mail-pf0-x235.google.com with SMTP id d187so507972pfg.11; Tue, 19 Sep 2017 15:11:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=references:user-agent:from:to:cc:subject:in-reply-to:date :message-id:mime-version; bh=pr5c7BIHji0ontCLfBuRDmt++QmX7s1ElHd1sPCLZNA=; b=lWqcT21Qsr0EN9Us8JOroF9qo//r8wFiGVrsZ0MBbHGKG8UMAQjIuZPkynGAOODZFo wXEAzzRaze2xUl8rwGmv3QTA1lMoIxug4qeMs15NV1/pr8rv/81+LL3MTVBXHN9mNzWZ ORdrPJUbpr/T83KrfNhrR+7jwkHqlE2OfmyZH4tZRgQJ0gMjxkPYruM4414odkz+Bsi7 BAcN1wgEC/42oc84Jr+I4dgorxs4gqcFK00dvGPzX2st3j5MTwo5RtJYv9N8mZk/QnQl lC0SbJFmUm/TTab0Hu3sIbC5FafT6up9ez3jyLsPYat2RJFuOz58QGy4EYZKJ6Er0e3t 1rPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:references:user-agent:from:to:cc:subject :in-reply-to:date:message-id:mime-version; bh=pr5c7BIHji0ontCLfBuRDmt++QmX7s1ElHd1sPCLZNA=; b=dUhgjOFekiHHZj7n5sV1kvs6EQcOmB46VFBrP5zrbb/44gHpIyMXnmeQXrpG6THvKv 8oEafC+sVDRq+by970tK4u3ogcHuyXtZ3VQ65F7llYCxAcz2vIbSg+K5tW9iy6RNJvrm SX0lRFkseUqy+TYVy2iawI+lFihiFa5cK1P7hLbo/voB40W1/ctLp3foUcfY6phXvqXG aKlDW/i3tDNTRo7+v/SWrVpgGU8WiTSbabZJbiEeY+I2EDAzyyeSe8qkqds8ASS8vZPM gXjK9F7YCpbkHKBOJcW98SUKZZsyk3n89YwCkIEnIWH95yvI3bGiheOBnReDhg21nUY6 SNVw== X-Gm-Message-State: AHPjjUh30PK0P5UUQTAiZhhXLciVs83i01uIBMjUL9jJu47uBH2c/Gk1 jlWxXW9VDoQOzIstS1LlJ5LPxUDt X-Google-Smtp-Source: AOwi7QD7KezKKVVeX5s6nBqVdki65xrLXUpR5P1IvreLJp4g5lqJBcd1V9tNou2UlfarU8QSn1A21g== X-Received: by 10.98.223.88 with SMTP id u85mr64469pfg.219.1505859085358; Tue, 19 Sep 2017 15:11:25 -0700 (PDT) Original-Received: from tim-desktop (2001-44b8-31f2-bb00-7042-27fb-e2b0-931a.static.ipv6.internode.on.net. [2001:44b8:31f2:bb00:7042:27fb:e2b0:931a]) by smtp.gmail.com with ESMTPSA id r81sm6477159pfj.106.2017.09.19.15.11.22 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 19 Sep 2017 15:11:24 -0700 (PDT) In-reply-to: <87mv5rkodt.fsf@hornfels.zedat.fu-berlin.de> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:400e:c00::235 X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.21 Precedence: list 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 Original-Sender: "Emacs-orgmode" Xref: news.gmane.org gmane.emacs.orgmode:116143 gmane.emacs.gnus.user:18722 Archived-At: Management of an emacs init file is a challenge for anyone who has been using Emacs for a long time. I did this after being a user for over 20 years and like you, was a little daunted by the task. However, I now realise it was the single best thing I ever did to improve my emacs. I also had let my config grow organically and what I found out when I decided to clean it up was that a lot of what I had in there was unnecessary, was slowing down my Emacs (both startup and runtime) and that many of my long-term emacs 'annoyances' were actually due to incorrect or outdated settings in my init file. A few things I learned which may be of help 1. Put your init in git (or your favourite source control system ) and do your changes incrementally. You will need to revert to previous versions, so be methodical with checking in changes and do it incrementally. 2. Have a look at the use-package macro. This really cleaned up my init file, helped me make it more modular and really improved both the structure and maintenance as well as startup times etc. 3. I now use org to manage my init file. In fact, I have a few init files. I have a bare bones minimal init file which I use when I need to debug a specific feature/package or generate bug reports, I have an experimental one where I play with new things and I have my stable one. Using org, I can just 'tangle' a new init based on one of those files whenever I need it. I started by just putting all my existing setup into a block in an org file and exporting that as elisp. As time permitted, I broke bits off into their own blocks with explanatory comments/text so that I can remember why/what of the block. 4. Finally, there are some really good 'canned' configurations out there. I personally quite like purcell's setup (on github). While I don't use any of these per se, I did 'borrow' some of the ideas. My setup is now healthier and more stable than it ever has been. The effort is definitely worth it. Tim Loris Bennett writes: > Eric S Fraga writes: > >> On Thursday, 14 Sep 2017 at 16:02, Loris Bennett wrote: >>> But should this kind of ordering dependency happen? Or should my >>> Customize block just be at the beginning of my .emacs rather than at the >>> end? >> >> I make sure my customizations are loaded before anything else. I have >> my customizations in a separate file and "(load custom-file)" as one of >> the first things in my Emacs init. Not the first as such as I set the >> load-path to point to the versions of packages I am using that may >> conflict with built-in ones in Emacs. > > For someone like me, who fails to spot the related variables even > within a single file, I think hiving customisation off into a separate > file might set up a few new tripwires for future me. > > Having said that, having let my .emacs grow organically (think "rampant > weeds") for 30 years, maybe I should take the shears to it. I'm just > worried that, if I started today, I might not be productive again until > the New Year :-( > > Cheers, > > Loris -- Tim Cross