unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "T.V. Raman" <tv.raman.tv@gmail.com>
To: emacs-devel@gnu.org
Cc: tv.raman.tv@gmail.com
Subject: Info: Console Vs GUI difference?
Date: Wed, 30 Oct 2013 02:27:49 -0700	[thread overview]
Message-ID: <CADkJX2h9KvLyZPy5tBxip+8d02d23+mK-tPcc+KS43PE1Entxw@mail.gmail.com> (raw)

As noted on previous threads -- Emacspeak relies heavily on
advice.

I've observed something strange over the last few years that I've
been too lazy to fix, but started digging  into recently - it's
an interesting problem and may point to a curious underlying bug
-- here goes.

Basically, Info running under X  appears to be making  calls to
signal  after *every user command* -- the signal is also clearly
caught and handled at a fairly low-level because you ordinarily
never see it.

Here is a simple way to cause it to happen -- though it might not
be as easy to observe without Emacspeak active.

At an emacs frame running at the Linux console, hit C-h i to open
info (after ensuring that any previous info buffers are killed)
--  then hit either 'p' or 'u' or 'n' to trigger a user-error --
Emacs reports that  there is no where to go -- and all is well.
Kill this buffer.

Now, switch to an emacs frame in a graphical environment under X,
and repeat the experiment.

Once Emacs has triggered the user error in Info as before, what
I'm observing that when in the info buffer (and only in the info
buffer) something in Emacs appears to be calling signal under the
covers -- and the  signal is trapped and suppressed
**after**after every user action.

Looking through info.el hasn't shed any light ---
-- 

--



             reply	other threads:[~2013-10-30  9:27 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-30  9:27 T.V. Raman [this message]
2013-10-30 12:35 ` Info: Console Vs GUI difference? Stefan Monnier
2013-10-30 21:46   ` T.V. Raman
2013-10-30 23:11     ` Stefan Monnier
2013-10-31 16:21       ` T.V. Raman
2013-10-31 18:02         ` Stefan Monnier
2013-10-31 22:14           ` T.V. Raman
2013-11-01  1:32             ` Stefan Monnier
2013-11-01  2:10               ` T.V. Raman
2013-11-01 12:23                 ` Stefan Monnier
2013-11-01 16:55                   ` T.V. Raman
2013-11-01 18:34                     ` Eli Zaretskii
2013-11-01 20:24                       ` T.V. Raman
2013-11-01 20:36                         ` Eli Zaretskii
2013-11-02  0:17                           ` T.V. Raman
2013-11-02  2:04                             ` Stefan Monnier
2013-11-03 15:51                               ` T.V. Raman
2013-11-03 19:02                                 ` Jarek Czekalski
2013-11-03 19:05                                   ` T.V. Raman
2013-11-03 21:19                                     ` Stefan Monnier
2013-11-04  3:10                                     ` Dmitri Paduchikh
2013-11-04 16:38                                       ` T.V. Raman
2013-11-02  7:04                             ` Eli Zaretskii
2013-11-02  1:39                           ` T.V. Raman
2013-11-02  8:06                             ` Jarek Czekalski
2013-11-02 15:35           ` T.V. Raman
2013-11-02 15:56             ` Jarek Czekalski
2013-11-02 16:35             ` Dmitri Paduchikh
2013-11-02 20:46               ` T.V. Raman
2013-10-30 13:46 ` Jarek Czekalski
2013-10-30 21:45   ` T.V. Raman
2013-10-31 20:23   ` Richard Stallman
2013-11-01  7:37     ` Eli Zaretskii
2013-11-01 17:21       ` T.V. 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=CADkJX2h9KvLyZPy5tBxip+8d02d23+mK-tPcc+KS43PE1Entxw@mail.gmail.com \
    --to=tv.raman.tv@gmail.com \
    --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 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).