From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "T.V. Raman" Newsgroups: gmane.emacs.devel Subject: Info: Console Vs GUI difference? Date: Sat, 2 Nov 2013 08:35:35 -0700 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Trace: ger.gmane.org 1383406537 1362 80.91.229.3 (2 Nov 2013 15:35:37 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 2 Nov 2013 15:35:37 +0000 (UTC) To: Stefan Monnier , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Nov 02 16:35:41 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VcdEi-0000kv-QA for ged-emacs-devel@m.gmane.org; Sat, 02 Nov 2013 16:35:40 +0100 Original-Received: from localhost ([::1]:42344 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VcdEi-0007sK-EH for ged-emacs-devel@m.gmane.org; Sat, 02 Nov 2013 11:35:40 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50558) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VcdEf-0007sF-8R for emacs-devel@gnu.org; Sat, 02 Nov 2013 11:35:37 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VcdEe-00085K-3z for emacs-devel@gnu.org; Sat, 02 Nov 2013 11:35:37 -0400 Original-Received: from mail-ob0-x22e.google.com ([2607:f8b0:4003:c01::22e]:63056) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VcdEd-00085G-UD for emacs-devel@gnu.org; Sat, 02 Nov 2013 11:35:36 -0400 Original-Received: by mail-ob0-f174.google.com with SMTP id vb8so5602347obc.5 for ; Sat, 02 Nov 2013 08:35:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=cuT616iy2xmXuAlhbXi+5oZjnKb0grgLKBYvXsX/6Ig=; b=C3nZych8/PvXVi9mEIx7+A63DzhZtCx4zUqfgNHhidKoe709OSSHI4zjRz+ujdRkps km0FaBuuQpXj0bJMQUm4H316DS/V58+0Vw23RiqHKXM4qZ+V3W3QKGjh3lLz9DHOYTGi i6TCXumHj3fHq0fOml/DzDaA9R+w/Ut9C7QMDj13hf09HDJLLWhZ57NgVi7FyXv2/4lX hsgzYkfYmrojRq5tPLuAMTg+ARo3/QoQF/MvBQ2LXxijgdDNd+shbCqoTsDaZR3FLCwv skRTn5FYVnfhZYaafIrX2hkTPK+/RMSTMFus1K/l9Z4aiPW3dydbUpDmkMVD/LA/7/nM vS0g== X-Received: by 10.182.66.164 with SMTP id g4mr1619849obt.47.1383406535286; Sat, 02 Nov 2013 08:35:35 -0700 (PDT) Original-Received: by 10.182.33.229 with HTTP; Sat, 2 Nov 2013 08:35:35 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:4003:c01::22e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:164867 Archived-At: Hi Stefan, My last attempt at using command-error-function -- appended below -- only produces a "back to top level" message in all instances. Once I can get this working, I'll make the advice on signal conditional on older emacsuns -- (defun emacspeak-error-handler (data context calling-function) "Emacspeak custom error handling function." (dtk-speak (format "%s %s" (or context "") (or (get (car data) 'error-message) "")))) (declaim (special command-error-function)) (add-function :before command-error-function 'emacspeak-error-handler) -- -- On 10/31/13, Stefan Monnier wrote: >> And speaking of aditional emacs hooks that would help emacspeak: > >> 1. A hook that I can use to catch read-only errors for typing >> commands -- a hook here would be a clean solution because >> independent of context, I mostly want to speak the same thing > >> 2. Less need to advice error/ and hopefully never to advice signal -- >> This one is harder because many emacs packages use signal and >> error to signal conditions that should be communicated to the >> average user. > > It seems from where I stand that both should be covered by > command-error-function. So, maybe you should explain in more detail > which part of command-error-function doesn't suit your need. > > > Stefan >