From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: rms@gnu.org, 65049@debbugs.gnu.org
Subject: bug#65049: Minor update to the repro steps
Date: Thu, 31 Aug 2023 09:00:26 +0300 [thread overview]
Message-ID: <8334zzg39h.fsf@gnu.org> (raw)
In-Reply-To: <28a6239a-1c1c-f863-babd-e99abf56282d@gutov.dev> (message from Dmitry Gutov on Thu, 31 Aug 2023 05:14:47 +0300)
> Date: Thu, 31 Aug 2023 05:14:47 +0300
> Cc: 65049@debbugs.gnu.org
> From: Dmitry Gutov <dmitry@gutov.dev>
>
> On 31/08/2023 05:07, Richard Stallman wrote:
> > What effect would the proposed change have that I as a user of VC mode
> > notice? I use it with CVS and with git.
>
> If you have files in that repository which use a coding system that
> doesn't match your configured language environment, it's possible that
> the output of vc-diff might look inappropriate (decoded incorrectly).
Yes, but I think the existing code has the same issue. IOW, the
situation where a VC fileset includes files with different encodings,
and the diffs of the entire fileset are shown in Emacs, is not well
supported by the Emacs decoding infrastructure, because that assumes
there's a single coding-system suitable to decode the entire text
shown in a buffer, and thus makes decisions about the encoding based
on sampling a small initial portion of the text.
Btw, the CVS case is slightly less problematic here, since in CVS one
usually looks at diffs of separate files, and the whole idea of VC
fileset is quite artificial, since CVS itself doesn't really support
multiple-file changesets, it treats each file separately.
next prev parent reply other threads:[~2023-08-31 6:00 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 7:50 bug#65049: 29.1; vc-do-command fails in windows emacs 29.1 Maxim Kim
2023-08-04 8:02 ` bug#65049: Minor update to the repro steps Maxim Kim
2023-08-04 11:05 ` Eli Zaretskii
2023-08-04 11:24 ` Maxim Kim
2023-08-04 17:56 ` Juri Linkov
2023-08-06 23:04 ` Maxim Kim
2023-08-07 1:09 ` Maxim Kim
2023-08-07 16:24 ` Eli Zaretskii
2023-08-07 23:17 ` Maxim Kim
2023-08-20 16:49 ` Juri Linkov
2023-08-20 18:25 ` Eli Zaretskii
2023-08-21 6:53 ` Juri Linkov
2023-08-21 11:00 ` Eli Zaretskii
2023-08-21 11:39 ` Maxim Kim
2023-08-21 12:18 ` Eli Zaretskii
2023-08-21 23:10 ` Maxim Kim
2023-08-22 12:52 ` Eli Zaretskii
2023-08-22 13:12 ` Maxim Kim
2023-08-22 13:17 ` Eli Zaretskii
2023-08-22 23:43 ` Maxim Kim
2023-08-23 4:28 ` Maxim Kim
2023-08-23 16:21 ` Eli Zaretskii
2023-08-23 17:42 ` Juri Linkov
2023-08-23 18:43 ` Eli Zaretskii
2023-08-23 20:13 ` Dmitry Gutov
2023-08-24 4:54 ` Eli Zaretskii
2023-08-24 21:06 ` Dmitry Gutov
2023-08-24 21:35 ` Dmitry Gutov
2023-08-24 21:44 ` Dmitry Gutov
2023-08-25 6:18 ` Eli Zaretskii
2023-08-26 0:45 ` Dmitry Gutov
2023-08-26 8:50 ` Eli Zaretskii
2023-08-27 1:14 ` Dmitry Gutov
2023-08-27 5:36 ` Eli Zaretskii
2023-08-27 22:32 ` Dmitry Gutov
2023-08-28 12:12 ` Eli Zaretskii
2023-08-28 13:45 ` Dmitry Gutov
2023-08-28 16:12 ` Eli Zaretskii
2023-08-28 16:51 ` Dmitry Gutov
2023-08-28 16:57 ` Eli Zaretskii
2023-08-28 17:39 ` Dmitry Gutov
2023-08-28 18:26 ` Eli Zaretskii
2023-08-31 2:07 ` Richard Stallman
2023-08-31 2:14 ` Dmitry Gutov
2023-08-31 6:00 ` Eli Zaretskii [this message]
2023-08-23 23:46 ` Maxim Kim
2024-10-02 17:45 ` bug#65049: 29.1; vc-do-command fails in windows emacs 29.1 Sebastián Monía
2024-10-02 18:51 ` Eli Zaretskii
2024-10-02 21:32 ` 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=8334zzg39h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65049@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--cc=rms@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).