GNU bug report logs -
#44513
default value of file-name-coding-system
Previous Next
Reported by: Boruch Baum <boruch_baum <at> gmx.com>
Date: Sun, 8 Nov 2020 09:16:02 UTC
Severity: minor
Tags: notabug
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
Message #14 received at submit <at> debbugs.gnu.org (full text, mbox):
On 2020-11-08 13:29, Eli Zaretskii wrote:
> On November 8, 2020 11:15:50 AM GMT+02:00, Boruch Baum <boruch_baum <at> gmx.com> wrote:
> > Shouldn't emacs ship with the default value of variable
> > file-name-coding-system being equal to that of the default value of
> > default-file-name-coding-system?
> >
> > file-name-coding-system => nil
> > (default-value file-name-coding-system) => nil
> > default-file-name-coding-system => utf-8-unix
>
> These are 2 separate variables, see the doc string of default-file-name-coding-system. One is for the user to set, thus nil by default, the other is what Emacs thinks should be the OS default. They are separate because Unix filesystems traditionally treat file names as byte streams, without imposing any encoding restrictions on them.
I'm proposing that even the one that's 'for the user to set' should have
a sane default. I'm a user, and it never occurred to me I needed to set
that variable (among all the other emacs variables begging a
customization). What percentage of users do you think install emacs and
on their own initiative say, "Of course, I now need to set
file-name-coding-system". If so, maybe it should be part of the official
emacs tutorial (sarcasm)?
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
This bug report was last modified 4 years and 192 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.