<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/lib/index.tcl, branch gitgui-0.13.0</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=gitgui-0.13.0</id>
<link rel='self' href='https://git.shady.money/git/atom?h=gitgui-0.13.0'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2010-01-28T01:13:52Z</updated>
<entry>
<title>git-gui: use themed tk widgets with Tk 8.5</title>
<updated>2010-01-28T01:13:52Z</updated>
<author>
<name>Pat Thoyts</name>
<email>patthoyts@users.sourceforge.net</email>
</author>
<published>2010-01-26T00:05:31Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=c80d7be5e1e0d110ea77cd41f658aabe5bcad0d8'/>
<id>urn:sha1:c80d7be5e1e0d110ea77cd41f658aabe5bcad0d8</id>
<content type='text'>
This patch enables the use of themed Tk widgets with Tk 8.5 and above.
These make a significant difference on Windows in making the
application appear native. On Windows and MacOSX ttk defaults to the
native look as much as possible. On X11 the user may select a theme
using the TkTheme XRDB resource class by adding an line to the
.Xresources file. The set of installed theme names is available using
the Tk command 'ttk::themes'. The default on X11 is similar to the current
un-themed style - a kind of thin bordered motif look.

A new git config variable 'gui.usettk' may be set to disable this if
the user prefers the classic Tk look. Using Tk 8.4 will also avoid the
use of themed widgets as these are only available since 8.5.

Some support is included for Tk 8.6 features (themed spinbox and native
font chooser for MacOSX and Windows).

