From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.224.197 with SMTP id ip5cs38754icb; Thu, 17 Feb 2011 01:49:21 -0800 (PST) Received: by 10.224.73.198 with SMTP id r6mr2189890qaj.359.1297936161147; Thu, 17 Feb 2011 01:49:21 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id i34si1347739qck.16.2011.02.17.01.49.20; Thu, 17 Feb 2011 01:49:21 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 3FBE43C8033; Thu, 17 Feb 2011 04:49:20 -0500 (EST) Received: from mail-ey0-f178.google.com (mail-ey0-f178.google.com [209.85.215.178]) by rubyforge.org (Postfix) with ESMTP id C7AF918581B2 for ; Thu, 17 Feb 2011 04:20:15 -0500 (EST) Received: by eyh5 with SMTP id 5so1242048eyh.23 for ; Thu, 17 Feb 2011 01:20:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:content-type:subject:from:to:in-reply-to :references:date:message-id:user-agent:content-transfer-encoding; bh=iddDoIW9waIcxcmuTJCZiMiil9aj6uc03jUIXd6Lvpo=; b=MctwkPNR/9ZfjfroGC8Ul+eSD9NbmdW+ysmzH7rApmnRwCYosqmAqJFARJDhiguQUI ruuOiZW3fc/FTWGoCrH4jPibYgKkWT+mGCpu0K5QNrdriU+CCalGcoo8TiBEdNR9nQM9 nNYa8wBcvEJeQCyU3EYmVHbRhC1RpJ6hs1ru8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:subject:from:to:in-reply-to:references:date:message-id :user-agent:content-transfer-encoding; b=hp8yS/Mcfyrrx1QAmtl7aeBjcl4ai5jWZ0GH6zffG7Ug/yCQhveBl7oEQT6VIzHuLT wAHgt+2p1ZKNO+t3Cv/k5d34bRcoKdpaLyTL1K30QQq7SAKtNwpa/5hVeSbEI50ExdrJ lfQxoQeu70XFOH3ME6+2MRUp/9dRJ8FQ0/XTc= Received: by 10.213.23.5 with SMTP id p5mr1911011ebb.81.1297934414803; Thu, 17 Feb 2011 01:20:14 -0800 (PST) Received: from localhost ([78.144.150.19]) by mx.google.com with ESMTPS id t50sm673618eeh.6.2011.02.17.01.20.12 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 17 Feb 2011 01:20:12 -0800 (PST) From: Shadowfirebird To: sup-talk In-reply-to: <1297887707-sup-809@plc.intranet.plecavalier.com> References: <1297887707-sup-809@plc.intranet.plecavalier.com> Date: Thu, 17 Feb 2011 09:20:10 +0000 Message-Id: <1297934366-sup-3072@blake> User-Agent: Sup/0.12 Subject: Re: [sup-talk] Body preview separator inbox-mode X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 > Could we have a body preview separator(| or , maybe?). I find it less > efficient when visually browsing the inbox-mode to not have any kind of > separator between each thread/response. +1. I can't tell what's subject and what's message body 'hint'. -- A boss with no humor is like a job that's no fun. _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk