all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: "Jostein Kjønigsen" <jostein@secure.kjonigsen.net>
Cc: jostein@kjonigsen.net, emacs-devel@gnu.org
Subject: Re: nxml-mode: Derive from prog-mode instead of text-mode
Date: Tue, 06 Jun 2017 10:45:20 -0400	[thread overview]
Message-ID: <jwvlgp5goy7.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <1496406872.1818733.996544288.4194749A@webmail.messagingengine.com> ("Jostein Kjønigsen"'s message of "Fri, 02 Jun 2017 14:34:32 +0200")

> One type of conflict is mode-state: For text-based modes I want to
> flyspell enabled, but for programming-related modes I want it disabled.
>
> Another type of conflict is keybindings: I like to plug in languagetool-
> related functionality on keys consistent with what I typically have in
> programming-modes. That means that targets of these bindings for these
> keys differ in text-mode and prog-mode.

It seems to me that those conflicts aren't a real problem for the
combined text+prog mode: the same problems exist with the current setup
when you want prog-mode and you get text-mode (or vice versa), so using
a combined text+prog mode wouldn't make things really worse.

And I don't think there's a really better solution to this problem: you
currently want A for text-modes and B for prog-modes, so for modes which
sit halfway you're going to have to tweak your ~/.emacs to tell Emacs
which of A or B (or yet something else, maybe) you want, no matter how
we make these halfway modes behave.


        Stefan



  reply	other threads:[~2017-06-06 14:45 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10 10:35 nxml-mode: Derive from prog-mode instead of text-mode Jostein Kjønigsen
2017-05-10 10:40 ` Yuri Khan
2017-05-10 10:52   ` Jostein Kjønigsen
2017-05-10 11:42     ` Yuri Khan
2017-05-10 12:00 ` Stefan Monnier
2017-05-10 16:38 ` Eli Zaretskii
2017-05-10 17:59   ` Jostein Kjønigsen
2017-05-10 18:59     ` Eli Zaretskii
2017-05-10 19:28       ` Eli Zaretskii
2017-05-11  7:29       ` Jostein Kjønigsen
2017-05-11 15:15         ` raman
2017-05-11 15:29           ` Eli Zaretskii
2017-05-11 15:26         ` Eli Zaretskii
2017-05-14 19:28         ` Philipp Stephani
2017-05-14 19:58           ` Dmitry Gutov
2017-05-15  3:05           ` Tom Tromey
2017-05-16 10:34             ` Jostein Kjønigsen
2017-05-16 11:17               ` Yuri Khan
2017-05-16 12:12                 ` Stefan Monnier
2017-05-16 14:04                   ` Drew Adams
2017-05-16 14:08                     ` Eric Abrahamsen
2017-05-16 18:19                       ` Drew Adams
2017-05-16 21:48                         ` Stefan Monnier
2017-05-17  5:13                         ` Yuri Khan
2017-05-17 12:53                           ` Stefan Monnier
2017-05-17 16:02                           ` Drew Adams
2017-05-17 16:20                             ` Yuri Khan
2017-05-17 16:37                             ` Stefan Monnier
2017-05-17 17:28                               ` Drew Adams
2017-05-17 18:42                                 ` Stefan Monnier
2017-05-17 18:52                                   ` Johan Bockgård
2017-05-16 14:11                     ` Stefan Monnier
2017-05-16 12:11               ` Stefan Monnier
2017-05-16 18:54               ` Eli Zaretskii
2017-05-16 19:02                 ` Jostein Kjønigsen
2017-05-24  8:50                   ` Jostein Kjønigsen
2017-05-30  8:05                     ` Jostein Kjønigsen
2017-05-31 11:52                       ` Stefan Monnier
2017-06-02 12:34                       ` Jostein Kjønigsen
2017-06-06 14:45                         ` Stefan Monnier [this message]
2017-05-16 21:50                 ` Stefan Monnier
2017-05-11  1:32 ` Rolf Ade

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

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

  git send-email \
    --in-reply-to=jwvlgp5goy7.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=jostein@kjonigsen.net \
    --cc=jostein@secure.kjonigsen.net \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.