unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Mark Oteiza <mvoteiza@udel.edu>
Cc: 22564@debbugs.gnu.org
Subject: bug#22564: Fundamental mode isn't fundamental enough.
Date: 6 Feb 2016 11:21:10 -0000	[thread overview]
Message-ID: <20160206112110.9815.qmail@mail.muc.de> (raw)
In-Reply-To: <mailman.3712.1454686507.843.bug-gnu-emacs@gnu.org>

Hello, Mark.

In article <mailman.3712.1454686507.843.bug-gnu-emacs@gnu.org> you wrote:

> Alan Mackenzie <acm@muc.de> writes:
>>> No, it's a deliberate feature, AFAIU.

>> You mean, there should no longer be a vanilla fundamental mode?  I would
>> argue that no "helpful" electric modes should be enabled in FM.  At the
>> moment, it appears, we are lacking a What-You-Do-Is-What-You-Get mode.

>> I think electric-*-modes should be disabled in FM unless explicitly
>> enabled by the user in an FM buffer.  We've become far too "clever" with
>> all these facilities.

> electric-indent-mode is the only electric-*-mode on by default, and I
> never understood why it was enabled. Up until bracketed paste was
> implemented, this issue of indenting pastes had been an annoyance (only
> later on did I realize to disable this electric mode).

What is "bracketed paste"?  The term appears only in xterm.el, but that
file doesn't say what it is.

I still think it's a bug that a standard OS paste operation doesn't work
out of the box in a non-specialised buffer.

-- 
Alan Mackenzie (Nuremberg, Germany).






  parent reply	other threads:[~2016-02-06 11:21 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-05 12:55 bug#22564: Fundamental mode isn't fundamental enough Alan Mackenzie
2016-02-05 14:46 ` Eli Zaretskii
2016-02-05 15:13   ` Alan Mackenzie
2016-02-05 15:34     ` Mark Oteiza
2016-02-05 15:38       ` Drew Adams
2016-02-05 17:57         ` Marcin Borkowski
2016-02-05 19:59           ` Drew Adams
2016-02-05 19:26     ` Eli Zaretskii
2016-02-05 20:18       ` Marcin Borkowski
2016-02-06 19:48     ` Richard Stallman
2016-02-05 20:23 ` Glenn Morris
2016-02-05 21:43   ` Glenn Morris
2016-02-05 21:53   ` Alan Mackenzie
2016-02-17  2:50     ` John Wiegley
2022-04-27 14:39       ` Lars Ingebrigtsen
2022-05-01  1:53         ` Richard Stallman
2022-05-01  6:16           ` Eli Zaretskii
2022-05-02 23:47             ` Richard Stallman
2022-05-03  7:03               ` Andreas Röhler
2022-05-03 14:28                 ` Drew Adams
2022-05-03 17:00               ` Eli Zaretskii
2022-05-04 22:49                 ` Richard Stallman
2022-05-05  5:43                   ` Eli Zaretskii
2022-05-05 11:02                     ` Andreas Röhler
2022-05-05 16:17                       ` Eli Zaretskii
2022-05-05 18:34                         ` Andreas Röhler
2022-05-06 23:20                     ` Richard Stallman
2022-05-07  6:30                       ` Eli Zaretskii
2022-05-07 23:08                         ` Richard Stallman
     [not found] ` <mailman.3748.1454702408.843.bug-gnu-emacs@gnu.org>
2016-02-06 11:06   ` Alan Mackenzie
2016-02-07 18:33     ` Richard Stallman
     [not found] ` <mailman.3712.1454686507.843.bug-gnu-emacs@gnu.org>
2016-02-06 11:21   ` Alan Mackenzie [this message]
2016-02-06 14:36     ` Mark Oteiza
2016-02-06 16:59 ` Achim Gratz
2016-02-07 19:09   ` Eli Zaretskii
2016-02-07 21:02 ` Achim Gratz
2016-02-07 21:08   ` Eli Zaretskii
2016-02-08 19:39 ` Achim Gratz
2016-02-08 20:05   ` Eli Zaretskii
2016-02-08 20:18 ` Achim Gratz
2016-02-08 20:53   ` Eli Zaretskii
2016-02-08 21:01 ` Achim Gratz
2016-02-09  3:31   ` Eli Zaretskii
     [not found] <<20160205125559.GC7727@acm.fritz.box>
     [not found] ` <<834mdnusem.fsf@gnu.org>
2016-02-05 15:36   ` Drew Adams
     [not found] <<mailman.3748.1454702408.843.bug-gnu-emacs@gnu.org>
     [not found] ` <<20160206110601.6095.qmail@mail.muc.de>
2016-02-06 15:57   ` Drew Adams
     [not found]   ` <<E1aSU9T-0002aS-5O@fencepost.gnu.org>
2016-02-07 19:43     ` Drew Adams

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=20160206112110.9815.qmail@mail.muc.de \
    --to=acm@muc.de \
    --cc=22564@debbugs.gnu.org \
    --cc=mvoteiza@udel.edu \
    /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).