* Some issues with error conditions
@ 2005-07-11 14:34 Dmitriyi Paduchikh
2005-07-11 16:57 ` Dmitriyi Paduchikh
2005-07-11 21:14 ` Richard M. Stallman
0 siblings, 2 replies; 3+ messages in thread
From: Dmitriyi Paduchikh @ 2005-07-11 14:34 UTC (permalink / raw)
Hello,
Evaluating expression
(let ((process (start-process "false" nil "false")))
(sleep-for 1)
(process-send-string process "Hi there!"))
produces an error of most general kind:
Debugger entered--Lisp error: (error "Process false not running")
process-send-string(#<process false> "Hi there!")
(let ((process ...)) (sleep-for 1) (process-send-string process "Hi there!"))
eval((let ((process ...)) (sleep-for 1) (process-send-string process "Hi there!")))
eval-last-sexp-1(nil)
eval-last-sexp(nil)
call-interactively(eval-last-sexp)
Shouldn't it be something like process-error instead? IMHO signalling
general error in this situation makes catching of errors related with
processes more difficult.
And also end-of-file (end of file during parsing),
invalid-read-syntax, scan-error (not sure about this) probably might
be all in the category parse-error as such condition already exists.
--
Dmitriyi Paduchikh
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Some issues with error conditions
2005-07-11 14:34 Some issues with error conditions Dmitriyi Paduchikh
@ 2005-07-11 16:57 ` Dmitriyi Paduchikh
2005-07-11 21:14 ` Richard M. Stallman
1 sibling, 0 replies; 3+ messages in thread
From: Dmitriyi Paduchikh @ 2005-07-11 16:57 UTC (permalink / raw)
I wrote:
[...]
> And also end-of-file (end of file during parsing),
> invalid-read-syntax, scan-error (not sure about this) probably might
> be all in the category parse-error as such condition already exists.
Sorry, the condition parse-error is defined in calendar/parse-time.el,
so probably it's not appropriate to do.
--
Dmitriyi Paduchikh
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Some issues with error conditions
2005-07-11 14:34 Some issues with error conditions Dmitriyi Paduchikh
2005-07-11 16:57 ` Dmitriyi Paduchikh
@ 2005-07-11 21:14 ` Richard M. Stallman
1 sibling, 0 replies; 3+ messages in thread
From: Richard M. Stallman @ 2005-07-11 21:14 UTC (permalink / raw)
Cc: emacs-devel
Shouldn't it be something like process-error instead? IMHO signalling
general error in this situation makes catching of errors related with
processes more difficult.
It sounds like a good idea. However, this is a new feature, not
in any sense fixing a problem, so we should not change it now.
I will add it to etc/TODO.
And also end-of-file (end of file during parsing),
invalid-read-syntax, scan-error (not sure about this) probably might
be all in the category parse-error as such condition already exists.
I didn't know that `parse-error' was defined.
It turns out to have been defined by a specific package
for its own error conditions.
We could redefine it as a broader category.
Again, we should not do so now. I will add it to etc/TODO.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-07-11 21:14 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-07-11 14:34 Some issues with error conditions Dmitriyi Paduchikh
2005-07-11 16:57 ` Dmitriyi Paduchikh
2005-07-11 21:14 ` Richard M. Stallman
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.