<?xml version="1.0" encoding="UTF-8" ?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>vimdev at Yahoo! Groups</title>
    <link>http://tech.groups.yahoo.com/group/vimdev/</link>
    <description>Vim (Vi IMproved) text editor developers list</description>

    <item>
      <title>Re: (patch) Lua interface</title>
      <pubDate>Thu, 04 Sep 2008 22:50:22 GMT</pubDate>
      <dc:creator>Paul Moore</dc:creator>
      <link>http://tech.groups.yahoo.com/group/vimdev/message/51954</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/vimdev/message/51954</guid>
      <description>On Sep 4, 8:55 pm, Tony Mechelynck &lt;antoine.mechely...@...&gt; ... That&#39;s my view. ... The only issue here is that Lua allows loading of extension modules </description>
    </item>
    <item>
      <title>Re: Bug with screen redraw introduced by 7.1.329</title>
      <pubDate>Thu, 04 Sep 2008 20:32:36 GMT</pubDate>
      <dc:creator>Matt Wozniski</dc:creator>
      <link>http://tech.groups.yahoo.com/group/vimdev/message/51953</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/vimdev/message/51953</guid>
      <description>... I can confirm this.  The numbers are really ASCII digits being added at EOL. ... I can reproduce this one as well, and can also confirm that resetting </description>
    </item>
    <item>
      <title>Re: Bug with screen redraw introduced by 7.1.329</title>
      <pubDate>Thu, 04 Sep 2008 20:09:49 GMT</pubDate>
      <dc:creator>Bram Moolenaar</dc:creator>
      <link>http://tech.groups.yahoo.com/group/vimdev/message/51952</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/vimdev/message/51952</guid>
      <description>... That condition is needed for when the right halve of a double-wide character is drawn over any character that used to be there.  We can&#39;t simply remove it.</description>
    </item>
    <item>
      <title>Re: (patch) Lua interface</title>
      <pubDate>Thu, 04 Sep 2008 19:56:26 GMT</pubDate>
      <dc:creator>Tony Mechelynck</dc:creator>
      <link>http://tech.groups.yahoo.com/group/vimdev/message/51951</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/vimdev/message/51951</guid>
      <description>... 1. If the interface uses a separate DLL, then the absence of that DLL must not prevent Vim from running (as long as the interface isn&#39;t used, of course). </description>
    </item>
    <item>
      <title>Tags/attributes for indentation</title>
      <pubDate>Thu, 04 Sep 2008 15:18:23 GMT</pubDate>
      <dc:creator>David Baelde</dc:creator>
      <link>http://tech.groups.yahoo.com/group/vimdev/message/51950</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/vimdev/message/51950</guid>
      <description>Hi, I&#39;m the author of omlet, an indentation mode for Ocaml. I gave up developing and even maintaining it, and I&#39;m looking for a good way to restart it from</description>
    </item>
    <item>
      <title>Re: (patch) Lua interface</title>
      <pubDate>Thu, 04 Sep 2008 14:38:43 GMT</pubDate>
      <dc:creator>Paul Moore</dc:creator>
      <link>http://tech.groups.yahoo.com/group/vimdev/message/51949</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/vimdev/message/51949</guid>
      <description>... On Windows, things get a little odd, as linking Lua as a DLL has 2 negative effects: 1. If lua51.dll isn&#39;t present, Vim won&#39;t start. This is fixable, but </description>
    </item>
    <item>
      <title>Re: (patch) Lua interface</title>
      <pubDate>Thu, 04 Sep 2008 01:44:32 GMT</pubDate>
      <dc:creator>Luis Carvalho</dc:creator>
      <link>http://tech.groups.yahoo.com/group/vimdev/message/51948</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/vimdev/message/51948</guid>
      <description>Hi Andy, ... That makes sense. I&#39;ve updated configure.in to link a shared lib. ... Thanks for the report. The latest patch, available at </description>
    </item>
    <item>
      <title>Re: Global cpo_save</title>
      <pubDate>Thu, 04 Sep 2008 00:41:25 GMT</pubDate>
      <dc:creator>Bill McCarthy</dc:creator>
      <link>http://tech.groups.yahoo.com/group/vimdev/message/51947</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/vimdev/message/51947</guid>
      <description>... Thanks for your and Ben&#39;s comments.  Of course simply adding an &quot;unlet&quot; doesn&#39;t solve the problem.  The problem is that a global is used.  If you had a</description>
    </item>
    <item>
      <title>Re: Global cpo_save</title>
      <pubDate>Thu, 04 Sep 2008 00:30:09 GMT</pubDate>
      <dc:creator>Bill McCarthy</dc:creator>
      <link>http://tech.groups.yahoo.com/group/vimdev/message/51946</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/vimdev/message/51946</guid>
      <description>... Thanks! Most scripts follow the same scheme, starting with let s:cpo_save = &amp;cpo &quot; adjust cpo and end with let &amp;cpo = s:cpo_save unlet s:cpo_save Besides</description>
    </item>
    <item>
      <title>Re: (patch) Lua interface</title>
      <pubDate>Wed, 03 Sep 2008 22:01:56 GMT</pubDate>
      <dc:creator>Andy Kittner</dc:creator>
      <link>http://tech.groups.yahoo.com/group/vimdev/message/51945</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/vimdev/message/51945</guid>
      <description>... Hi, First of all thanks for the patch, I&#39;ve also been toying around with Lua support in vim, but up to now it&#39;s only a sandbox for playing around with</description>
    </item>
    <item>
      <title>Re: Bug with screen redraw introduced by 7.1.329</title>
      <pubDate>Wed, 03 Sep 2008 21:13:18 GMT</pubDate>
      <dc:creator>Ingo Karkat</dc:creator>
      <link>http://tech.groups.yahoo.com/group/vimdev/message/51944</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/vimdev/message/51944</guid>
      <description>... Do you use the big or huge version of VIM? The &#39;rightleft&#39; feature, which is enabled in the big version, causes these redraws. See this comment in </description>
    </item>
    <item>
      <title>Re: synIDattr() and &#39;guisp&#39; attribute [with patch]</title>
      <pubDate>Wed, 03 Sep 2008 20:34:01 GMT</pubDate>
      <dc:creator>Bram Moolenaar</dc:creator>
      <link>http://tech.groups.yahoo.com/group/vimdev/message/51943</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/vimdev/message/51943</guid>
      <description>... It&#39;s in the todo list. -- I am also told that there is a logical proof out there somewhere that demonstrates that there is no task which duct tape cannot</description>
    </item>
    <item>
      <title>Re: Global cpo_save</title>
      <pubDate>Wed, 03 Sep 2008 20:13:24 GMT</pubDate>
      <dc:creator>Bram Moolenaar</dc:creator>
      <link>http://tech.groups.yahoo.com/group/vimdev/message/51942</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/vimdev/message/51942</guid>
      <description>... I&#39;ll fix vim.vim and matchparen.vim.  Sorry I didn&#39;t notice this mistake before. I&#39;ll leave hamster.vim to David. -- How To Keep A Healthy Level Of</description>
    </item>
    <item>
      <title>Bug with screen redraw introduced by 7.1.329</title>
      <pubDate>Wed, 03 Sep 2008 18:58:26 GMT</pubDate>
      <dc:creator>Tyler Spivey</dc:creator>
      <link>http://tech.groups.yahoo.com/group/vimdev/message/51941</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/vimdev/message/51941</guid>
      <description>... Hash: SHA1 hello. I have noticed that starting from 7.1.329, using vim in the console with the encoding set to utf8, there is a bug with redrawing</description>
    </item>
    <item>
      <title>Re: Global cpo_save</title>
      <pubDate>Wed, 03 Sep 2008 15:33:29 GMT</pubDate>
      <dc:creator>Tony Mechelynck</dc:creator>
      <link>http://tech.groups.yahoo.com/group/vimdev/message/51940</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/vimdev/message/51940</guid>
      <description>... The &quot;:let&quot; statement never remembers where its operand was set (unlike ... In this case, the above precautions are prudent, but only really necessary if</description>
    </item>

  </channel>
</rss>
<!-- wr1.grp.scd.yahoo.com uncompressed/chunked Fri Sep  5 06:50:41 PDT 2008 -->
