<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git, branch gitgui-0.8.3</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.3</id>
<link rel='self' href='https://git.shady.money/git/atom?h=gitgui-0.8.3'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2007-09-17T03:12:19Z</updated>
<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: Provide 'uninstall' Makefile target to undo an installation</title>
<updated>2007-09-14T00:02:39Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-09-13T23:50:35Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=042f53c569c92b40e63c6993c8998d2aac22e383'/>
<id>urn:sha1:042f53c569c92b40e63c6993c8998d2aac22e383</id>
<content type='text'>
Several users have requested a "make uninstall" target be provided
in the stock git-gui Makefile so that they can undo an install
if git-gui goes to the wrong place during the initial install,
or if they are unhappy with the tool and want to remove it from
their system.

We currently assume that the complete set of files we need to delete
are those defined by our Makefile and current source directory.
This could differ from what the user actually has installed if they
installed one version then attempt to use another to perform the
uninstall.  Right now I'm just going to say that is "pilot error".
Users should uninstall git-gui using the same version of source
that they used to make the installation.  Perhaps in the future we
could read tclIndex and base our uninstall decisions on its contents.

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: Make backporting changes from i18n version easier</title>
<updated>2007-09-13T23:04:14Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-09-13T23:04:14Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=e7034d66ecd9c16ae8bd8d331fc41efc48e925f1'/>
<id>urn:sha1:e7034d66ecd9c16ae8bd8d331fc41efc48e925f1</id>
<content type='text'>
This is a very trivial hack to define a global mc procedure that
does not actually perform i18n translations on its input strings.
By declaring an mc procedure here in our maint version of git-gui
we can take patches that are intended for the latest development
version of git-gui and easily backport them without needing to
tweak the mc calls first.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;</content>
</entry>
<entry>
<title>git-gui: Don't delete send on Windows as it doesn't exist</title>
<updated>2007-09-11T22:57:18Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-09-11T17:37:45Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=63c4024ff080430004967fa27b8af8fe243e2ea3'/>
<id>urn:sha1:63c4024ff080430004967fa27b8af8fe243e2ea3</id>
<content type='text'>
The Windows port of Tk does not have the send command so we
cannot delete it from our global namespace, but the Mac OS
X and X11 ports do have it.  Switching this delete attempt
into a catch makes send go away, or stay away.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;
</content>
</entry>
<entry>
<title>git-gui: Trim trailing slashes from untracked submodule names</title>
<updated>2007-09-10T00:39:47Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-09-10T00:38:05Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=8938410189315979255c1dfcc3c0b7a4bf9953e5'/>
<id>urn:sha1:8938410189315979255c1dfcc3c0b7a4bf9953e5</id>
<content type='text'>
Oddly enough `git ls-files --others` supplies us the name of an
untracked submodule by including the trailing slash but that
same git version will not accept the name with a trailing slash
through `git update-index --stdin`.  Stripping off that final
slash character before loading it into our file lists allows
git-gui to stage changes to submodules just like any other file.

This change should give git-gui users some basic submodule support,
but it is strictly at the plumbing level as we do not actually know
about calling the git-submodule porcelain that is a recent addition
to git 1.5.3.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&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>
</feed>
