From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: etc/HELLO markup etc.
Date: Sun, 06 Jan 2019 13:08:35 -0500 [thread overview]
Message-ID: <jwvy37x3bhg.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: 83r2dpznvy.fsf@gnu.org
>> > Thanks. I guess we can remove most of charset markup from HELLO,
>> > leaving only one or two as an example of the facility.
>>
>> And to get back to bug#33796: does that mean I can install a change to
>> convert those Elisp files to utf-8?
>
> Yes, I think so. Except that I'd prefer not to mix code changes and
> encoding changes. Can you do that in two separate patches?
Yes, of course,
Stefan
next prev parent reply other threads:[~2019-01-06 18:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3fd27fe5-e650-b207-fdd4-36f805b89b4d@cs.ucla.edu>
[not found] ` <83bm5hcroa.fsf@gnu.org>
[not found] ` <9f33127d-f01b-b138-7a0c-ffeac7b77938@cs.ucla.edu>
[not found] ` <835zvochdj.fsf@gnu.org>
[not found] ` <5f113128-36c9-30c6-3413-8dc36051e058@cs.ucla.edu>
[not found] ` <83va3nban3.fsf@gnu.org>
2018-12-21 21:07 ` 27.0.50; Use utf-8 is all our Elisp files Paul Eggert
2018-12-22 1:19 ` Eric Lindblad
2018-12-22 7:56 ` etc/HELLO markup etc. (Was: 27.0.50; Use utf-8 is all our Elisp files) Eli Zaretskii
2018-12-22 8:12 ` etc/HELLO markup etc Eli Zaretskii
2018-12-22 19:41 ` Paul Eggert
2018-12-22 20:42 ` Eli Zaretskii
2018-12-23 7:47 ` Yuri Khan
2018-12-23 15:42 ` Eli Zaretskii
2018-12-23 15:53 ` Werner LEMBERG
2018-12-23 16:04 ` Eli Zaretskii
2018-12-23 21:11 ` Werner LEMBERG
2018-12-28 7:10 ` Eli Zaretskii
2018-12-29 7:23 ` handa
2018-12-29 7:37 ` Eli Zaretskii
2019-01-06 12:06 ` handa
2019-01-06 15:29 ` Eli Zaretskii
2019-01-06 17:26 ` Stefan Monnier
2019-01-06 17:39 ` Eli Zaretskii
2019-01-06 18:08 ` Stefan Monnier [this message]
2018-12-29 5:32 Van L
2018-12-29 7:33 ` Eli Zaretskii
2018-12-30 6:51 ` Van L
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=jwvy37x3bhg.fsf-monnier+gmane.emacs.devel@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@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).