[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Errors in interactive commands

From: Andreas Röhler
Subject: Re: Errors in interactive commands
Date: Tue, 02 Aug 2011 21:04:41 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; de; rv: Gecko/20110616 SUSE/3.1.11 Thunderbird/3.1.11

Am 02.08.2011 19:46, schrieb Antoine Levitt:
What's the policy concerning errors in interactive commands when they
are called from an invalid context? Right now emacs is a bit
inconsistent: C-f at the end of a buffer displays a message, while C-M-f


thats a bug IMHO, like the error with point at closing string:


forward-sexp: Scan error: "Unbalanced parentheses", 6, 8

inside an empty parenthesis pair raises an error. We should decide on a
standard and apply it to every such command (I'm willing to do it.)

I'm personally in favour of displaying a message, because it makes
editing with toggle-debug-on-error less painful. What do others think?

please permit raising the return-value question again at the occasion:

It's very convenient IMHO, when using a function which move, being able to check for example the returned position like

(eq 123 (ar-forward-word-atpt))

;; https://launchpad.net/s-x-emacs-werkstatt/

which would return at the end buffer nil, not an error, so a while will stop smoothly.

Messaging should be the respective, ie functions interactively called should message it's return values beside returning.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]