From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: npostavs@gmail.com, 18764@debbugs.gnu.org
Subject: bug#18764: 24.4; electric-indent in *scratch* signals an error
Date: Mon, 18 Jun 2018 18:15:15 +0300 [thread overview]
Message-ID: <83602gt9bw.fsf@gnu.org> (raw)
In-Reply-To: <772680b2-622b-6b67-3eb6-9baa02bd3621@yandex.ru> (message from Dmitry Gutov on Mon, 18 Jun 2018 12:33:34 +0300)
> Cc: 18764@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Mon, 18 Jun 2018 12:33:34 +0300
>
> On 6/17/18 6:48 AM, Eli Zaretskii wrote:
>
> > I submit that any errors in code that tries to indent should be
> > suppressed, as they are not relevant to what the user wanted. If
> > those errors are important in other contexts, they will pop up there,
> > and can then decide what to do with them.
>
> That's going to make user complaints like "why it doesn't indent" or "it
> doesn't indent right" harder to debug and address.
IMO, this is a lesser evil. And if it turns out to be a real problem,
we could always add a variable to control whether such errors are
silently ignored.
next prev parent reply other threads:[~2018-06-18 15:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-18 14:59 bug#18764: 24.4; electric-indent in *scratch* signals an error Eli Zaretskii
2018-06-15 2:34 ` Noam Postavsky
2018-06-16 11:30 ` Eli Zaretskii
2018-06-16 13:48 ` Noam Postavsky
2018-06-16 15:03 ` Eli Zaretskii
2018-06-16 23:13 ` Noam Postavsky
2018-06-17 3:48 ` Eli Zaretskii
2018-06-18 9:33 ` Dmitry Gutov
2018-06-18 15:15 ` Eli Zaretskii [this message]
2018-06-21 0:19 ` Noam Postavsky
2018-06-21 14:39 ` Eli Zaretskii
2018-06-24 1:40 ` Noam Postavsky
2018-06-24 14:52 ` Eli Zaretskii
2018-06-25 23:20 ` Noam Postavsky
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=83602gt9bw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18764@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=npostavs@gmail.com \
/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.