From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: dgutov@yandex.ru, 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, 08 Feb 2019 23:18:42 +0200 [thread overview]
Message-ID: <83h8deou6l.fsf@gnu.org> (raw)
In-Reply-To: <jwvpns2tgh3.fsf-monnier+emacsbugs@gnu.org> (message from Stefan Monnier on Fri, 08 Feb 2019 11:08:36 -0500)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Dmitry Gutov <dgutov@yandex.ru>, 34350@debbugs.gnu.org, vincent.belaiche@gmail.com
> Date: Fri, 08 Feb 2019 11:08:36 -0500
>
> I think intuitively, in terms of encoding for the file's contents the
> backends should always return a byte-sequence (i.e. with no-conversion)
> and the front-end should then decide how to decode it (e.g., obeying
> the -*- coding -*- cookie and such).
Why do we need to leave this to the front end? It's a waste of cycles
to do decoding manually in Lisp, and it also pushes this obscure art
to application levels, where many Lisp programmers won't know how to
DTRT.
IMO, it's the other way around: by default the back-end should not
insist on any encoding, except where the VCS requires it, and it
should always by default decode the stuff it returns. The front end
should disable code conversions when needed, and the back-end should
honor that. This will mostly do TRT, because in the vast majority of
cases users do want eventually to have the stuff decoded, the number
of cases where we want the contrary is minuscule.
VC is just a fancy way of visiting files, so it should normally do the
same, i.e. decode.
next prev parent reply other threads:[~2019-02-08 21:18 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h8deou6l.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34350@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.