all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jarek Czekalski <jarekczek@poczta.onet.pl>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 15670@debbugs.gnu.org
Subject: bug#15670: 24.3; dummy user-errors on info nodes without prev/next nodes
Date: Tue, 22 Oct 2013 09:15:55 +0200	[thread overview]
Message-ID: <5266262B.3040308@poczta.onet.pl> (raw)
In-Reply-To: <87zjq17t6l.fsf@web.de>


W dniu 2013-10-22 07:47, Michael Heerdegen pisze:
> I mean, emacsspeak does things like advising `signal' and `error'.
>

I guess this is the point. Emacspeak doesn't respect the rules of error 
handling. Whether it can do its job in a cleaner way - I don't know yet. 
But I'm convinced that there is no bug in Emacs, because the user-error 
is caught and should not see the surface. I also know how to fix 
Emacspeak in the way it was intended to work.

Please close the ticket. Sorry for bothering you.

As an analogy in other languages we can code:
try {
   c = a / b;
}
catch (DivisionByZero) {
   c = -1;
}
That's fine. If someone wants to intercept all the DivisionByZero 
exceptions, which possibly own dedicated error handlers - they do wrong 
thing.

Thanks
Jarek






  reply	other threads:[~2013-10-22  7:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-21 15:32 bug#15670: 24.3; dummy user-errors on info nodes without prev/next nodes Jarek Czekalski
2013-10-21 15:52 ` bug#15670: how advised Jarek Czekalski
2013-10-21 16:43 ` bug#15670: 24.3; dummy user-errors on info nodes without prev/next nodes Drew Adams
2013-10-21 17:16 ` Stefan Monnier
2013-10-22  1:17   ` Michael Heerdegen
2013-10-22  5:47     ` Michael Heerdegen
2013-10-22  7:15       ` Jarek Czekalski [this message]
2013-10-23  7:51         ` Michael Heerdegen
2013-10-21 18:22 ` bug#15670: i'll try to get more info Jarek Czekalski

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=5266262B.3040308@poczta.onet.pl \
    --to=jarekczek@poczta.onet.pl \
    --cc=15670@debbugs.gnu.org \
    --cc=michael_heerdegen@web.de \
    /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.