From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Gerrit Pape <pape@smarden.org>
Cc: git@vger.kernel.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] gitk: don't save the geometry to rc file on exit
Date: Sat, 23 Feb 2008 13:52:36 +0100 [thread overview]
Message-ID: <200802231352.37934.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <20080223113759.12854.qmail@6a8737aa4695b2.315fe32.mid.smarden.org>
lördagen den 23 februari 2008 skrev Gerrit Pape:
> Saving the geometry can cause several inconveniences, e.g. when using a
> temporary dual screen setup, or sharing ~/.gitk between multiple
> systems. Additionally it can be argued that window placement and sizing
> are the tasks of the window manager. So don't do that anymore.
Shouldn't the restoring code also be dropped then?
Other than that, I agree. The Gitk current behaviour wrt dual screens
is really inconvenient.
-- robin
next prev parent reply other threads:[~2008-02-23 12:53 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
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 [this message]
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=200802231352.37934.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=git@vger.kernel.org \
--cc=pape@smarden.org \
--cc=paulus@samba.org \
/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).