unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Nala Ginrut <nalaginrut@gmail.com>
To: mikael@djurfeldt.com
Cc: Maxime Devos <maximedevos@telenet.be>,
	Adam Faiz <adam.faiz@disroot.org>,
	 guile-devel <guile-devel@gnu.org>
Subject: Re: [PATCH] test-suite: Add tests for `for-rdelim-in-port`-relatedfunctions.
Date: Sat, 21 Dec 2024 02:31:47 +0900	[thread overview]
Message-ID: <CAPjoZocK42yoB4Cnx-kom1zmokFRbV2zU_MBNapo-8uKL1ScyQ@mail.gmail.com> (raw)
In-Reply-To: <CAA2XvwJfbHk15VZQcar92ttcwthE7cxMcvkKHuWk5BXxP9ea1Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 638 bytes --]

>
> If so, the entire (ice-9 rdelim) module needs to be revised as well as
> libguile/rdelim.c since the current implementation assumes that the line
> delimiter is a single character, which was not true under Windows last time
> I checked.
>


As I know, Windows seems the only mainstream and living OS which treat
newline with 2 chars. And according to my previous suggestion, people use
WSL for GNU tools on Windows nowadays.
So I wonder if it is still necessary to introduce and maintain such
complexity.
But as I said before, it is not a bad idea to do this, just cost wise.
Again, I don't against such an opinion.

Best regards.

>

[-- Attachment #2: Type: text/html, Size: 1417 bytes --]

  reply	other threads:[~2024-12-20 17:31 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-16 15:21 [PATCH 1/2] rdelim: Add new procedure `for-rdelim-in-port` Adam Faiz
2024-12-16 15:24 ` [PATCH 2/2] doc: Add documentation for `for-rdelim-in-port` and, related procedures Adam Faiz
2024-12-17  4:31   ` [PATCH] test-suite: Add tests for `for-rdelim-in-port`-related functions Adam Faiz
2024-12-17  5:11     ` Nala Ginrut
2024-12-17  7:21       ` Mikael Djurfeldt
2024-12-17 16:43         ` Mikael Djurfeldt
2024-12-20  9:15           ` Maxime Devos
2024-12-20  9:57             ` Nala Ginrut
2024-12-20 11:51               ` Maxime Devos
2024-12-20 12:00                 ` Nala Ginrut
2024-12-20 12:53                   ` Maxime Devos
2024-12-20 13:00                     ` Nala Ginrut
2024-12-20 13:45                       ` Maxime Devos
2024-12-20 13:52                         ` Nala Ginrut
2024-12-20 14:18                           ` Maxime Devos
2024-12-20 14:30                             ` Nala Ginrut
2024-12-20 14:32                               ` Nala Ginrut
2024-12-20 14:47                               ` Maxime Devos
2024-12-20 14:56                                 ` Nala Ginrut
2024-12-20 15:07                                   ` Maxime Devos
2024-12-20 15:13                                     ` Nala Ginrut
2024-12-19 21:50     ` Mikael Djurfeldt
2024-12-20 15:15       ` [PATCH] test-suite: Add tests for `for-rdelim-in-port`-relatedfunctions Maxime Devos
2024-12-20 17:11         ` Mikael Djurfeldt
2024-12-20 17:31           ` Nala Ginrut [this message]
2024-12-20 18:40           ` Maxime Devos
2024-12-16 16:46 ` [PATCH 1/2] rdelim: Add new procedure `for-rdelim-in-port` Nala Ginrut

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/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPjoZocK42yoB4Cnx-kom1zmokFRbV2zU_MBNapo-8uKL1ScyQ@mail.gmail.com \
    --to=nalaginrut@gmail.com \
    --cc=adam.faiz@disroot.org \
    --cc=guile-devel@gnu.org \
    --cc=maximedevos@telenet.be \
    --cc=mikael@djurfeldt.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.
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).