When typing in the Search field, select the current search result (so
that it gets highlighted in orange). This makes it easier to understand
what will happen if you then type Ctrl-S.
Signed-off-by: Stefan Haller ste...@haller-berlin.de
---
gitk | 5 -
1 file changed, 4 insertions(+), 1
Here's something that has been bugging me for a long time: when using
the incremental search feature, it's hard to tell what happens when
clicking the Search button (or type Ctrl-S) repeatedly. It does have
the concept of a current search hit, and Ctrl-S advances to the next
one; however, you
On Mac, the back and forward buttons show an empty rectange instead of
a grayed-out arrow when they are disabled. The reason is a Tk bug on Mac
that causes disabled images not to draw correctly (not to draw at all,
that is); see
On 09/21/2012 10:49 PM, Jeff King wrote:
Oh. It sounds like setting $SHELL to zsh is really the problem, then. If
it is not Bourne-compatible when called as zsh, then it really should
be called in a way that turns on compatibility mode (bash will do this
when called as sh, but you can also do
The loop can be triggered with git diff-tree --graph commit where
the commit is a non-merge. It goes like this
- graph_show_commit
- graph_next_line
- graph_output_padding_line
The last function quits because graph-commit is NULL, but
graph_next_line() does not return shown, so the loop in
On Sat, Sep 22, 2012 at 03:03:58PM +0200, Stefano Lattarini wrote:
On 09/21/2012 10:49 PM, Jeff King wrote:
Oh. It sounds like setting $SHELL to zsh is really the problem, then. If
it is not Bourne-compatible when called as zsh, then it really should
be called in a way that turns on
Hi,
Also, there are many academic institutions, and at least some might
be happy to host an event like this (I'm thinking especially of the Zuse
institute). I had offered to help with hooking up with them several
weeks ago already. So, it's really just a matter of communication.
Yep.
On 09/22/2012 07:47 PM, Jeff King wrote:
On Sat, Sep 22, 2012 at 03:03:58PM +0200, Stefano Lattarini wrote:
On 09/21/2012 10:49 PM, Jeff King wrote:
Oh. It sounds like setting $SHELL to zsh is really the problem, then. If
it is not Bourne-compatible when called as zsh, then it really should
Ramkumar Ramachandra artag...@gmail.com writes:
Here's a patch.
-- 8 --
From: Ramkumar Ramachandra artag...@gmail.com
Date: Sat, 22 Sep 2012 10:25:10 +0530
Subject: [PATCH] test-lib: do not trust $SHELL
Do not trust $SHELL to be a bourne-compatible shell. Instead, use the
Makefile
Michael J Gruber g...@drmicha.warpmail.net writes:
On my mental scratch pad (yeah, that's where the bald spots are) I have
the following more general idea to enhance the revision parser:
--limit-run=script::
--run=script:::
These options run the script `script` on each revision that is
As I know how hard translations can be, esp. with that much technical terms
inside, I'm usually expecting _not_ to yield the same result when translating
a software's translation back to English.
However, git-rebase just threw these two sentences at me (And though i know
their meaning, i
On Wed, Sep 19, 2012 at 7:35 PM, Felipe Contreras
felipe.contre...@gmail.com wrote:
Hi,
On Wed, Sep 14, 2011 at 7:39 PM, Jakub Narebski jna...@gmail.com wrote:
P.S. Would you be interested in running the next survey?
I haven't seen any news regarding the 2012 survey. I'm interested in
12 matches
Mail list logo
