unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christoph Scholtes <cschol2112@googlemail.com>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: Fundamental mode vs. special mode
Date: Sun, 23 Oct 2011 08:58:15 -0600	[thread overview]
Message-ID: <86ehy3hi0o.fsf@googlemail.com> (raw)
In-Reply-To: <yyxy5wcxjew.fsf@fencepost.gnu.org> (Chong Yidong's message of "Sun, 23 Oct 2011 03:21:27 -0400")

Chong Yidong <cyd@stupidchicken.com> writes:

> It's not a good idea to add anything to Fundamental mode.  The point of
> it is to be fundamental.

OK.

> Anyway, binding "q" to `quit-window' is no good; I imagine some users
> expect want to be able to edit the buffer.  Same with other cases like
> the *Messages* buffer.

OK. I guess to me a buffer like *Shell Mode Output* is a read-only
buffer, hence `special'. If I want to edit the output of a shell command
I can always create buffer and insert the output into it with M-1
M-!. That's what I would have to do in a shell outside Emacs, no? On the
other hand, I can see how someone might think the current behavior is an
advantage.

As a user, I feel like buffers Emacs creates, which show some kind of
status information (logs, shell output etc.), I should be able to read
and acknowledge (e.g. with `q') like other `special' buffers. It feels
like quite often I have to think about what the correct command is for
this buffer, where I feel it should be more natural from a UI point of
view.

But then again, maybe I just have spent too much time in the non-free
world with its UI paradigms. ;)

Christoph



  parent reply	other threads:[~2011-10-23 14:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-22 20:13 Fundamental mode vs. special mode Christoph Scholtes
2011-10-23  7:21 ` Chong Yidong
2011-10-23  9:19   ` martin rudalics
2011-10-23 13:28     ` Juri Linkov
2011-10-23 18:59       ` martin rudalics
2011-10-24  5:07         ` Juri Linkov
2011-10-24 16:39         ` Richard Stallman
2011-10-23 13:14   ` Johan Bockgård
2011-10-25  2:38     ` Chong Yidong
2011-10-25  3:51       ` Chong Yidong
2011-10-25 12:30         ` Stefan Monnier
2011-10-25 13:53           ` Juanma Barranquero
2011-10-25 15:11             ` Paul Eggert
2011-10-25 20:02               ` Stefan Monnier
2011-10-25 20:30                 ` Alan Mackenzie
2011-10-26  1:11                   ` Chong Yidong
2011-10-26 12:11                     ` Nix
2011-10-26 11:50                   ` Richard Stallman
2011-10-27  2:25                     ` Chong Yidong
2011-10-23 14:58   ` Christoph Scholtes [this message]
2011-10-24  5:11     ` Juri Linkov
2011-10-24 12:46       ` Stefan Monnier
2011-10-24 17:17       ` Alan Mackenzie
2011-10-25  4:30         ` Juri Linkov
2011-10-25 20:49           ` Alan Mackenzie
2011-10-26  1:18             ` Chong Yidong

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.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=86ehy3hi0o.fsf@googlemail.com \
    --to=cschol2112@googlemail.com \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    /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.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).