git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: git@vger.kernel.org
Subject: Re: What's new in git-gui.git
Date: Tue, 29 May 2007 00:11:08 -0400	[thread overview]
Message-ID: <20070529041108.GG7044@spearce.org> (raw)
In-Reply-To: <20070528224949.GC7044@spearce.org>

"Shawn O. Pearce" <spearce@spearce.org> wrote:
> --- Roadmap ---
> 
> Looking ahead, I'd like to see some improvement in the following
> areas.  It would be nice if some Tcl/Tk-minded individuals were
> willing to dive and help.  ;-)

I also want to get file change notification integrated into git-gui.
Basic idea is, if you edit a file in your editor of choice, git-gui
should notice it right away, without waiting for you to press the
damn Rescan button.

On Windows the only thing that actually works there (aside from
drawing lots and lots of blue pixels) is a fancy little file
monitoring API.  That actually works quite well.  Nothing else on
that OS works of course, but it will tell you when a file changes.
NT 4.0 and later only... ;-)

Apparently the Linux folks have this new fangled inotify thing
that is also good at telling applications about changed files.
It seems the hg folks are using it to speed up "hg status" by
having a background daemon keep track of which files are dirty,
and which aren't.

So I'm likely to want to try to implement something like this for
core Git and for git-gui, but my primary development system is Mac
OS X, where the BSD gods have only given us kqueue() and all its
warts... (it is basically useless for this task of monitoring a
"huge" tree like git.git, Mozilla.git need not apply).

-- 
Shawn.

  reply	other threads:[~2007-05-29  4:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-28 22:49 What's new in git-gui.git Shawn O. Pearce
2007-05-29  4:11 ` Shawn O. Pearce [this message]
2007-05-29  8:12   ` Alex Riesen
2007-05-29 10:59   ` Johannes Schindelin
2007-05-30  2:39     ` Shawn O. Pearce
2007-05-29 11:18   ` Petr Baudis
2007-05-30  2:34     ` Shawn O. Pearce
2007-05-29  7:46 ` Johannes Sixt

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=20070529041108.GG7044@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).