From: Dmitry Kurochkin <dmitry.kurochkin@gmail.com>
To: Carl Worth <cworth@cworth.org>
Cc: notmuch@notmuchmail.org, Austin Clements <amdragon@MIT.EDU>
Subject: Re: [PATCH 2/2] test: use emacsclient(1) for Emacs tests
Date: Wed, 29 Jun 2011 00:58:41 +0400 [thread overview]
Message-ID: <87k4c5y8ou.fsf@gmail.com> (raw)
In-Reply-To: <87zkl190od.fsf@yoom.home.cworth.org>
On Tue, 28 Jun 2011 13:10:58 -0700, Carl Worth <cworth@cworth.org> wrote:
Non-text part: multipart/signed
> On Tue, 28 Jun 2011 20:42:42 +0400, Dmitry Kurochkin <dmitry.kurochkin@gmail.com> wrote:
> > I would like to hear what other (Carl in particular) think about this.
> > If the consensus is for your approach, I would be happy to implement
> > it.
>
> In general, I love the whole series, thanks! I'm looking forward to our
> future, faster test suite.
>
BTW Carl, while we continue our debate, you may consider applying the
first 9 patches from the series :)
id:"1309236311-2162-1-git-send-email-dmitry.kurochkin@gmail.com"
Regards,
Dmitry
> Even more, I love the constructive dialog that follows the original
> series and the attention being focused on getting things right.
>
> As for the detail of whether to use emacsclient or Austin's look-alike,
> I don't have a strong attachment to either solution. I do appreciate
> concrete technical things like "robust against recycled PIDs", "more
> robust against leaving daemon's around for some reason", etc.
>
> Would any of this potentially interfere with my own usage of emacsclient
> and emacs server? I use them regularly and would be quite surprised (and
> likely frustrated) if the test suite got mixed up with my existing emacs
> server (or the other way around). Maybe that's already taken care of
> with either approach? (A quick skim of the emacsclient manual age didn't
> make it obvious to me how emacslcient finds its server.)
>
> -Carl
>
> --
> carl.d.worth@intel.com
Non-text part: application/pgp-signature
next prev parent reply other threads:[~2011-06-28 20:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-26 23:52 [PATCH 1/5] test: do not set `message-signature' in test_emacs Dmitry Kurochkin
2011-06-26 23:52 ` [PATCH 2/5] test: cleanup test_emacs Dmitry Kurochkin
2011-06-26 23:52 ` [PATCH 3/5] test: wrap and indent test_emacs calls Dmitry Kurochkin
2011-06-26 23:52 ` [PATCH 4/5] test: save buffer content to file instead of printing it in Emacs tests Dmitry Kurochkin
2011-06-26 23:52 ` [PATCH 5/5] test: remove some sed(1) calls " Dmitry Kurochkin
2011-06-27 3:54 ` [PATCH 1/2] test: use emacs_deliver_message in Emacs SMTP send test Dmitry Kurochkin
2011-06-27 3:54 ` [PATCH 2/2] test: use emacsclient(1) for Emacs tests Dmitry Kurochkin
2011-06-27 20:02 ` Austin Clements
2011-06-27 20:22 ` Dmitry Kurochkin
2011-06-27 20:32 ` Austin Clements
2011-06-28 1:03 ` Dmitry Kurochkin
2011-06-28 3:49 ` Austin Clements
2011-06-28 3:59 ` Dmitry Kurochkin
2011-06-28 4:17 ` Austin Clements
2011-06-28 4:44 ` Dmitry Kurochkin
2011-06-28 16:22 ` Austin Clements
2011-06-28 16:42 ` Dmitry Kurochkin
2011-06-28 20:10 ` Carl Worth
2011-06-28 20:47 ` Dmitry Kurochkin
2011-06-28 22:41 ` Carl Worth
2011-06-28 20:58 ` Dmitry Kurochkin [this message]
2011-06-28 22:42 ` Carl Worth
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k4c5y8ou.fsf@gmail.com \
--to=dmitry.kurochkin@gmail.com \
--cc=amdragon@MIT.EDU \
--cc=cworth@cworth.org \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).