From: Federico Beffa <beffa@ieee.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 21829@debbugs.gnu.org
Subject: bug#21829: guix import hackage failures
Date: Thu, 12 Nov 2015 17:54:48 +0100 [thread overview]
Message-ID: <CAKrPhPOeaub1iEnedfxv7G+1rgWpUS8mkjRGOxhtNdXSUz5a5Q@mail.gmail.com> (raw)
In-Reply-To: <87vb971t74.fsf@gnu.org>
On Thu, Nov 12, 2015 at 10:07 AM, Ludovic Courtès <ludo@gnu.org> wrote:
> Federico Beffa <beffa@ieee.org> skribis:
> I wonder if it wouldn’t be easier to change the lexer to recognize line
> feeds are white space or newlines, maybe along these lines:
What you suggest is not enough. You have to tweak a couple of other
places as well.
I don't like having to mess around in token recognition code to
account for different eol styles. With my proposal I was trying to
abstract this away and make the eol style problem orthogonal to
parsing: first we convert to a "normal form" and then we operate on
it. Should we find some files in 'mac' eol-style (in Emacs parlance)
then it would be trivial to adapt.
Could you be more explicit about what you do not like about this?
Regards,
Fede
next prev parent reply other threads:[~2015-11-12 16:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 15:00 bug#21829: guix import hackage failures Paul van der Walt
2015-11-04 23:11 ` Ludovic Courtès
2015-11-10 16:40 ` Federico Beffa
2015-11-11 11:18 ` Ludovic Courtès
2015-11-11 21:29 ` Federico Beffa
2015-11-12 9:07 ` Ludovic Courtès
2015-11-12 16:54 ` Federico Beffa [this message]
2015-11-12 20:21 ` Ludovic Courtès
2015-11-13 17:08 ` Federico Beffa
2015-11-13 21:19 ` Ludovic Courtès
2015-11-14 14:37 ` Federico Beffa
2015-11-15 20:59 ` Ludovic Courtès
2015-11-25 16:55 ` Federico Beffa
2015-11-25 21:45 ` Ludovic Courtès
2015-11-26 8:28 ` Federico Beffa
2015-11-26 8:46 ` Ludovic Courtès
2015-11-26 17:23 ` Federico Beffa
2015-11-26 19:56 ` Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKrPhPOeaub1iEnedfxv7G+1rgWpUS8mkjRGOxhtNdXSUz5a5Q@mail.gmail.com \
--to=beffa@ieee.org \
--cc=21829@debbugs.gnu.org \
--cc=ludo@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/guix.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).