From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.117.16 with SMTP id p16cs487859agc; Mon, 2 Nov 2009 11:29:59 -0800 (PST) Received: by 10.224.85.202 with SMTP id p10mr3059851qal.351.1257190199205; Mon, 02 Nov 2009 11:29:59 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 27si7469179qyk.89.2009.11.02.11.29.59; Mon, 02 Nov 2009 11:29:59 -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 Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id D9C8F1D7885B; Mon, 2 Nov 2009 14:29:58 -0500 (EST) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 4B7DD1858291 for ; Mon, 2 Nov 2009 14:22:49 -0500 (EST) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1N52UL-0005OC-0N for sup-talk@rubyforge.org; Mon, 02 Nov 2009 11:22:49 -0800 From: William Morgan To: sup-talk In-reply-to: References: Date: Mon, 02 Nov 2009 11:22:48 -0800 Message-Id: <1257189701-sup-8211@masanjin.net> User-Agent: Sup/git Subject: Re: [sup-talk] "Force tags to be joined" doesn't save 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 Reformatted excerpts from Steven Walter's message of 2009-11-02: > If I select two threads and combine them with #, sup seems to combine > them, and the current view becomes "modified." If I save ($) and > reload (@), the threads show up separately again. Is this expected > behavior? I pushed a fix for this to master yesterday. Do you still have this with a recent git? (I.e. one with cc2359bf87bd982501e57f703fbf4368b7f9cb5f). -- William _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk