<html>
<body>
<div style="font-family: Verdana, Arial, Helvetica, Sans-Serif;">
<table bgcolor="#f9f3c9" width="100%" cellpadding="8" style="border: 1px #c9c399 solid;">
<tr>
<td>
This is an automatically generated e-mail. To reply, visit:
<a href="http://git.reviewboard.kde.org/r/110713/">http://git.reviewboard.kde.org/r/110713/</a>
</td>
</tr>
</table>
<br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<p style="margin-top: 0;">On May 29th, 2013, 8:10 p.m. UTC, <b>Andreas Pakulat</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<table width="100%" border="0" bgcolor="white" style="border: 1px solid #C0C0C0; border-collapse: collapse; margin: 2px padding: 2px;">
<thead>
<tr>
<th colspan="4" bgcolor="#F0F0F0" style="border-bottom: 1px solid #C0C0C0; font-size: 9pt; padding: 4px 8px; text-align: left;">
<a href="http://git.reviewboard.kde.org/r/110713/diff/2/?file=146917#file146917line792" style="color: black; font-weight: bold; text-decoration: underline;">shell/textdocument.cpp</a>
<span style="font-weight: normal;">
(Diff revision 2)
</span>
</th>
</tr>
</thead>
<tbody>
<tr>
<th bgcolor="#b1ebb0" style="border-right: 1px solid #C0C0C0;" align="right"><font size="2"></font></th>
<td bgcolor="#c5ffc4" width="50%"><pre style="font-size: 8pt; line-height: 140%; margin: 0; "></pre></td>
<th bgcolor="#b1ebb0" style="border-left: 1px solid #C0C0C0; border-right: 1px solid #C0C0C0;" align="right"><font size="2">790</font></th>
<td bgcolor="#c5ffc4" width="50%"><pre style="font-size: 8pt; line-height: 140%; margin: 0; "><span class="cp">#if ( KDE_VERSION_MAJOR == 4 && KDE_VERSION_MINOR >= 11 ) || KDE_VERSION_MAJOR > 4</span></pre></td>
</tr>
</tbody>
</table>
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Not sure you want to dive into this, but one could use cmake to try to do a compile-test with the header exposing the enum and a short snippet that uses the enum. If the compile-test succeeds the cmake code can set a define and else not set it so this code could be also enabled for people building kate+kte from git.
I think there already is a config.h.in or so which has such defines in the kdevplatform root.</pre>
</blockquote>
<p>On May 29th, 2013, 9:43 p.m. UTC, <b>Sven Brauch</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">To be honest, I don't think it's worth it. The feature is very minor and if you compile yourself you can either update everything, or just live without that display. I don't think it even qualifies as a defect, for that matter ;)
And cmake compile tests are a bit of a hassle, aren't they... like, you need an extra directory with an extra cmake file and whatnot...
If you really think it's worth it I'll take it as an opportunity and learn how it works, but I'd say it's not :)</pre>
</blockquote>
<p>On May 30th, 2013, 7:28 a.m. UTC, <b>Andreas Pakulat</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">I think you misunderstood a bit. Kate and its KTextEditor code can be build and installed these days from the git repository. They can be installed into a location other than the install-directory of kdelibs and still override the kdelibs-shipped katepart/ktexteditor. I'm using such a setup here and it allows me to ignore the fact that I have a 2 years old kdelibs installed and can't upgrade that at the moment. Compiling kdelibs from sources is not an option for me, thats simply too much effort. But I don't use the vi-mode either, so just wanted to clarify that these days there might be quite some users out there using latest-kate/kte with an older kdelibs.
I don't know where you got the impression that cmake compile tests need an extra directory, you can use try_compile with just a source file as well. Something like this with a bit of tweaking for the includedirs/libraries should work:
try_compile( HAS_EDITVIMODE ${CMAKE_OUTPUT_DIRECTORY} ${CMAKE_SOURCE_DIRECTORY}/testeditvimode.cpp
CMAKE_FLAGS "-DINCLUDE_DIRECTORIES=${KDE_INCLUDES}" "-DLINK_LIBRARIES=${KDE_LIBRARIES}" )</pre>
</blockquote>
</blockquote>
<pre style="margin-left: 1em; white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Ok, I'll submit a version which does this shortly.</pre>
<br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<p style="margin-top: 0;">On May 29th, 2013, 8:10 p.m. UTC, <b>Andreas Pakulat</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<table width="100%" border="0" bgcolor="white" style="border: 1px solid #C0C0C0; border-collapse: collapse; margin: 2px padding: 2px;">
<thead>
<tr>
<th colspan="4" bgcolor="#F0F0F0" style="border-bottom: 1px solid #C0C0C0; font-size: 9pt; padding: 4px 8px; text-align: left;">
<a href="http://git.reviewboard.kde.org/r/110713/diff/2/?file=146917#file146917line793" style="color: black; font-weight: bold; text-decoration: underline;">shell/textdocument.cpp</a>
<span style="font-weight: normal;">
(Diff revision 2)
</span>
</th>
</tr>
</thead>
<tbody>
<tr>
<th bgcolor="#b1ebb0" style="border-right: 1px solid #C0C0C0;" align="right"><font size="2"></font></th>
<td bgcolor="#c5ffc4" width="50%"><pre style="font-size: 8pt; line-height: 140%; margin: 0; "></pre></td>
<th bgcolor="#b1ebb0" style="border-left: 1px solid #C0C0C0; border-right: 1px solid #C0C0C0;" align="right"><font size="2">791</font></th>
<td bgcolor="#c5ffc4" width="50%"><pre style="font-size: 8pt; line-height: 140%; margin: 0; "> <span class="k">if</span> <span class="p">(</span> <span class="o">!</span> <span class="n">d</span><span class="o">-></span><span class="n">statusLabel</span> <span class="p">)</span> <span class="p">{</span></pre></td>
</tr>
</tbody>
</table>
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Did you see adymo's comment about there being some status-bar-space at the right end of the bottom button's? I'm not sure that'll look good/right, but maybe worth a try.</pre>
</blockquote>
<p>On May 29th, 2013, 9:43 p.m. UTC, <b>Sven Brauch</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Sorry, I don't know what you're referring to here. Which comment do you mean?</pre>
</blockquote>
<p>On May 30th, 2013, 7:28 a.m. UTC, <b>Andreas Pakulat</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">He replied on the mailinglist thread where we talked about the position of the vi-mode label. See http://mail.kde.org/pipermail/kdevelop-devel/2013-May/045402.html</pre>
</blockquote>
</blockquote>
<pre style="margin-left: 1em; white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">I guess this corner is meant? http://i.imgur.com/0bxH0bi.png
That is not going to work in my opinion, since the information displayed is per-view, and you might have multiple views. On the other hand, we're just displaying the line number for the active view anyways (probably not a good idea either)...
Still, it sounds like introducing trouble to me.</pre>
<br />
<p>- Sven</p>
<br />
<p>On May 29th, 2013, 9:43 p.m. UTC, Sven Brauch wrote:</p>
<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="8" style="background-image: url('http://git.reviewboard.kde.org/static/rb/images/review_request_box_top_bg.ab6f3b1072c9.png'); background-position: left top; background-repeat: repeat-x; border: 1px black solid;">
<tr>
<td>
<div>Review request for KDevelop.</div>
<div>By Sven Brauch.</div>
<p style="color: grey;"><i>Updated May 29, 2013, 9:43 p.m.</i></p>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Description </h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" style="border: 1px solid #b8b5a0">
<tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">The kate people recently merged the vi mode status bar into the main editor status bar (which makes sense). We don't show that bar though, so the vi mode bar is missing. This patch adds it back in, by adding a custom label to the view which displays the vi mode and file name. See the thread [1] where this was discussed on kwrite-devel.
I'm aware that this is not the most elegant code ever but it gets the job done.
______
[1] http://lists.kde.org/?l=kwrite-devel&m=136499004230520&w=2</pre>
</td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Testing </h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" style="border: 1px solid #b8b5a0">
<tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">seems to work ok, toggling vi mode, toggling mode inside vi mode (insert / normal etc) works</pre>
</td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Diffs</b> </h1>
<ul style="margin-left: 3em; padding-left: 0;">
<li>shell/textdocument.h <span style="color: grey">(1d31ad9)</span></li>
<li>shell/textdocument.cpp <span style="color: grey">(196dfaf)</span></li>
</ul>
<p><a href="http://git.reviewboard.kde.org/r/110713/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>