From: Drew Adams <drew.adams@oracle.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>, emacs-devel@gnu.org
Subject: RE: nxml-mode: Derive from prog-mode instead of text-mode
Date: Tue, 16 May 2017 11:19:18 -0700 (PDT) [thread overview]
Message-ID: <93458087-0860-4fcd-9628-dfcf2b231a69@default> (raw)
In-Reply-To: <877f1gx5b3.fsf@ericabrahamsen.net>
> >> > This probably could be unified, too. The big difference here is modes
> >> > that are neither text nor programming — I call them application modes
> >> > — such as dired, calendar, or compilation — because they don’t need
> >>
> >> These should supposedly derive from special-mode.
> >
> > Absolutely not, for Dired. It should not derive from
> > special-mode, tabulated-list-mode, or anything else.
>
> I'm curious why not special-mode. My observation of special-mode is
> that it handles: 1) quit, 2) refresh, and 3) unbind everything else.
Quit (`q') and refresh (`g') - that's all. Oh, and `h' too - but
not `?'.
Like `?', all of the `special-mode' keys besides `q', `g', and `h'
are inappropriate - Dired uses them for other things.
Sure, Dired could override those other bindings, but it makes no
sense to derive from special mode just to get the mundane bindings
for `q', `g', and `h' - providing just `quit-window', `revert-buffer',
and `describe-mode' hardly makes for a "special" mode.
And Dired has its own hooks. I see no reason for Dired to
respect/use `special-mode-hook'.
next prev parent reply other threads:[~2017-05-16 18:19 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 [this message]
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
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=93458087-0860-4fcd-9628-dfcf2b231a69@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.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.