git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Tommy Thorn <tommy-git@thorn.ws>, git@vger.kernel.org
Subject: Re: Bug in gitk - can post the window off screen
Date: Thu, 7 Feb 2008 10:56:19 +0100	[thread overview]
Message-ID: <200802071056.19370.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <20080207063020.GP24004@spearce.org>

torsdagen den 7 februari 2008 skrev Shawn O. Pearce:
> Tommy Thorn <tommy-git@thorn.ws> wrote:
> > Just a quick heads-up: I was running a dual screen setup with gitk on my 
> > 2nd monitor. When I later started gitk up without the 2nd monitor, the 
> > gitk window didn't appear. Given the time between the two sessions, it 
> > didn't occur to me what the problem was.
> > 
> > Gitk should probably validate the "set geometry(main)" variable against 
> > the current resolution.
> 
> Sad to say but this is a known issue with both gitk and git-gui.
> Both applications save the prior geometry and restore it during
> the next run, but neither validates the new geometry makes sense
> with the current available desktop space.  :-\

Seems KDE forces it back into visible space, but it is annoying that the 
gitk/git-gui windows do not come up on the same monitor as my cursor is on. 
Could we change it and save just size, just like "all other" apps?

-- robin

  reply	other threads:[~2008-02-07  9:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-07  6:16 Bug in gitk - can post the window off screen Tommy Thorn
2008-02-07  6:30 ` Shawn O. Pearce
2008-02-07  9:56   ` Robin Rosenberg [this message]
2008-02-07 10:10     ` Gerrit Pape
2008-02-23 11:37       ` [PATCH] gitk: don't save the geometry to rc file on exit Gerrit Pape
2008-02-23 12:52         ` Robin Rosenberg
2008-02-23 13:15           ` Jonathan del Strother
2008-02-23 22:49         ` Paul Mackerras
2008-02-24 15:44           ` Mark Levedahl
2008-02-24 18:21             ` Edgar Toernig
2008-03-06 12:17             ` Paul Mackerras
2008-03-06 12:59               ` Jonathan del Strother
2008-03-06 23:10                 ` Paul Mackerras
2008-03-07  3:03               ` Mark Levedahl
2008-03-07 11:11               ` martin f krafft
2008-03-08 11:11                 ` Paul Mackerras
2008-03-10 11:29                   ` martin f krafft
2008-03-10 13:17                   ` David Tweed
2008-02-25  8:07           ` martin f krafft
2008-02-25 12:09             ` Paul Mackerras
2008-02-25 12:24               ` martin f krafft
2008-02-25 13:35               ` Mark Levedahl
2008-02-25 14:15                 ` martin f krafft
2008-02-25 19:59                 ` Martin Langhoff
2008-02-25 23:08                   ` Robin Rosenberg
2008-02-26  2:15           ` A Large Angry SCM

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200802071056.19370.robin.rosenberg.lists@dewire.com \
    --to=robin.rosenberg.lists@dewire.com \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.org \
    --cc=tommy-git@thorn.ws \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).