From: Stefan Monnier <monnier@iro.umontreal.ca>
To: 16805@debbugs.gnu.org
Subject: bug#16805: 24.3.50; url-cookie-write-file: set print-length
Date: Tue, 13 Jan 2015 14:59:11 -0500 [thread overview]
Message-ID: <jwvlhl6312r.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <87sifewo3r.fsf@violet.siamics.net> (Ivan Shmakov's message of "Tue, 13 Jan 2015 18:07:52 +0000")
> I believe I’ve managed to stumble upon this myself, and was able
> to successfully overcome the issue with the patch MIMEd.
Looks good, thanks,
Stefan "yes, we have kind of mess in this print-* dynbind
configuration of the printing system. Someone already
suggested we provide a `with-default-print-config' macro
as a first step to sanity."
prev parent reply other threads:[~2015-01-13 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 2:39 bug#16805: 24.3.50; url-cookie-write-file: set print-length raman
2015-01-13 18:07 ` Ivan Shmakov
2015-01-13 19:59 ` Stefan Monnier [this message]
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=jwvlhl6312r.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=16805@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).