From mboxrd@z Thu Jan  1 00:00:00 1970
Received: by 10.52.162.5 with SMTP id xw5csp433836vdb;
        Fri, 2 Aug 2013 06:18:38 -0700 (PDT)
X-Received: by 10.182.148.8 with SMTP id to8mr3135026obb.17.1375449517957;
        Fri, 02 Aug 2013 06:18:37 -0700 (PDT)
Return-Path: <sup-talk-bounces@rubyforge.org>
Received: from rubyforge.org ([50.56.192.79])
        by mx.google.com with ESMTP id c1si4268234oeq.127.2013.08.02.06.18.37
        for <eg@gaute.vetsj.com>;
        Fri, 02 Aug 2013 06:18:37 -0700 (PDT)
Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) client-ip=50.56.192.79;
Authentication-Results: mx.google.com;
       spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org
Received: from localhost.localdomain (localhost [127.0.0.1])
	by rubyforge.org (Postfix) with ESMTP id 1EF3B2E20D;
	Fri,  2 Aug 2013 13:18:32 +0000 (UTC)
Received: from mail-ve0-f172.google.com (mail-ve0-f172.google.com
	[209.85.128.172]) by rubyforge.org (Postfix) with ESMTP id 007222E145
	for <sup-talk@rubyforge.org>; Wed, 10 Jul 2013 02:44:58 +0000 (UTC)
Received: by mail-ve0-f172.google.com with SMTP id jz10so5286864veb.17
	for <sup-talk@rubyforge.org>; Tue, 09 Jul 2013 19:44:58 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=content-type:from:to:subject:date:message-id:user-agent
	:content-transfer-encoding:x-gm-message-state;
	bh=6djwZu1P5WSfhpwaMszW9ceriRFThCab+4ZMQ3nIbfM=;
	b=XVyIXchx/lofVxiywQMt6svOsIoClk9E7YPCY1ytJGOBBV0cs4Moe7LfdrDo/ny+A9
	+AAY5dzri8nZSX085RDdQiYr0oQTELVidQ1qZnKN+fy9pg/k21yyTWQ4R0tL6fqNDfUX
	2f5UqEYX/v2vWxviH4snzaD26FTXj/9+9v84qRtr4D0N0rowsBxRWuM9TWPYUKqhRLFa
	ALJUna5heMkcuSaraq/54Hv4AIFwR0AhFjm8aZuDIg4P10SzhTxbeRX1peHfIOhuqbno
	Nt8+Pj0C19Lsr5SE5kWXhfuWxet6Pqy/zDDXzN8yq7iTRlRYNIJJWUYRqp5YjoPysoTE
	wgLA==
X-Received: by 10.58.40.16 with SMTP id t16mr17848636vek.64.1373410843496;
	Tue, 09 Jul 2013 16:00:43 -0700 (PDT)
Received: from localhost (c-174-63-120-188.hsd1.ma.comcast.net.
	[174.63.120.188])
	by mx.google.com with ESMTPSA id ir5sm22210778veb.6.2013.07.09.16.00.42
	for <sup-talk@rubyforge.org>
	(version=TLSv1 cipher=RC4-SHA bits=128/128);
	Tue, 09 Jul 2013 16:00:42 -0700 (PDT)
From: Steven Schmeiser <steven@schmeiser.org>
To: sup-talk <sup-talk@rubyforge.org>
Date: Tue, 09 Jul 2013 19:00:39 -0400
Message-Id: <1373410624-sup-1657@indy.local>
User-Agent: Sup/git
X-Gm-Message-State: ALoCoQmizxaNPVNYML7Vu3XNrwFb24EYjorXsTQNyzQ4hJzWCSGHOHCktHbENusOPZ+OYkStySPb
Subject: [sup-talk] always use async editing?
X-BeenThere: sup-talk@rubyforge.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: User & developer discussion of Sup <sup-talk.rubyforge.org>
List-Unsubscribe: <http://rubyforge.org/mailman/options/sup-talk>,
	<mailto:sup-talk-request@rubyforge.org?subject=unsubscribe>
List-Archive: <http://rubyforge.org/pipermail/sup-talk>
List-Post: <mailto:sup-talk@rubyforge.org>
List-Help: <mailto:sup-talk-request@rubyforge.org?subject=help>
List-Subscribe: <http://rubyforge.org/mailman/listinfo/sup-talk>,
	<mailto:sup-talk-request@rubyforge.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sup-talk-bounces@rubyforge.org
Errors-To: sup-talk-bounces@rubyforge.org


Is there a way to always use async editing when composing a reply or new
message?  Right now, when I reply to a message, I hit 'E' then 'H' to
launch my async editor.  Can this be configured as the default
behavior and can asyn mode be used to compose new messages (without
going back and editing a draft?)

Steve
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk