all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: dgutov@yandex.ru, 18764@debbugs.gnu.org
Subject: bug#18764: 24.4; electric-indent in *scratch* signals an error
Date: Thu, 21 Jun 2018 17:39:06 +0300	[thread overview]
Message-ID: <83wousqk51.fsf@gnu.org> (raw)
In-Reply-To: <87zhzpq9dn.fsf@gmail.com> (message from Noam Postavsky on Wed, 20 Jun 2018 20:19:16 -0400)

> From: Noam Postavsky <npostavs@gmail.com>
> Cc: Dmitry Gutov <dgutov@yandex.ru>,  18764@debbugs.gnu.org
> Date: Wed, 20 Jun 2018 20:19:16 -0400
> 
> >> 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.
> 
> We can be a little more discriminating than my initial blanket
> `ignore-errors', see commit message in the attached patch:

Fine with me, but I'd prefer a comment in the code explaining why we
catch errors here.

Thanks.





  reply	other threads:[~2018-06-21 14:39 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
2018-06-21  0:19                 ` Noam Postavsky
2018-06-21 14:39                   ` Eli Zaretskii [this message]
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=83wousqk51.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.