From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: darael@dracon.is, tzz@lifelogs.com, 33780@debbugs.gnu.org
Subject: bug#33780: network-stream.el: network-stream-certificate always returns nil
Date: Sat, 12 Jan 2019 13:13:04 +0200 [thread overview]
Message-ID: <83o98mf7sv.fsf@gnu.org> (raw)
In-Reply-To: <m2a7ka5coh.fsf@gmail.com> (message from Robert Pluim on Wed, 09 Jan 2019 11:48:46 +0100)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: Vinothan Shankar <darael@dracon.is>, eliz@gnu.org, Ted Zlatanov <tzz@lifelogs.com>
> Date: Wed, 09 Jan 2019 11:48:46 +0100
Thanks, a few comments regarding the Texinfo part:
> +Passing @code{:client certificate t} triggers looking up of client
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This should be wrapped in @w{..}, otherwise makeinfo might divide it
between two lines.
> +certificates matching @var{host} and @var{service} using the
> +'auth-source' library. Any resulting client certificates are passed
auth-source should be in @file, and without the quotes.
> +down to the lower TLS layers. The format used by @file{.authinfo} to
> +specify the per-server keys is described in @xref{Help for
> +users,,auth-source, auth, Emacs auth-source Library}.
@xref can only be used at the beginning of a sentence, as it generates
a capitalizes "See". Use "see @ref" instead here.
next prev parent reply other threads:[~2019-01-12 11:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 19:02 bug#33780: network-stream.el: network-stream-certificate always returns nil Vinothan Shankar
2018-12-19 17:19 ` Robert Pluim
2018-12-20 11:24 ` Vinothan Shankar
2018-12-20 18:45 ` Robert Pluim
2018-12-21 13:16 ` Robert Pluim
2019-01-09 10:48 ` Robert Pluim
2019-01-12 11:13 ` Eli Zaretskii [this message]
2019-01-14 13:27 ` Robert Pluim
2019-01-14 16:00 ` Eli Zaretskii
2019-01-14 16:25 ` Robert Pluim
2019-01-14 16:45 ` Eli Zaretskii
2019-01-14 17:40 ` Robert Pluim
2019-01-14 18:51 ` Eli Zaretskii
2019-01-15 20:31 ` Robert Pluim
2019-01-24 10:40 ` Robert Pluim
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=83o98mf7sv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33780@debbugs.gnu.org \
--cc=darael@dracon.is \
--cc=rpluim@gmail.com \
--cc=tzz@lifelogs.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.