emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: Eric S Fraga <esflists@gmail.com>
Cc: Roland Everaert <reveatwork@gmail.com>, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: electric-pair, autopair, smartparens, etc in org-mode
Date: Thu, 25 Oct 2018 08:24:24 +1100	[thread overview]
Message-ID: <87h8hbkph3.fsf@gmail.com> (raw)
In-Reply-To: <87in1rbp3j.fsf@gmail.com>


Eric S Fraga <esflists@gmail.com> writes:

> On Wednesday, 24 Oct 2018 at 12:38, Roland Everaert wrote:
>> Pleased to see it was helpful. The funny thing is that I use that config
>> for, maybe, 10 years and never think about changing it.
>
> I've been using emacs for well over 30 years now.  You would not believe the crud that has built up in my config files... ;-) :Q
>
> Mind you, with org, I have started rationalizing the config files but it's a time consuming task and the adage of "if it ain't broke, don't fix it" has power...

+1

Likewise, started with Emacs 19 and I still have some code which I added
back then in my init!

I went through the pain of cleaning up my init file some time ago when I
moved to make better use of 'use-package'. Have to say that while things
were not 'broken' before my cleanup, they are certainly working better
now and my init is much smaller.

What I found was that a lot of what was in my init file was simply no
longer required as similar (often superior) functionality has crept into
the main Emacs distribution - all I needed to do was remove my code and
turn the feature on.

The two big benefits from the clean up have been much faster start up
(something which never really bothered me as I run emacs for weeks
without re-starting anyway) and far more predictable behaviour when I
try out or add a new mode (I often found my custom tweaks would not
always work well with new modes etc).

Org is extremely useful in this process. Create an org file and put all
your existing init in there as source blocks so that you can reproduce
your setup using tangle. Then create a new-init.org file and just add
the stuff you must have i.e. email config, essential modes etc. Then you
can switch between old and new setups using tangle to generate new
init.el file. When you have time, start with the new-init version and
start adding/tweaking to get the behaviour you want. Rather than just
copy across your old setup, check to see what is available in core - if
your like me, you will find lots of we use to tweak in code is now part
of core emacs and all you need to do is turn it on. At some point, you
will find you stay in your new init file and no longer need to revert to
the old version. You will likely find lots of stuff never gets
migrated. 

It really is worth the time and effort.

Tim

-- 
Tim Cross

  reply	other threads:[~2018-10-24 21:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-21  0:36 electric-pair, autopair, smartparens, etc in org-mode Matt Price
2018-10-21  7:28 ` Nicolas Goaziou
2018-10-21 16:43   ` Matt Price
2018-10-23  7:58     ` Roland Everaert
2018-10-23 11:48       ` stardiviner
2018-10-23 13:07         ` Eric S Fraga
2018-10-24 13:12           ` Matt Price
2018-10-24 14:15             ` Eric S Fraga
2018-10-24 10:38         ` Roland Everaert
2018-10-24 10:45           ` Eric S Fraga
2018-10-24 21:24             ` Tim Cross [this message]
2018-10-25 15:07               ` Eric S Fraga
2018-10-25 22:57                 ` Samuel Wales
2018-10-25 22:59                   ` Samuel Wales
2018-10-26  9:23                   ` Eric S Fraga
2018-10-26 21:45                   ` Tim Cross

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h8hbkph3.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=esflists@gmail.com \
    --cc=reveatwork@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).