From: Tassilo Horn <tsdh@gnu.org>
To: George McNinch <gmcninch@gmail.com>
Cc: ding@gnus.org
Subject: Re: message-send-and-exit
Date: Mon, 06 May 2013 14:58:26 +0200 [thread overview]
Message-ID: <87mws8mfil.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <878v3tf669.fsf@gmail.com> (George McNinch's message of "Sun, 05 May 2013 17:49:50 -0400")
George McNinch <gmcninch@gmail.com> writes:
> Subsequent to a recent git commit:
>
> ,----
> | commit 1d2c4fbb9bdc1078d1727b27139e4df5ba7cb2cb (patch) (side-by-side diff)
> | tree 17f735797a5312b5366f1ed9bccf3380c179ed26
> | parent 0fceb665e268e9749e51e72f453b785b1a1ee596 (diff)
> |
> | message.el (message-bury): Make `buffer' optional; HEAD master
> | (message-send-and-exit): Don't pass `buf' so as to hide the buffer (bug#14085)
> `----
>
> I seem to get the error
>
> message-send-and-exit: Wrong type argument: stringp, nil
>
> every time I send a message.
That problem already came up in <878v3so8s6.fsf@thinkpad.tsdh.de>, and
for the time being, I've reverted that commit.
Bye,
Tassilo
prev parent reply other threads:[~2013-05-06 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-05 21:49 message-send-and-exit George McNinch
2013-05-06 12:58 ` Tassilo Horn [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mws8mfil.fsf@thinkpad.tsdh.de \
--to=tsdh@gnu.org \
--cc=ding@gnus.org \
--cc=gmcninch@gmail.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.
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 NNTP newsgroup(s).