all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Paul Eggert <eggert@gnu.org>, 16161@debbugs.gnu.org
Subject: bug#16161: 24.3.50; gnutls connections from Gnus no longer work after r115526, bug#16161: 24.3.50; gnutls connections from Gnus no longer work after r115526
Date: Mon, 16 Dec 2013 12:37:28 -0500	[thread overview]
Message-ID: <87zjo0n1d3.fsf@flea.lifelogs.com> (raw)
In-Reply-To: <mvmlhzk4vqr.fsf@hawking.suse.de> (Andreas Schwab's message of "Mon, 16 Dec 2013 17:16:12 +0100, Mon, 16 Dec 2013 18:49:54 +0200")

On Mon, 16 Dec 2013 17:16:12 +0100 Andreas Schwab <schwab@suse.de> wrote: 

AS> Ted Zlatanov <tzz@lifelogs.com> writes:
>> I've changed the `CHECK_LIST_CONS' back to `Flistp'

AS> Flistp never returns zero.

Thanks.

On Mon, 16 Dec 2013 18:49:54 +0200 Eli Zaretskii <eliz@gnu.org> wrote: 

EZ> Why not use CHECK_LIST instead?  It does allow for nil, and is
EZ> slightly faster.

The error message was not helpful at all, there is no `verify_error'
function parameter (it would be nice to be able to set the error message
from these macros).  May I replace it with this?  It's what CHECK_LIST
does, internally, IIUC.

#+begin_src c
  if (!CONSP (x) && !NILP (x))
    error ("gnutls-boot: invalid :verify_error parameter (not a list)");
#+end_src

Thanks
Ted





  parent reply	other threads:[~2013-12-16 17:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-16 12:33 bug#16161: 24.3.50; gnutls connections from Gnus no longer work after r115526 Nix
2013-12-16 12:51 ` Nix
2013-12-16 15:53   ` Ted Zlatanov
2013-12-16 16:16     ` Andreas Schwab
2013-12-16 16:49       ` Eli Zaretskii
2013-12-16 17:37       ` Ted Zlatanov [this message]
2013-12-16 18:25         ` bug#16161: 24.3.50; gnutls connections from Gnus no longer work after r115526, " Eli Zaretskii
2013-12-16 18:53           ` Ted Zlatanov
2013-12-16 19:50             ` Nix

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=87zjo0n1d3.fsf@flea.lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=16161@debbugs.gnu.org \
    --cc=eggert@gnu.org \
    --cc=schwab@suse.de \
    /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.