unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: npostavs@users.sourceforge.net
To: raman <raman@google.com>
Cc: 18139@debbugs.gnu.org
Subject: bug#18139: 24.4.50; called-interactively-p and skip advice:
Date: Sat, 25 Mar 2017 11:55:54 -0400	[thread overview]
Message-ID: <8737e11hbp.fsf@users.sourceforge.net> (raw)
In-Reply-To: <p91silj2bmq.fsf@raman-glaptop.roam.corp.google.com> (raman@google.com's message of "Wed, 30 Jul 2014 06:56:45 -0700")

tags 18139 unreproducible
quit

raman <raman@google.com> writes:

> This should hopefully produce the  backtrace --  
>
> I'll give two recipes below  -- the first is impossible  for me to try 
>
> 1. emacs -q
> 2. load-library ruby-mode
> 3. evaluate this form:
>
> (defadvice backward-sexp (around test pre act comp)
> (when (called-interactively-p 'interactive)
>       (message "advice!"))
> ad-do-it)
> 3. Open a ruby file test.rb
> 4. type 
> puts "foo"
> 5. Invoke electric-newline-and-indent -- to trigger the bug.

I assume this should be `electric-newline-and-maybe-indent' (C-j).

Nothing happens when I do this (except that a newline is inserted).

> Recipe 2:
>
> Do the same as above with emacspeak loaded -- and without bothering with
> the  additional piece of advice.

Nothing happens when I do this (except that a newline is inserted).
Probably because now emacspeak has a workaround by setting a
`ems-called-interactively-p' flag.  Do you know which version of
emacspeak triggers the bug?





  reply	other threads:[~2017-03-25 15:55 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
2014-07-30  3:59     ` Eli Zaretskii
2014-07-30 13:56       ` raman
2017-03-25 15:55         ` npostavs [this message]
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=8737e11hbp.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=18139@debbugs.gnu.org \
    --cc=raman@google.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 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).