Signed-off-by: Pat Thoyts &lt;patthoyts@users.sourceforge.net&gt;
Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;
</content>
</entry>
<entry>
<title>git-gui: handle really long error messages in updateindex.</title>
<updated>2010-01-23T22:22:28Z</updated>
<author>
<name>Pat Thoyts</name>
<email>patthoyts@users.sourceforge.net</email>
</author>
<published>2009-12-20T02:02:03Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=ea888f84bd6ebb7e944311d95251d28a3b547024'/>
<id>urn:sha1:ea888f84bd6ebb7e944311d95251d28a3b547024</id>
<content type='text'>
As reported to msysGit (bug #340) it is possible to get some very
long error messages when updating the index. The use of a label to
display this prevents scrolling the output. This patch replaces the
label with a scrollable text widget configured to look like a label.

Signed-off-by: Pat Thoyts &lt;patthoyts@users.sourceforge.net&gt;
Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;
</content>
</entry>
<entry>
<title>git-gui: Make Ctrl-T safe to use for conflicting files.</title>
<updated>2008-09-30T18:47:33Z</updated>
<author>
<name>Alexander Gavrilov</name>
<email>angavrilov@gmail.com</email>
</author>
<published>2008-09-30T08:12:16Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=0aea2842d9d556afa4a3e8120e465479ad7368ca'/>
<id>urn:sha1:0aea2842d9d556afa4a3e8120e465479ad7368ca</id>
<content type='text'>
A previous patch added a check for conflict markers, which
is done when the file is about to be staged due to a click
on the icon. However, pressing Ctrl-T still immediately
stages the file without confirmation. This patch fixes it.

The check requires a loaded diff, so staging multiple files
at once won't work if they are unmerged.

Signed-off-by: Alexander Gavrilov &lt;angavrilov@gmail.com&gt;
Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;
</content>
</entry>
<entry>
<title>git-gui: Support conflict states _U &amp; UT.</title>
<updated>2008-09-05T04:28:55Z</updated>
<author>
<name>Alexander Gavrilov</name>
<email>angavrilov@gmail.com</email>
</author>
<published>2008-08-30T21:00:49Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=ff515d81faa22f26b611ed7fd06a76d0c300ea39'/>
<id>urn:sha1:ff515d81faa22f26b611ed7fd06a76d0c300ea39</id>
<content type='text'>
Support _U (local deleted, remote modified) and
UT (file type changed in conflict) modes.

Note that 'file type changed' does not refer to
changes in the executable bit, instead it denotes
replacing a file with a link, or vice versa.

Signed-off-by: Alexander Gavrilov &lt;angavrilov@gmail.com&gt;
Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;
</content>
</entry>
<entry>
<title>git-gui: Mark forgotten strings for translation.</title>
<updated>2008-09-05T04:28:48Z</updated>
<author>
<name>Christian Stimming</name>
<email>stimming@tuhh.de</email>
</author>
<published>2008-09-04T09:50:53Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=700e560341edfe32242b6b5b3b380d6f945ec0e8'/>
<id>urn:sha1:700e560341edfe32242b6b5b3b380d6f945ec0e8</id>
<content type='text'>
Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;
</content>
</entry>
<entry>
<title>git-gui: Teach git gui about file type changes</title>
<updated>2008-08-25T04:36:17Z</updated>
<author>
<name>Gustaf Hendeby</name>
<email>hendeby@isy.liu.se</email>
</author>
<published>2008-08-22T20:10:27Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=e681cb7d6a00b4860c84bf8ca7b8d8dab366c9fc'/>
<id>urn:sha1:e681cb7d6a00b4860c84bf8ca7b8d8dab366c9fc</id>
<content type='text'>
Signed-off-by: Gustaf Hendeby &lt;hendeby@isy.liu.se&gt;
Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;
</content>
</entry>
<entry>
<title>git-gui: (i18n) Fix a bunch of still untranslated strings.</title>
<updated>2008-02-04T02:25:29Z</updated>
<author>
<name>Christian Stimming</name>
<email>stimming@tuhh.de</email>
</author>
<published>2008-02-02T09:20:17Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=5e6d7768e13088cc0082614fd106b327214fdc6d'/>
<id>urn:sha1:5e6d7768e13088cc0082614fd106b327214fdc6d</id>
<content type='text'>
Signed-off-by: Christian Stimming &lt;stimming@tuhh.de&gt;
Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;
</content>
</entry>
<entry>
<title>git-gui: Fix broken revert confirmation.</title>
<updated>2008-01-16T05:44:14Z</updated>
<author>
<name>Christian Stimming</name>
<email>stimming@tuhh.de</email>
</author>
<published>2008-01-08T20:21:15Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=d4544601513c9ab5a702d7815afcdf13014b06cc'/>
<id>urn:sha1:d4544601513c9ab5a702d7815afcdf13014b06cc</id>
<content type='text'>
I broke this extremely cool feature in 1ac17950,
but it is rather easy to fix this. Sorry for that.

Signed-off-by: Christian Stimming &lt;stimming@tuhh.de&gt;
Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;
</content>
</entry>
<entry>
<title>Merge branch 'maint'</title>
<updated>2007-10-23T22:50:19Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-10-23T22:50:19Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=f4e9996b77415707a20a139463c3e3782e2fa48f'/>
<id>urn:sha1:f4e9996b77415707a20a139463c3e3782e2fa48f</id>
<content type='text'>
* maint:
  git-gui: Make sure we get errors from git-update-index

Conflicts:

	lib/index.tcl
</content>
</entry>
<entry>
<title>git-gui: Make sure we get errors from git-update-index</title>
<updated>2007-10-23T22:49:27Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-10-23T20:55:32Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=d4e890e5de1ea7107d8d1b4134ab0144bbf27b8c'/>
<id>urn:sha1:d4e890e5de1ea7107d8d1b4134ab0144bbf27b8c</id>
<content type='text'>
I'm seeing a lot of silent failures from git-update-index on
Windows and this is leaving the index.lock file intact, which
means users are later unable to perform additional operations.

When the index is locked behind our back and we are unable to
use it we may need to allow the user to delete the index lock
and try again.  However our UI state is probably not currect
as we have assumed that some changes were applied but none of
them actually did.  A rescan is the easiest (in code anyway)
solution to correct our UI to show what the index really has
(or doesn't have).

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;
</content>
</entry>
</feed>
