all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: emacs-devel@gnu.org
Subject: electric-indent-post-self-insert-function: a partial code review.
Date: Sun, 17 Nov 2013 16:27:38 +0000	[thread overview]
Message-ID: <20131117162738.GA19455@acm.acm> (raw)

Hi, Emacs.

The doc string of `electric-indent-inhibit' says:

    "If non-nil, reindentation is not appropriate for this buffer."

.  This is vague and wishy-washy.  What, exactly, does "not appropriate"
mean?  When non-nil, does reindentation get done, or doesn't it?  Better
would be:

    "If non-nil, electric reindentation is not done in this buffer."

, if this is in fact what is intended.

#########################################################################

The doc string of `electric-indent-functions-without-reindent' says:

    "List of indent functions that can't reindent."

.  Even though the rest of the doc string explains what is meant, this
top line is nonsensical - all the functions listed _can_ reindent.
Better, I think, would be:

    "List of indent functions which won't be used for reindentation."

, even if not all that much better.  But what is meant by
"REindentation", as opposed to "indentation"?

Also, in `electric-indent-post-self-insert-function', there are two
calls to `indent-according-to-mode'.  `e-i-f-without-reindent' is only
checked for one of these calls.  Is this a bug?

########################################################################

In `electric--after-char-pos', there is the strange looking form:

    (eq (char-before) last-command-event) ;; Sanity check.

.  What is this supposed to check?  After inserting a newline,
(char-before) is 10.  `last-command-event' is (on my Linux tty) either
10 or 13 (after typing C-j or <ret>).  Distingushing them here doesn't
seem to make sense.  What is this form intended to distinguish?

#########################################################################

Assuming the above meaning for `electric-indent-inhibit', then there is
the following problem: even with `e-i-inhibit' set to t, electric
indentation gets done on the new line after insertion of a \n.

To see this, note that `pos' is bound to (electric--after-char-pos),
that is, the position after the last non-ws character inserted into the
buffer.  The last clause inside the outermost `when' is:

      (unless (and electric-indent-inhibit
                   (> pos (line-beginning-position)))
        (indent-according-to-mode)))

.  This will invoke `indent-according-to-mode' when (<= pos
(line-beginning-position)), i.e. when a \n has just been inserted,
regardless of `electric-indent-inhibit'.  This is surely a bug.

#########################################################################

In general, `electric-mode-post-self-insert-function' seems horrifically
and needlessly over-complicated, even though it is only 50 lines long.
The various checks performed before invoking `indent-according-to-mode'
are done at many different places at several different levels of nesting
in the code.  For instance, why is `electric-indent-inhibit' checked
twice at a lower level, rather than just once at the top level?

Why can the various checks not simply be successive arms of an `and'
form?

The reindentation of the original line sometimes happens in the first
call of `indent-according-to-mode', sometimes in the second call.
Perhaps it would be clearer if the original line was always reindented
in the first call, and the new line (if any) in the second call.

-- 
Alan Mackenzie (Nuremberg, Germany).



             reply	other threads:[~2013-11-17 16:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-17 16:27 Alan Mackenzie [this message]
2013-11-17 21:11 ` electric-indent-post-self-insert-function: a partial code review Stefan Monnier

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=20131117162738.GA19455@acm.acm \
    --to=acm@muc.de \
    --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 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.