unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: 16253@debbugs.gnu.org
Subject: bug#16253: 24.3.50; Irrelevant warnings from gnutls
Date: Sun, 09 Feb 2014 19:01:16 -0800	[thread overview]
Message-ID: <87lhxjwu0z.fsf@building.gnus.org> (raw)
In-Reply-To: <87sirr8zmp.fsf@lifelogs.com> (Ted Zlatanov's message of "Sun, 09 Feb 2014 21:34:06 -0500")

Ted Zlatanov <tzz@lifelogs.com> writes:

> OK.  I will log them to a special " *TLS errors*" buffer.  That's a good
> balance.

Yeah, that would be good.  And perhaps limit the size of the buffer.

> Doing that from C is not obvious, compared to the standard `message'
> function.  Any hints?  Should I just call `Fget-buffer-create' and
> call functions to append to the returned buffer Lisp_Object, or is there
> a magical equivalent?

I just had a look at message_dolog (which puts data into the *Messages*
buffer).  It didn't look pretty...  Is all that really necessary?

> Also, I think we should add that buffer, plus the version of GnuTLS and
> the priority string, to bug reports.  WDYT?

For all Emacs bug reports?  Hm...

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/





  reply	other threads:[~2014-02-10  3:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-25  9:09 bug#16253: 24.3.50; Irrelevant warnings from gnutls Lars Ingebrigtsen
2014-01-07 23:47 ` Ted Zlatanov
2014-01-18 17:29   ` Lars Ingebrigtsen
2014-01-18 17:57     ` Eli Zaretskii
2014-01-20 16:11       ` Ted Zlatanov
2014-01-18 18:06     ` Lars Ingebrigtsen
2014-01-20 16:11       ` Ted Zlatanov
2014-01-20 20:19         ` Lars Ingebrigtsen
2014-02-10  2:34           ` Ted Zlatanov
2014-02-10  3:01             ` Lars Ingebrigtsen [this message]
2014-02-10 10:42               ` Ted Zlatanov
2014-12-08 19:58 ` Lars Magne Ingebrigtsen

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lhxjwu0z.fsf@building.gnus.org \
    --to=larsi@gnus.org \
    --cc=16253@debbugs.gnu.org \
    /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 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).