From: Lennart Borgman <lennart.borgman@gmail.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Nathan Weizenbaum <nex342@gmail.com>,
6378@debbugs.gnu.org, 6378-done@debbugs.gnu.org
Subject: bug#6378: all-completions Segfault
Date: Tue, 8 Jun 2010 21:32:11 +0200 [thread overview]
Message-ID: <AANLkTikRm_MFGsYotbVpYRLy4xzTaeG3lx19ckgbxySq@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimx0lBOgyPTF9coOuQPMHK6IARCloUkI0pGv9MA@mail.gmail.com>
On Tue, Jun 8, 2010 at 9:08 PM, Juanma Barranquero <lekktu@gmail.com> wrote:
> On Tue, Jun 8, 2010 at 20:58, Lennart Borgman <lennart.borgman@gmail.com> wrote:
>
>> Isn't there a similar case in Ftry_completion?
>
> Apparently no.
>
> ELISP> (try-completion "" [])
> *** Eval error *** Wrong type argument: vectorp, []
> ELISP> (try-completion "" [[]])
> *** Eval error *** Bad data in guts of obarray
> ELISP> (try-completion "" [0])
> nil
> ELISP> (try-completion "" [a])
> ""
> ELISP>
>
> Juanma
So the thing protecting it is that an obarray can't have length 0? Can
one be sure that does not break someday?
next prev parent reply other threads:[~2010-06-08 19:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 15:46 bug#6378: all-completions Segfault Nathan Weizenbaum
2010-06-08 16:37 ` Lawrence Mitchell
2010-06-08 20:30 ` Stefan Monnier
2010-06-09 5:13 ` Thierry Volpiatto
2010-06-09 6:13 ` Lennart Borgman
2010-06-09 7:23 ` Thierry Volpiatto
2010-06-09 8:51 ` Lennart Borgman
2010-06-09 10:05 ` Thierry Volpiatto
2010-06-09 11:43 ` Andreas Schwab
2010-06-09 12:01 ` Thierry Volpiatto
2010-06-09 12:13 ` Andreas Schwab
2010-06-09 6:18 ` Thierry Volpiatto
2010-06-09 9:09 ` Lawrence Mitchell
2010-06-08 16:41 ` Juanma Barranquero
2010-06-08 16:53 ` Juanma Barranquero
2010-06-08 18:58 ` Lennart Borgman
2010-06-08 19:08 ` Juanma Barranquero
2010-06-08 19:32 ` Lennart Borgman [this message]
2010-06-08 19:57 ` Juanma Barranquero
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=AANLkTikRm_MFGsYotbVpYRLy4xzTaeG3lx19ckgbxySq@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=6378-done@debbugs.gnu.org \
--cc=6378@debbugs.gnu.org \
--cc=lekktu@gmail.com \
--cc=nex342@gmail.com \
/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.