From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.228.134 with SMTP id je6cs372069icb; Mon, 10 Jan 2011 13:18:42 -0800 (PST) Received: by 10.236.95.41 with SMTP id o29mr5804796yhf.29.1294694319430; Mon, 10 Jan 2011 13:18:39 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id u10si20425811vbx.75.2011.01.10.13.18.39; Mon, 10 Jan 2011 13:18:39 -0800 (PST) Received-SPF: pass (google.com: domain of sup-devel-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-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-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 AB70D167831F; Mon, 10 Jan 2011 16:18:38 -0500 (EST) Received: from mail-fx0-f50.google.com (mail-fx0-f50.google.com [209.85.161.50]) by rubyforge.org (Postfix) with ESMTP id C494A185835E for ; Mon, 10 Jan 2011 16:09:11 -0500 (EST) Received: by fxm14 with SMTP id 14so18629415fxm.23 for ; Mon, 10 Jan 2011 13:09:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=X8DnrTeQz2248Xi3tt5+MTT5YI1+LT97c7iW/kGIAI0=; b=sg9vFYjVpeQ581I/16JVq2W+Ny0wio4q8E/vPqdRvfLrJG26irXH6gtWFhRRPrvw8F 5cly+rnLUriGon3mICBLl8+GW6tvWb7k0a06NrzOu4WtUN2iXasUBPFauA0NRE4KP5Sd Gf/h8eA3vHekYYLpmMw78GLY8K5gxqD3fF6k0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=pJSEk7oichsC9TcKnIN4Z9Q488+Sg+tM1oLE6VG5ib86vTvwEN9MbejH1D3OIE1jNC MyBFMo69AUM52gWZ9IHN9z2yww+Zljc97T6FB5pNsEZkObAz5UF7G/ep/XG44fVC1plR Z8Umg2D4r0P/sUMIz8sjX5waAxn99tiMK38Tc= MIME-Version: 1.0 Received: by 10.223.78.138 with SMTP id l10mr479579fak.17.1294693750846; Mon, 10 Jan 2011 13:09:10 -0800 (PST) Received: by 10.223.159.141 with HTTP; Mon, 10 Jan 2011 13:09:10 -0800 (PST) In-Reply-To: <1294691658-sup-2474@mithink> References: <1294691658-sup-2474@mithink> Date: Mon, 10 Jan 2011 16:09:10 -0500 Message-ID: From: Steve To: Michael Hamann Cc: sup-devel Subject: Re: [sup-devel] Bug report: temp file commit breaks my emacs hook X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org On Mon, Jan 10, 2011 at 3:48 PM, Michael Hamann wrote: > Hi, > > Excerpts from Steve's message of 2011-01-10 21:11:35 +0100: >> This commit has broken part of the interaction between sup and my emacs. >> >> commit 60573298a2258c101a85b3de8121f73d7aec2d51 >> Author: Michael Hamann >> Date: =A0 Fri Oct 8 10:03:36 2010 -0400 >> >> =A0 =A0 Fix monkey-patching of Tempfile >> >> >> Did you change the name of the temp file that gets passed to emacs? > > Yes. Now sup can and must use the syntax for Tempfile creation that is > available in Ruby version 1.8.7 and newer. It allows to set both a > prefix and a suffix. I didn't care about the filename because I had the > experience that with the old filename my Vim didn't recognize the > content as email and without the extension it recognizes it which gives > me nice syntax highlighting even without configuring anything. > >> My emacs hook looks like this. >> >> (add-to-list 'auto-mode-alist >> '("sup\\.\\(compose\\|forward\\|reply\\|resume\\)-mode$" . mail-mode)) > > The string you are looking for is now at the beginning of the filename > so you could change your hook to match the beginning of the filename > instead of the end. Makes sense. I have corrected my emacs pattern. No need to patch. Thanks! _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel