git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Julliard <julliard@winehq.org>
To: "Gábor Melis" <mega@retes.hu>
Cc: git@vger.kernel.org
Subject: Re: git emacs mode patch
Date: Sat, 17 Mar 2007 11:04:25 +0100	[thread overview]
Message-ID: <87y7lwxk2e.fsf@wine.dyndns.org> (raw)
In-Reply-To: <200703151403.56552.mega@retes.hu> (Gábor Melis's message of "Thu\, 15 Mar 2007 14\:03\:56 +0100")

Gábor Melis <mega@retes.hu> writes:

> +(defcustom git-hide-unknown t
> +  "Hide files with unknown status by default."
> +  :group 'git
> +  :type 'boolean)

This one should default to nil for backwards compatibility.

> @@ -1017,15 +1028,18 @@ and returns the process output as a string."
>        (with-temp-buffer
>          (git-run-command t nil "diff-index" "-z" "-M" "HEAD")
>          (git-parse-status status)))
> +    (unless (member 'up-to-date hidden-statuses)
>        (with-temp-buffer
> -        (git-run-command t nil "ls-files" "-z" "-u")
> -        (git-parse-ls-unmerged status))
> +        (git-run-command t nil "ls-files" "-z" "-t")
> +        (git-parse-ls-files status 'unknown)))
> +    (unless (member 'unknown hidden-statuses)

Why are you removing the ls-files -u?  This will break the detection
of unmerged files.

> +(defun git-toggle-up-to-date ()
> +  (interactive)
> +  (if (member 'up-to-date hidden-statuses)
> +      (setq hidden-statuses (remove 'up-to-date hidden-statuses))
> +    (push 'up-to-date hidden-statuses))

The status should be named 'uptodate instead of 'up-to-date since
that's what's used for individual files. Having two different
spellings for the same word would be very confusing.

-- 
Alexandre Julliard
julliard@winehq.org

  reply	other threads:[~2007-03-17 10:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-15 13:03 git emacs mode patch Gábor Melis
2007-03-17 10:04 ` Alexandre Julliard [this message]
2007-03-25 17:03   ` Gábor Melis
2007-03-26 10:02     ` Alexandre Julliard

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=87y7lwxk2e.fsf@wine.dyndns.org \
    --to=julliard@winehq.org \
    --cc=git@vger.kernel.org \
    --cc=mega@retes.hu \
    /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).