unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Bartosz Kaczyński" <bkaczynski@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 70004@debbugs.gnu.org
Subject: bug#70004: 30.0.50; vc-dir-mark-all-files doesn't work in *vc-dir* buffer
Date: Fri, 29 Mar 2024 11:57:24 +0000	[thread overview]
Message-ID: <875xx5w8rf.fsf@posteo.net> (raw)
In-Reply-To: <867chnipgz.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 27 Mar 2024 18:55:40 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> So can you try figuring out why it doesn't work correctly in that
> repository?  What is different about that repository?

Ok, I found the dependency why it sometimes works and sometimes
doesn't. It's about the point position when changes affect files in
different directories. If the point is located in a different place than
the line where the files are, for example, a line that points to a
directory - then marking all files with the <M> key doesn't include all
files.

--8<---------------cut here---------------start------------->8---
VC backend : Git
Working dir: ~/.emacs.d/
Branch     : main
Tracking   : origin/main
Remote     : git@myremote.git
Stash      : Nothing stashed

                         ./
     edited              init.el
                         lisp/
     edited              lisp/init-org.el
--8<---------------cut here---------------end--------------->8---

Unlike, the <U> key, which unmark all files regardless of position.

Rather, it has nothing to do with the repository itself or the backend.





  reply	other threads:[~2024-03-29 11:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-26 14:17 bug#70004: 30.0.50; vc-dir-mark-all-files doesn't work in *vc-dir* buffer Bartosz Kaczyński
2024-03-26 16:41 ` Eli Zaretskii
2024-03-27 16:07   ` Bartosz Kaczyński
2024-03-27 16:55     ` Eli Zaretskii
2024-03-29 11:57       ` Bartosz Kaczyński [this message]
2024-03-31  9:17         ` Eli Zaretskii
2024-04-02 16:31           ` Bartosz Kaczyński
2024-04-02 16:40             ` Eli Zaretskii

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: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=875xx5w8rf.fsf@posteo.net \
    --to=bkaczynski@posteo.net \
    --cc=70004@debbugs.gnu.org \
    --cc=eliz@gnu.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://git.savannah.gnu.org/cgit/emacs.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).