git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: Dan Zwell <dzwell@zwell.net>, Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] git-gui: Update russian translation
Date: Wed, 12 Aug 2009 08:40:17 -0700	[thread overview]
Message-ID: <20090812154016.GG1033@spearce.org> (raw)
In-Reply-To: <20090812152409.GA5407@blimp.localdomain>

Alex Riesen <raa.lkml@gmail.com> wrote:
> Shawn O. Pearce, Wed, Aug 12, 2009 16:43:45 +0200:
> > Dan Zwell <dzwell@zwell.net> wrote:
> > > When there is a large number of new or modified files,
> > > "display_all_files" takes a long time, and git-gui appears to
> > > hang. This change limits the number of files that are displayed.
> > > This limit can be set as gui.maxfilesdisplayed, and is
> > > 5000 by default.
> > >
> > > A warning is shown when the list of files is truncated.
> > 
> > Thanks, applied.
> 
> But now, when I really think about the change, it looks useless.
> What has the _number_ of files has to do with the files you actually
> have to handle? As the sorting of the file list cannot be changed (and
> it wouldn't be a big help anyway), you have no chance to get to your
> file if it happens to be past the limit!
> 
> Wouldn't a pathname/glob filter in the command-line (or file/path
> selection dialog) to limit the scope be more appropriate and useful?
> And have the file list reading to happen in background, as gitk does?

Good point.  I suspect the problem wasn't so much with Tcl doing the
list processing as it was with Tk actually creating the underlying
icons and stuff for each file name.  But with the list clipped,
you are right, you are basically SOL.  You can't do much beyond
dropping back to the CLI and using the CLI tools.

IMHO, if we aren't going to handle 20k file names, we should at least
punt and tell the user we aren't going to handle 20k file names,
rather than just play Outlook wannabe and lockup the entire UI until
the user gets bored and kill -9's us.  So this patch is better than
nothing, it at least lets the user know we have given up on them.

-- 
Shawn.

  reply	other threads:[~2009-08-12 15:40 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30 20:37 [PATCH] Limited git-gui to displaying 5000 new files Dan Zwell
2009-08-10 15:38 ` Shawn O. Pearce
2009-08-10 17:06   ` Alex Riesen
2009-08-10 17:08     ` Shawn O. Pearce
2009-08-10 15:15       ` Dan Zwell
2009-08-11 18:23   ` [PATCH] Limit git-gui to display a maximum number of files Dan Zwell
2009-08-11 20:29     ` Shawn O. Pearce
2009-08-11 18:50       ` Dan Zwell
2009-08-12 14:43         ` Shawn O. Pearce
2009-08-12 15:24           ` [PATCH] git-gui: Update russian translation Alex Riesen
2009-08-12 15:40             ` Shawn O. Pearce [this message]
2009-08-12 15:51               ` Dan Zwell
  -- strict thread matches above, loose matches on Subject: below --
2020-11-06 18:49 [PATCH] git-gui: update Russian translation Dimitriy Ryazantcev
2020-11-18 11:02 ` Dimitriy
2020-11-18 12:28   ` Pratyush Yadav
2020-11-18 15:27     ` Dimitriy
2020-11-18 17:43       ` Pratyush Yadav
2020-12-01 19:24 ` Pratyush Yadav
     [not found] <1444730020-12292-1-git-send-email-dimitriy.ryazantcev@gmail.com>
     [not found] ` <1444730020-12292-2-git-send-email-dimitriy.ryazantcev@gmail.com>
2015-10-14 10:44   ` [PATCH] git-gui: Update " Pat Thoyts
2015-10-12 11:41 Dimitriy Ryazantcev
2015-10-12 11:41 ` Dimitriy Ryazantcev
2011-01-19 10:48 [PATCH 2/3] git-gui: spelling fixes in russian translation Dmitry Potapov
2011-01-19 21:01 ` [PATCH] git-gui: update " Alex Riesen
2011-01-24 23:57   ` Pat Thoyts
2011-01-25  0:34     ` Junio C Hamano
2011-01-27 11:39       ` Pat Thoyts
2008-03-14 13:03 [PATCH] Update Japanese translation しらいしななこ
2008-03-14 22:25 ` [PATCH] git-gui: update russian translation Alex Riesen

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=20090812154016.GG1033@spearce.org \
    --to=spearce@spearce.org \
    --cc=dzwell@zwell.net \
    --cc=git@vger.kernel.org \
    --cc=raa.lkml@gmail.com \
    /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).