unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Problem with doc-view-previous-major-mode
Date: Sat, 13 Apr 2013 16:57:47 +0200	[thread overview]
Message-ID: <87r4ieeavo.fsf@rosalinde.fritz.box> (raw)
In-Reply-To: <jwvhajblo1k.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 12 Apr 2013 12:24:34 -0400")

On Fri, 12 Apr 2013 12:24:34 -0400 Stefan Monnier <monnier@iro.umontreal.ca> wrote:

>>>> what happens with -Q.  But I have customized the global value of
>>>> major-mode to text-mode,
>>> Why?
>> Because I found that I often wanted to do quick tests in text-mode by
>> typing `C-x b a'.
>
> I see.
>
>> Your question suggests suggests that this customization is
>> ill-advised;
>
> No.  Customizing default-major-mode has been supported "for ever" and
> your use case makes sense, but the way it works makes for some annoying
> corner cases, such as the one you've bumped into.
>
> So I'd like to use another mechanism, such that you could still
> configure the mode to use for a new buffer created via C-x b, but
> without it affecting things like your doc-view case.

Do you have something already in the works, or are you soliciting ideas?
If the latter, maybe we could add a prefix argument to switch-to-buffer
that sets the major-mode (using completion and defaulting to the value
of a user option) if the buffer switched to is new.

>> And if it is ill-advised, then major-mode shouldn't be customizable,
>> should it?
>
> If I could rewrite history, indeed the default value of major-mode would
> not be customizable.

When an alternative is in place, the customizability could be obsoleted.

Steve Berman



  reply	other threads:[~2013-04-13 14:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-11 20:30 Problem with doc-view-previous-major-mode Stephen Berman
2013-04-12  1:57 ` Stefan Monnier
2013-04-12  8:09   ` Stephen Berman
2013-04-12 16:24     ` Stefan Monnier
2013-04-13 14:57       ` Stephen Berman [this message]
2013-04-14  2:56 ` Stefan Monnier
2013-04-14 12:55   ` Stephen Berman

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=87r4ieeavo.fsf@rosalinde.fritz.box \
    --to=stephen.berman@gmx.net \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).