From: Samuel Wales <samologist@gmail.com>
To: Tim Cross <theophilusx@gmail.com>,
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 15:57:41 -0700 [thread overview]
Message-ID: <CAJcAo8u0b2=Z9MgU-cdZK5fX6qC0eB+HwhSbW=_C7dugVwGPfQ@mail.gmail.com> (raw)
In-Reply-To: <xuu6r2gecbf4.fsf@gmail.com>
can either of you give examples of code or settings that you had that
made behavior of new modes unpredictable because emacs started
supporting the behavior you made the code or settings for?
On 10/25/18, Eric S Fraga <esflists@gmail.com> wrote:
> On Thursday, 25 Oct 2018 at 08:24, Tim Cross wrote:
>> Likewise, started with Emacs 19 and I still have some code which I added
>> back then in my init!
>
> [...]
>
>> 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).
>
> The second of these is indeed a benefit of cleaning up initialization
> files. I have been doing so, in any case, just at a slower pace than I
> should. I actually have been doing exactly what you suggest: using org
> and tangling.
> --
> Eric S Fraga via Emacs 27.0.50, Org release_9.1.13-894-gf79545
>
>
--
The Kafka Pandemic: <http://thekafkapandemic.blogspot.com>
The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.
"You’ve really gotta quit this and get moving, because this is murder
by neglect." ---
<http://www.meaction.net/2017/02/03/pwme-people-with-me-are-being-murdered-by-neglect>.
next prev parent reply other threads:[~2018-10-25 22:57 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
2018-10-25 15:07 ` Eric S Fraga
2018-10-25 22:57 ` Samuel Wales [this message]
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='CAJcAo8u0b2=Z9MgU-cdZK5fX6qC0eB+HwhSbW=_C7dugVwGPfQ@mail.gmail.com' \
--to=samologist@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=reveatwork@gmail.com \
--cc=theophilusx@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).