<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/lib, branch gitgui-0.8.4</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=gitgui-0.8.4</id>
<link rel='self' href='https://git.shady.money/git/atom?h=gitgui-0.8.4'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2007-10-21T00:42:01Z</updated>
<entry>
<title>git-gui: Don't display CR within console windows</title>
<updated>2007-10-21T00:42:01Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-10-21T00:42:01Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=bbbadf6e58f72ac6bf739d2a1109cbd872eb1083'/>
<id>urn:sha1:bbbadf6e58f72ac6bf739d2a1109cbd872eb1083</id>
<content type='text'>
Git progress bars from tools like git-push and git-fetch use CR
to skip back to the start of the current line and redraw it with
an updated progress.  We were doing this in our Tk widget but had
failed to skip the CR, which Tk doesn't draw well.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;
</content>
</entry>
<entry>
<title>git-gui: Handle progress bars from newer gits</title>
<updated>2007-10-21T00:36:27Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-10-20T18:16:15Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=bea6878be2fb73e50407f93f2bcd71b961510c19'/>
<id>urn:sha1:bea6878be2fb73e50407f93f2bcd71b961510c19</id>
<content type='text'>
Post Git 1.5.3 a new style progress bar has been introduced that
uses only one line rather than two.  The formatting of the completed
and total section is also slightly different so we must adjust our
regexp to match.  Unfortunately both styles are in active use by
different versions of Git so we need to look for both.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;
</content>
</entry>
<entry>
<title>git-gui: Correctly report failures from git-write-tree</title>
<updated>2007-10-20T05:42:01Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-10-20T05:42:01Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=8af52d7a83a78c5f3a60d5bd5099a5073655339a'/>
<id>urn:sha1:8af52d7a83a78c5f3a60d5bd5099a5073655339a</id>
<content type='text'>
If git-write-tree fails (such as if the index file is currently
locked and it wants to write to it) we were not getting the error
message as $tree_id was always the empty string so we shortcut
through the catch and never got the output from stderr.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;
</content>
</entry>
<entry>
<title>git-gui: Disable native platform text selection in "lists"</title>
<updated>2007-09-17T03:12:19Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-09-17T03:12:19Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=3849bfba84fb5b0e9d46920f62105b4e1dd97e63'/>
<id>urn:sha1:3849bfba84fb5b0e9d46920f62105b4e1dd97e63</id>
<content type='text'>
Sometimes we use a Tk text widget as though it were a listbox.
This happens typically when we want to show an icon to the left
of the text label or just when a text widget is generally a better
choice then the native listbox widget.

In these cases if we want the user to have control over the selection
we implement our own "in_sel" tag that shows the selected region
and we perform our own selection management in the background
via keybindings and mouse bindings.  In such uses we don't want
the user to be able to activate the native platform selection by
dragging their mouse through the text widget.  Doing so creates a
very confusing display and the user is left wondering what it may
mean to have two different types of selection in the same widget.

Tk doesn't allow us to delete the "sel" tag that it uses internally
to manage the native selection but it will allow us to make it
invisible by setting the tag to have the same display properties
as unselected text.  So long as we don't actually use the "sel"
tag for anything in code its effectively invisible.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;</content>
</entry>
<entry>
<title>git-gui: Paper bag fix "Commit-&gt;Revert" format arguments</title>
<updated>2007-09-14T00:08:53Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-09-14T00:08:53Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=55bad4f096b1f18eec94169c864c39bf0abda1db'/>
<id>urn:sha1:55bad4f096b1f18eec94169c864c39bf0abda1db</id>
<content type='text'>
The recent bug fix to correctly handle filenames with %s (or any
other valid Tcl format specifier) missed a \ on this line and
caused the remaining format arguments to not be supplied when we
updated the status bar.  This caused a Tcl error anytime the user
was trying to perform a file revert.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;</content>
</entry>
<entry>
<title>git-gui: Font chooser to handle a large number of font families</title>
<updated>2007-09-13T23:07:46Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-09-13T23:07:46Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=afe2098ddd3e21d1d1afc428d3c8d91f37b01692'/>
<id>urn:sha1:afe2098ddd3e21d1d1afc428d3c8d91f37b01692</id>
<content type='text'>
Simon Sasburg noticed that on X11 if there are more fonts than can
fit in the height of the screen Tk's native tk_optionMenu does not
offer scroll arrows to the user and it is not possible to review
all choices or to select those that are off-screen.  On Mac OS X
the tk_optionMenu works properly but is awkward to navigate if the
list is long.

