From: Eli Zaretskii <eliz@gnu.org>
To: vincent.belaiche@gmail.com (Vincent Belaïche)
Cc: 27391@debbugs.gnu.org
Subject: bug#27391: 25.2.50; utf-8 coding cookie is not applied on some specific markdown file
Date: Fri, 16 Jun 2017 15:59:23 +0300 [thread overview]
Message-ID: <83lgos142c.fsf@gnu.org> (raw)
In-Reply-To: <841sqkdzh5.fsf@gmail.com> (vincent.belaiche@gmail.com)
> From: vincent.belaiche@gmail.com (Vincent Belaïche)
> Date: Fri, 16 Jun 2017 12:00:06 +0200
> Cc: Vincent Belaïche <vincent.belaiche@gmail.com>
>
> I was editing some file written in Markdown. Here is the file :
>
> https://framagit.org/latex-pourquoi-comment/lpc-articles/blob/795ecb9d4f7b8870486fe6557f01d2fe450c4461/CONTRIBUTING.md
>
> My Emacs default configuration was to get files in latin-1. So I had
> added some `coding: utf-8' cookie in this file. But it did not work, the
> file was still read in latin-1 instead of utf8.
I cannot reproduce this, and I don't see any coding cookies in the
file I downloaded.
Please provide a minimal recipe that's required to reproduce the
problem. In particular, since you tried in "emacs -q", I don't
understand what does it mean that your default configuration is
latin-1: in "emacs -q" your default configuration is determined by
your system locale.
Thanks.
next prev parent reply other threads:[~2017-06-16 12:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 10:00 bug#27391: 25.2.50; utf-8 coding cookie is not applied on some specific markdown file Vincent Belaïche
2017-06-16 12:59 ` Eli Zaretskii [this message]
2017-06-16 14:08 ` Vincent Belaïche
2017-06-16 14:10 ` Vincent Belaïche
2017-06-16 18:38 ` Eli Zaretskii
2017-06-16 19:08 ` Vincent Belaïche
2017-06-16 19:15 ` Vincent Belaïche
2017-06-16 19:31 ` Andreas Schwab
2017-06-16 19:37 ` Vincent Belaïche
2017-06-16 21:27 ` Vincent Belaïche
2017-06-16 21:34 ` Philipp Stephani
2017-06-16 21:39 ` Philipp Stephani
2017-06-16 21:52 ` Philipp Stephani
2017-06-16 22:09 ` Vincent Belaïche
2017-06-16 22:23 ` Vincent Belaïche
2017-06-17 5:45 ` Vincent Belaïche
2017-06-17 14:30 ` Philipp Stephani
2017-06-19 10:51 ` Vincent Belaïche
2017-06-26 11:39 ` Philipp Stephani
2017-06-27 6:05 ` Vincent Belaïche
2017-06-17 14:15 ` Philipp Stephani
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=83lgos142c.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=27391@debbugs.gnu.org \
--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).