From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Anirudh Sanjeev <anirudh@anirudhsanjeev.org>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] [PATCH 1/4] Add method to shell out asynchronously
Date: Sun, 11 Apr 2010 01:42:59 +0530 [thread overview]
Message-ID: <w2of3271551004101312r9ad11837y91d363153f0fc182@mail.gmail.com> (raw)
In-Reply-To: <1270928203-sup-5488@deepthought>
On Sun, Apr 11, 2010 at 1:10 AM, Anirudh Sanjeev
<anirudh@anirudhsanjeev.org> wrote:
> Perhaps adding a custom option in config.yaml to launch editor
> asynchronously might be a better option, and also suggest sensible
> defaults.
Did you even read the patch? That's what I've done. From PATCH 4/4:
+ editor_daemon = $config[:editor_daemon]
-- Ram
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-04-10 20:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-10 10:37 Ramkumar Ramachandra
2010-04-10 19:40 ` Anirudh Sanjeev
2010-04-10 20:12 ` Ramkumar Ramachandra [this message]
2010-04-10 20:21 ` Anirudh Sanjeev
2010-04-11 2:50 ` Ramkumar Ramachandra
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=w2of3271551004101312r9ad11837y91d363153f0fc182@mail.gmail.com \
--to=artagnon@gmail.com \
--cc=anirudh@anirudhsanjeev.org \
--cc=sup-talk@rubyforge.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox