From: Eli Zaretskii <eliz@gnu.org>
To: Andy Moreton <andrewjmoreton@gmail.com>
Cc: 21780@debbugs.gnu.org
Subject: bug#21780: 25.0.50; Saving *Help* results in bad encoding because of curly quotes
Date: Sat, 31 Oct 2015 09:28:11 +0200 [thread overview]
Message-ID: <83a8qzzed0.fsf@gnu.org> (raw)
In-Reply-To: <86bnbgot1t.fsf@gmail.com>
> From: Andy Moreton <andrewjmoreton@gmail.com>
> Date: Fri, 30 Oct 2015 23:06:22 +0000
>
> On Fri 30 Oct 2015, Eli Zaretskii wrote:
>
> >> Date: Fri, 30 Oct 2015 22:50:57 +0200
> >> From: Eli Zaretskii <eliz@gnu.org>
> >> Cc: 21780@debbugs.gnu.org
> >>
> >> If you want to have Unix EOLs by default, the correct customization is
> >> this:
> >>
> >> (setq-default buffer-file-coding-system
> >> (coding-system-change-eol-conversion
> >> buffer-file-coding-system 'unix))
> >
> > This variant is better:
> >
> > (setq-default buffer-file-coding-system
> > (coding-system-change-eol-conversion
> > default-buffer-file-coding-system 'unix))
>
> Why ? Help for `default-buffer-file-coding-system' says:
>
> This variable is obsolete since 23.2;
> use ‘buffer-file-coding-system’ instead.
Then use (default-value buffer-file-coding-system) instead. The point
being to use the default value to modify the default value. When this
code runs, the current buffer should have the same value as its
buffer-local value, but I preferred not to rely on that.
> I think Drew's version was fine.
What Drew's version? The one that unconditionally used undecided-unix
as the default? I very much disagree.
next prev parent reply other threads:[~2015-10-31 7:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<536fdfb7-20dd-4d23-886c-8e842b6844fd@default>
[not found] ` <<83lhal1qtm.fsf@gnu.org>
2015-10-29 20:53 ` bug#21780: 25.0.50; Saving *Help* results in bad encoding because of curly quotes Drew Adams
2015-10-30 7:47 ` Eli Zaretskii
[not found] ` <<2c1ac781-86b8-4365-8466-52455afb79f6@default>
[not found] ` <<83k2q423x7.fsf@gnu.org>
2015-10-30 15:07 ` Drew Adams
2015-10-30 15:22 ` Eli Zaretskii
[not found] ` <<17cf8a49-1cc4-4834-91ec-b7d092693ebf@default>
[not found] ` <<83si4sz8i5.fsf@gnu.org>
2015-10-30 16:02 ` Drew Adams
2015-10-30 16:17 ` Drew Adams
2015-10-30 20:50 ` Eli Zaretskii
2015-10-30 20:57 ` Eli Zaretskii
2015-10-29 1:50 ` Drew Adams
2015-10-29 17:41 ` Eli Zaretskii
2015-10-30 23:06 ` Andy Moreton
2015-10-31 7:28 ` Eli Zaretskii [this message]
2015-10-31 18:10 ` Andy Moreton
[not found] <<48a87436-595a-4f65-9e3c-094f6d77ee96@default>
[not found] ` <<83eggcytam.fsf@gnu.org>
[not found] ` <<83d1vwyt02.fsf@gnu.org>
2015-10-30 21:27 ` Drew Adams
[not found] <<ab84db1b-77e3-4ef1-ac0e-e91264d78b8f@default>
[not found] ` <<83oafh1sj1.fsf@gnu.org>
2015-10-29 17:58 ` Drew Adams
2015-10-29 18:18 ` Eli Zaretskii
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=83a8qzzed0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21780@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).