From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 34350@debbugs.gnu.org, vincent.belaiche@gmail.com
Subject: bug#34350: 27.0.50; ediff-revision broken with SVN backend + non ascii chars both in directory and in filename
Date: Fri, 8 Feb 2019 20:25:35 +0300 [thread overview]
Message-ID: <622e6df3-fb17-cf8a-a166-23fd1549a6c7@yandex.ru> (raw)
In-Reply-To: <83va1vr41l.fsf@gnu.org>
On 07.02.2019 18:50, Eli Zaretskii wrote:
> Any idea why it insists on disabling code-conversions?
This was well before my time, and the only people I remember messing
with these variables anywhere in VC ever since are you (for
Windows-related fixes) and Michael. So this might require some digging
with vc-annotate.
Also note that this affects two commands: one that returns the file
name, and another, its contents. I'm not sure what encoding 'git
cat-file blob' outputs in.
> In addition to producing undecoded buffer, these bindings have the
> adverse effect of forcing Emacs not to encode command-line arguments
> we pass to the VCS, which is the immediate cause for the current bug.
The adverse effect sounds like a separate bug.
next prev parent reply other threads:[~2019-02-08 17:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 19:52 bug#34350: 27.0.50; ediff-revision broken with SVN backend + non ascii chars both in directory and in filename Vincent Belaïche
2019-02-07 15:41 ` Eli Zaretskii
2019-02-07 22:27 ` Vincent Belaïche
2019-02-08 7:02 ` Eli Zaretskii
2019-02-07 15:50 ` Eli Zaretskii
2019-02-08 16:08 ` Stefan Monnier
2019-02-08 21:18 ` Eli Zaretskii
2019-02-08 21:50 ` Stefan Monnier
2019-02-08 22:10 ` Eli Zaretskii
2019-02-08 23:03 ` Stefan Monnier
2019-02-09 9:01 ` Eli Zaretskii
2019-02-09 13:12 ` Stefan Monnier
2019-02-09 13:42 ` Eli Zaretskii
2019-02-09 14:03 ` Stefan Monnier
2019-02-11 21:20 ` Vincent Belaïche
2019-02-11 22:00 ` Stefan Monnier
2019-02-08 17:25 ` Dmitry Gutov [this message]
2019-02-08 21:45 ` Eli Zaretskii
2019-02-09 7:58 ` Dmitry Gutov
2019-02-09 8:23 ` Eli Zaretskii
2019-02-10 19:52 ` Vincent Belaïche
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=622e6df3-fb17-cf8a-a166-23fd1549a6c7@yandex.ru \
--to=dgutov@yandex.ru \
--cc=34350@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=vincent.belaiche@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).