This is a rewrite of our font selection by providing a new modal
dialog that the user can launch from the git-gui Options panel.
The dialog offers the user a scrolling list of fonts in a pane.
An example text shows the user what the font looks like at the size
they have selected.  But I have to admit the example pane is less
than ideal.  For example in the case of our diff font we really
should show the user an example diff complete with our native diff
syntax coloring.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;
Acked-by: Simon Sasburg &lt;simon.sasburg@gmail.com&gt;</content>
</entry>
<entry>
<title>git-gui: Assume untracked directories are Git submodules</title>
<updated>2007-09-10T00:39:42Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-09-10T00:13:10Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=3b9dfde3d636aeb961318d41b3ab59f72414d010'/>
<id>urn:sha1:3b9dfde3d636aeb961318d41b3ab59f72414d010</id>
<content type='text'>
If `git ls-files --others` returned us the name of a directory then
it is because Git has decided that this directory itself contains a
valid Git repository and its files shouldn't be listed as untracked
for this repository.

In such a case we should label the object as a Git repository and
not just as a directory.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;
</content>
</entry>
<entry>
<title>git-gui: handle "deleted symlink" diff marker</title>
<updated>2007-09-09T23:47:26Z</updated>
<author>
<name>Michele Ballabio</name>
<email>barra_cuda@katamail.com</email>
</author>
<published>2007-09-09T19:09:07Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=4ed1a190d09c7d6a248038edb11addda77af7550'/>
<id>urn:sha1:4ed1a190d09c7d6a248038edb11addda77af7550</id>
<content type='text'>
Signed-off-by: Michele Ballabio &lt;barra_cuda@katamail.com&gt;
Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;
</content>
</entry>
<entry>
<title>git-gui: show unstaged symlinks in diff viewer</title>
<updated>2007-09-09T23:47:22Z</updated>
<author>
<name>Michele Ballabio</name>
<email>barra_cuda@katamail.com</email>
</author>
<published>2007-09-09T19:04:45Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=2d19f8e921a1cdc562783814747819b0d5a12641'/>
<id>urn:sha1:2d19f8e921a1cdc562783814747819b0d5a12641</id>
<content type='text'>
git-gui has a minor problem with regards to symlinks that point
to directories.

	git init
	mkdir realdir
	ln -s realdir linkdir
	git gui

Now clicking on file names in the "unstaged changes" window,
there's a problem coming from the "linkdir" symlink: git-gui
complains with

	error reading "file4": illegal operation on a directory

...even though git-gui can add that same symlink to the index just
fine.

This patch fix this by adding a check.

[sp: Minor fix to use {link} instead of "link" in condition
     and to only open the path if it is not a symlink.]

Signed-off-by: Michele Ballabio &lt;barra_cuda@katamail.com&gt;
Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;
</content>
</entry>
<entry>
<title>git-gui: lib/index.tcl: handle files with % in the filename properly</title>
<updated>2007-09-09T03:06:26Z</updated>
<author>
<name>Gerrit Pape</name>
<email>pape@smarden.org</email>
</author>
<published>2007-09-07T17:16:59Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=0b883ab30c869c4f22a19e49aedc1604d335cd91'/>
<id>urn:sha1:0b883ab30c869c4f22a19e49aedc1604d335cd91</id>
<content type='text'>
Steps to reproduce the bug:

 $ mkdir repo &amp;&amp; cd repo &amp;&amp; git init
 Initialized empty Git repository in .git/
 $ touch 'foo%3Fsuite'
 $ git-gui

Then click on the 'foo%3Fsuite' icon to include it in a changeset, a
popup comes with:
'Error: bad field specifier "F"'

Vincent Danjean noticed the problem and also suggested the fix, reported
through
 http://bugs.debian.org/441167

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