From 95baa25ff0d2a02117932c5f9bc965a347945e1f Mon Sep 17 00:00:00 2001 From: Katsumi Yamaoka Date: Mon, 3 Oct 2016 02:43:20 +0000 Subject: [PATCH 1/3] * doc/misc/message.texi (Bcc Warning): Document mml-secure-safe-bcc-list. --- doc/misc/message.texi | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/doc/misc/message.texi b/doc/misc/message.texi index 761fb772f46..2e664b9a0f3 100644 --- a/doc/misc/message.texi +++ b/doc/misc/message.texi @@ -1326,7 +1326,13 @@ OpenPGP) or @code{mml-secure-smime-encrypt-to-self} (for The @code{Bcc} header is meant to hide recipients of messages. However, when encrypted messages are used, the e-mail addresses of all @code{Bcc}-headers are given away to all recipients without -warning, which is a bug, see +warning, which is a bug. +@vindex mml-secure-safe-bcc-list +But now Message got to warn if Bcc recipients are found in an encrypted +message when you are just about to send it. If you are sure those +@code{Bcc} addresses are safe to expose, set the +@code{mml-secure-safe-bcc-list} variable, that is a list of e-mail +addresses. See @uref{https://debbugs.gnu.org/cgi/bugreport.cgi?bug=18718}. From 9fc81bcf74a3cf710b6a014ec3a490ad713a0775 Mon Sep 17 00:00:00 2001 From: Katsumi Yamaoka Date: Mon, 3 Oct 2016 03:03:40 +0000 Subject: [PATCH 2/3] * doc/misc/message.texi (Bcc Warning): Fix markup. --- doc/misc/message.texi | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/misc/message.texi b/doc/misc/message.texi index 2e664b9a0f3..0b82f343d71 100644 --- a/doc/misc/message.texi +++ b/doc/misc/message.texi @@ -1328,9 +1328,9 @@ However, when encrypted messages are used, the e-mail addresses of all @code{Bcc}-headers are given away to all recipients without warning, which is a bug. @vindex mml-secure-safe-bcc-list -But now Message got to warn if Bcc recipients are found in an encrypted -message when you are just about to send it. If you are sure those -@code{Bcc} addresses are safe to expose, set the +But now Message got to warn if @code{Bcc} recipients are found in an +encrypted message when you are just about to send it. If you are sure +those @code{Bcc} addresses are safe to expose, set the @code{mml-secure-safe-bcc-list} variable, that is a list of e-mail addresses. See @uref{https://debbugs.gnu.org/cgi/bugreport.cgi?bug=18718}. From 74b4f13842f3119f98797ea76d9be42457b330e1 Mon Sep 17 00:00:00 2001 From: Philipp Stephani Date: Sun, 2 Oct 2016 19:58:39 +0200 Subject: [PATCH 3/3] Document nil args of compare-buffer-substrings * editfns.c (Fcompare_buffer_substrings): Document behavior when the arguments are nil. --- src/editfns.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/editfns.c b/src/editfns.c index 51b87de8821..4e90dad568f 100644 --- a/src/editfns.c +++ b/src/editfns.c @@ -2892,6 +2892,10 @@ Return -N if first string is less after N-1 chars, +N if first string is greater after N-1 chars, or 0 if strings match. The first substring is in BUFFER1 from START1 to END1 and the second is in BUFFER2 from START2 to END2. +All arguments may be nil. If BUFFER1 or BUFFER2 is nil, the current +buffer is used. If START1 or START2 is nil, the value of `point-min' +in the respective buffers is used. If END1 or END2 is nil, the value +of `point-max' in the respective buffers is used. The value of `case-fold-search' in the current buffer determines whether case is significant or ignored. */) (Lisp_Object buffer1, Lisp_Object start1, Lisp_Object end1, Lisp_Object buffer2, Lisp_Object start2, Lisp_Object end2)