* Curious error logic in completion--some
@ 2014-02-26 22:27 Daniel Colascione
2014-03-04 3:20 ` Stefan Monnier
0 siblings, 1 reply; 2+ messages in thread
From: Daniel Colascione @ 2014-02-26 22:27 UTC (permalink / raw)
To: Emacs developers
Why does completion--some to raise an error only if one of its passed-in
functions raises an error and all return nil? If we want to treat an
error as "no completions", we should do that consistently or
consistently propagate errors to callers. The way it is now, where the
interpretation of an error from a completion table depends on what other
completion tables are in use, seems odd.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Curious error logic in completion--some
2014-02-26 22:27 Curious error logic in completion--some Daniel Colascione
@ 2014-03-04 3:20 ` Stefan Monnier
0 siblings, 0 replies; 2+ messages in thread
From: Stefan Monnier @ 2014-03-04 3:20 UTC (permalink / raw)
To: Daniel Colascione; +Cc: Emacs developers
> Why does completion--some to raise an error only if one of its passed-in
> functions raises an error and all return nil?
Kind of a historical accident. We could try to remove that after the
trunk re-opens and see how to deal with the consequences.
Stefan
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-03-04 3:20 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-02-26 22:27 Curious error logic in completion--some Daniel Colascione
2014-03-04 3:20 ` Stefan Monnier
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).