unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Nala Ginrut <nalaginrut@gmail.com>
Cc: "mikael@djurfeldt.com" <mikael@djurfeldt.com>,
	 Adam Faiz <adam.faiz@disroot.org>,
	guile-devel <guile-devel@gnu.org>,
	 Ricardo Wurmus <rekado@elephly.net>, Tomas Volf <~@wolfsden.cz>
Subject: RE: [PATCH] test-suite: Add tests for `for-rdelim-in-port`-related functions.
Date: Fri, 20 Dec 2024 13:53:06 +0100	[thread overview]
Message-ID: <20241220135310.r0t92D0082kJuzj010t981@laurent.telenet-ops.be> (raw)
In-Reply-To: <CAPjoZoeRnmUePOXiNLo3QxjShpLNPqTft3ibVnhpa=w3j_MJEQ@mail.gmail.com>

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

>I have no any interest to persuade you, just show my opinion and suggestions. 
>And I also have no interest to argue with you about the design, because the efforts has made according to you suggestions. 
This is a problem. Just making a proposal without following up on discussions of its merits / demerits is ok, as long as you don’t push the proposal afterwards. Likewise, mentioning a (claimed) demerits of a counter-proposal is fine even if you don’t follow-up on counter-arguments.
But you did continue pushing the proposal – and not just by making some parts of it more clear, but in the form “actually I do intend to persuade, but I don’t want to think about actual arguments, so I’ll just repeat my claims without addressing the (counter)arguments”. Tacking on “just my opinion” doesn’t make it so, it just makes it look like an attempt for plausible deniability.
Whether you intended to or not, you did present an ad nauseum (+ implausible deniability) argument, so it is an ad nauseum argument.
>I'm trying to follow the idea to not waste any efforts have been made.
(Here you are making an (implicit) strawman again.) Then you are failing. In my proposal there is nothing about wasting effort, and your nauseum argumentation is quite a waste.
>My suggestion is to find something function to test under different platforms. And if you think (uname) is not a good way, you should give a better solution.
I already did. Also, no. Just because you know something is bad, doesn’t mean you know a better solution, so it doesn’t automatically follow that a better solution should be given.
It’s quite frustrating to be asked “You should tell me how to X” right after I did tell you how to X. It’s as-if you want people to not join the ML or have people leave the ML.
>If any possible, follow the path technically, not waste anyone's time, include me, to discuss things that outside of the patch itself.
Going slightly beyond the scope of a patch is not necessarily a waste of time, and on average can same some time (because less patches would be needed), as I probably mentioned earlier in some other words.
Also, "anyone” includes me. You should stop wasting _my_ time by repeating your ad nauseum messages -- whether it’s for just repeating your opinion, or intended for (fallacious) argumentation or persuasion, it is quite ad nauseum.
Regards,
Maxime Devos

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

  reply	other threads:[~2024-12-20 12:53 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 [this message]
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
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=20241220135310.r0t92D0082kJuzj010t981@laurent.telenet-ops.be \
    --to=maximedevos@telenet.be \
    --cc=adam.faiz@disroot.org \
    --cc=guile-devel@gnu.org \
    --cc=mikael@djurfeldt.com \
    --cc=nalaginrut@gmail.com \
    --cc=rekado@elephly.net \
    --cc=~@wolfsden.cz \
    /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).