From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 40148@debbugs.gnu.org, mangelozzi@gmail.com
Subject: bug#40148: 26.3; Custom package header checked out from GIT in Windows will not parse
Date: Fri, 20 Mar 2020 16:47:54 +0200 [thread overview]
Message-ID: <83lfnvdqw5.fsf@gnu.org> (raw)
In-Reply-To: <85v9mznlx4.fsf@gmail.com> (message from Noam Postavsky on Fri, 20 Mar 2020 10:25:11 -0400)
> From: Noam Postavsky <npostavs@gmail.com>
> Cc: Michael Angelozzi <mangelozzi@gmail.com>, 40148@debbugs.gnu.org
> Date: Fri, 20 Mar 2020 10:25:11 -0400
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > It may be the case that package.el should be more tolerant in this
> > case, but that's just the tip of an iceberg, because there are files
> > out there where LF to CR-LF conversions are a no-no (just one example:
> > Unix shell scripts). Just say no to this "feature", and Bob's your
> > uncle.
>
> The problem happens without git conversion as well (because Emacs
> defaults to "dos" encoding on windows-nt systems):
You are saying that creating a package (or a new file in a package)
should leave the EOL format of the Lisp files at "dos", and distribute
the package's files like that via the elpa's?
next prev parent reply other threads:[~2020-03-20 14:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 8:50 bug#40148: 26.3; Custom package header checked out from GIT in Windows will not parse Michael Angelozzi
2020-03-20 13:58 ` Eli Zaretskii
2020-03-20 14:25 ` Noam Postavsky
2020-03-20 14:47 ` Eli Zaretskii [this message]
2020-03-20 19:47 ` Noam Postavsky
2020-03-21 7:35 ` Eli Zaretskii
2021-12-05 1:18 ` Lars Ingebrigtsen
2021-12-05 1:19 ` Lars Ingebrigtsen
[not found] ` <CAFNYG9f3OaP=a+NbKq73XNxKdK4SJX9T4EBL-hbCCwD82+P+Kw@mail.gmail.com>
2021-12-05 19:55 ` Lars Ingebrigtsen
2021-12-07 4:13 ` Richard Stallman
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=83lfnvdqw5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=40148@debbugs.gnu.org \
--cc=mangelozzi@gmail.com \
--cc=npostavs@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).