From: Eric S Fraga <esflists@gmail.com>
To: Samuel Wales <samologist@gmail.com>
Cc: Tim Cross <theophilusx@gmail.com>,
Org Mode <emacs-orgmode@gnu.org>,
Roland Everaert <reveatwork@gmail.com>
Subject: Re: electric-pair, autopair, smartparens, etc in org-mode
Date: Fri, 26 Oct 2018 10:23:51 +0100 [thread overview]
Message-ID: <878t2ljc2g.fsf@gmail.com> (raw)
In-Reply-To: <CAJcAo8u0b2=Z9MgU-cdZK5fX6qC0eB+HwhSbW=_C7dugVwGPfQ@mail.gmail.com> (Samuel Wales's message of "Thu, 25 Oct 2018 15:57:41 -0700")
On Thursday, 25 Oct 2018 at 15:57, Samuel Wales wrote:
> 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?
In my case, mostly incompatible bindings of keys, e.g. the tab key, especially in the context of auto-completion mechanisms and auto-expansion (e.g. yasnippet). It's not so much unpredictable behaviour as wrong behaviour due to settings stepping on the toes of subsequently installed packages.
--
Eric S Fraga via Emacs 27.0.50, Org release_9.1.11-620-ga548e4
next prev parent reply other threads:[~2018-10-26 9:23 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
2018-10-25 22:59 ` Samuel Wales
2018-10-26 9:23 ` Eric S Fraga [this message]
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=878t2ljc2g.fsf@gmail.com \
--to=esflists@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=reveatwork@gmail.com \
--cc=samologist@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).