From: Eli Zaretskii <eliz@gnu.org>
To: Andy Moreton <andrewjmoreton@gmail.com>
Cc: 51497@debbugs.gnu.org
Subject: bug#51497: 29.0.50; (vc-print-log) broken over TRAMP
Date: Sun, 07 Nov 2021 08:31:14 +0200 [thread overview]
Message-ID: <83k0hka34d.fsf@gnu.org> (raw)
In-Reply-To: <86r1btvsso.fsf@gmail.com> (message from Andy Moreton on Sat, 06 Nov 2021 22:11:03 +0000)
> From: Andy Moreton <andrewjmoreton@gmail.com>
> Date: Sat, 06 Nov 2021 22:11:03 +0000
>
> I missed the discussion in bug#39452 at the time, but while the solution
> was being worked on, I used advice to stub out the literal pathspec
> functions:
> (advice-add 'vc-git--literal-pathspec :override #'identity)
> (advice-add 'vc-git--literal-pathspecs :override #'identity)
>
> That workaround is still needed for me. Without that, nothing in vc-git
> works in my environment (64bit minw64 build on win10, using cygwin bash
> and git together with cygwin-mount.el from emacs wiki).
We need to understand why the original code doesn't work for you,
otherwise we cannot decide what to do about that issue. FWIW, Git
works for me on Windows from Emacs without any changes. But I don't
use the Cygwin Bash and cygwin-mount.el, which I always warned people
about. If you want to use Cygwin, why not also use Cygwin Emacs and
Git, and save yourself those troubles?
next prev parent reply other threads:[~2021-11-07 6:31 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-30 1:24 bug#51497: 29.0.50; (vc-print-log) broken over TRAMP dima
2021-10-30 12:48 ` Lars Ingebrigtsen
2021-10-30 13:21 ` Dmitry Gutov
2021-10-30 19:01 ` Dima Kogan
2021-10-31 0:56 ` Dmitry Gutov
2021-10-31 6:58 ` Dima Kogan
2021-10-31 8:16 ` Michael Albinus
2021-10-31 12:26 ` Dmitry Gutov
2021-10-31 16:05 ` Michael Albinus
2021-11-03 2:00 ` Dmitry Gutov
2021-11-03 17:09 ` Michael Albinus
2021-11-05 2:00 ` Dmitry Gutov
2021-11-03 2:03 ` Dmitry Gutov
2021-11-03 3:03 ` Dima Kogan
2021-11-03 12:06 ` Dmitry Gutov
2021-11-06 13:22 ` Dmitry Gutov
2021-11-06 15:51 ` Eli Zaretskii
2021-11-06 19:44 ` Dmitry Gutov
2021-11-06 19:52 ` Eli Zaretskii
2021-11-06 22:11 ` Andy Moreton
2021-11-06 22:21 ` Dmitry Gutov
2021-11-06 23:03 ` Andy Moreton
2021-11-07 0:11 ` Dmitry Gutov
2021-11-07 6:47 ` Eli Zaretskii
2021-11-07 10:43 ` Andy Moreton
2021-11-07 22:36 ` Dmitry Gutov
2021-11-08 12:49 ` Eli Zaretskii
2021-11-08 17:30 ` Dmitry Gutov
2021-11-08 18:18 ` Eli Zaretskii
2021-12-23 10:28 ` Lars Ingebrigtsen
2021-12-26 0:53 ` Dmitry Gutov
2021-12-27 1:36 ` Dmitry Gutov
2022-01-03 3:59 ` Dmitry Gutov
2022-01-03 21:15 ` Dima Kogan
2022-01-03 22:51 ` Dmitry Gutov
2022-01-04 3:28 ` Eli Zaretskii
2022-01-05 2:09 ` Dmitry Gutov
2022-01-21 13:50 ` Lars Ingebrigtsen
2022-01-21 14:11 ` Dmitry Gutov
2022-01-03 21:16 ` Andy Moreton
2021-11-07 6:43 ` Eli Zaretskii
2021-11-07 10:45 ` Andy Moreton
2021-11-07 6:31 ` Eli Zaretskii [this message]
2021-11-06 22:19 ` Dmitry Gutov
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=83k0hka34d.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51497@debbugs.gnu.org \
--cc=andrewjmoreton@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://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).