From: raman <raman@google.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 18139@debbugs.gnu.org
Subject: bug#18139: 24.4.50; called-interactively-p and skip advice:
Date: Tue, 29 Jul 2014 17:40:37 -0700 [thread overview]
Message-ID: <87bns7n0fu.fsf@gmail.com> (raw)
In-Reply-To: <pz4mxzyag7.fsf@fencepost.gnu.org> (Glenn Morris's message of "Tue, 29 Jul 2014 20:08:56 -0400")
A minimal example would be nice, but the minimal example doesn't
break. The insanely complex code that gets invoked when you call
electric newline and indent from ruby mode appears to be the only
pattern to date that triggers this.
next prev parent reply other threads:[~2014-07-30 0:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 1:58 bug#18139: 24.4.50; called-interactively-p and skip advice: raman
2014-07-30 0:08 ` Glenn Morris
2014-07-30 0:40 ` raman [this message]
2014-07-30 3:59 ` Eli Zaretskii
2014-07-30 13:56 ` raman
2017-03-25 15:55 ` npostavs
2021-08-10 16:23 ` Lars Ingebrigtsen
2014-08-01 16:12 ` raman
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=87bns7n0fu.fsf@gmail.com \
--to=raman@google.com \
--cc=18139@debbugs.gnu.org \
--cc=rgm@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 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).