From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 34862@debbugs.gnu.org, rms@gnu.org
Subject: bug#34862: 27.0.50; Trying to update pinyin.map
Date: Wed, 20 Mar 2019 12:41:45 -0700 [thread overview]
Message-ID: <87ftrhs58m.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <83imwds5cw.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 20 Mar 2019 21:39:11 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Eric Abrahamsen <eric@ericabrahamsen.net>
>> Cc: Richard Stallman <rms@gnu.org>, 34862@debbugs.gnu.org
>> Date: Wed, 20 Mar 2019 12:30:22 -0700
>>
>> > I think this should be done with a script, and that script should be
>> > in our repository. The easiest kind of a script is a Lisp program, of
>> > course, but we can also use other kinds, such as Awk scripts.
>>
>> Awk seems just right for the problem, but I haven't written much in it;
>> I did the original munging in elisp. Would this be a script written for
>> use with -batch and a custom make target?
>
> Yes.
>
>> should it also be responsible for downloading a recent copy of the
>> source file, or should that be done first, and the function pointed
>> at the file?
>
> The latter, I think. That's what we do with the other data files we
> use from external sources, e.g. see admin/unidata/.
Understood -- thanks for this.
next prev parent reply other threads:[~2019-03-20 19:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 21:49 bug#34862: 27.0.50; Trying to update pinyin.map Eric Abrahamsen
2019-03-15 5:03 ` Eli Zaretskii
2019-03-15 5:58 ` Eric Abrahamsen
2019-03-15 7:04 ` Eli Zaretskii
2019-03-15 18:31 ` Eric Abrahamsen
2019-03-20 9:45 ` Eli Zaretskii
2019-03-20 19:30 ` Eric Abrahamsen
2019-03-20 19:39 ` Eli Zaretskii
2019-03-20 19:41 ` Eric Abrahamsen [this message]
2022-02-02 18:59 ` Lars Ingebrigtsen
2022-02-08 0:26 ` Eric Abrahamsen
2022-02-08 6:12 ` Lars Ingebrigtsen
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=87ftrhs58m.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=34862@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rms@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).