From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] PATCH: click-to-focus in fgui
Date: Sun, 15 Aug 2021 08:47:44 +0200 [thread overview]
Message-ID: <CAFSF3XOUL6QPyW_MrpK6HE3PjxRniH9qfzYjj8O5sEtB-VN8mQ@mail.gmail.com> (raw)
In-Reply-To: <35D30064F0C69F74F6CF5AF1C2CAC860@smtp.pobox.com>
On 8/14/21, unobe@cpan.org <unobe@cpan.org> wrote:
> Quoth hiro <23hiro@gmail.com>:
>> > So far you're free to treat that as whatever you want. As you seem to
>> > hate the discussion and maybe the participants of it
>>
>> thanks for making it easy for me so I know i can stop reading already
>> after the second sentence.
>> both statements are untrue.
>
> I'm not understanding your line of reasoning, hiro: his first
> statement is untrue? You (hiro) are not free to treat that (i.e., his
> previous e-mail's content) as whatever you want (e.g., some sort of
> trolling)?
>
> For the second sentence, you only quoted the premise: Eckard said you
> "seem"--it's his perspective. If his perspective is not true, that's
> not the same as his statement re: his perspective not being true.[1]
> You can just say that his perspective (i.e, "hiro hate[s] the
> discussion and maybe the participants of it") isn't true, or just
> ignore the first paragraph entirely. If the premise is untrue, then
> his conclusion ("it's probably of much more value if you sit down and
> write a Plan9 bible with all se do's and dont's well ordered by
> precedence") does not necessarily follow. After the first paragraph,
> the rest of his e-mail is mainly focused on the issue. He is open to
> discussion. He ends his e-mail with: "Up to now, I didn't find a
> strong counterargument against a different focus policy, but am still
> open to know that."
>
> [1] The difference between "She seems to be angry" and she actually
> being angry.
>
>
wrong.
disclaimer: i'm not an expert in hiro studies.
next prev parent reply other threads:[~2021-08-15 20:24 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 22:59 Silas McCroskey
2021-08-10 14:19 ` ori
2021-08-11 5:28 ` rgl
2021-08-11 20:49 ` Philip Silva
2021-08-11 21:09 ` Steve Simon
2021-08-11 22:37 ` Xiao-Yong Jin
2021-08-12 9:05 ` hiro
2021-08-12 14:36 ` Eckard Brauer
2021-08-13 6:44 ` unobe
2021-08-13 7:10 ` hiro
2021-08-14 10:20 ` Eckard Brauer
2021-08-14 13:09 ` qwx
2021-08-14 15:03 ` Stuart Morrow
2021-08-14 13:17 ` José Miguel Sánchez García
2021-08-14 20:57 ` Patch-keeping (Was Re: [9front] PATCH: click-to-focus in fgui) unobe
2021-08-14 15:04 ` [9front] PATCH: click-to-focus in fgui Stuart Morrow
2021-08-14 18:08 ` hiro
2021-08-14 21:43 ` unobe
2021-08-15 6:47 ` hiro [this message]
2021-08-14 21:46 ` unobe
2021-08-15 13:36 ` Eckard Brauer
2021-08-15 19:16 ` hiro
2021-08-15 17:31 ` kvik
2021-08-15 18:34 ` Kurt H Maier
2021-08-15 18:48 ` Stanley Lieber
2021-08-15 20:18 ` Eckard Brauer
2021-08-15 22:35 ` Stanley Lieber
2021-08-16 5:14 ` Stanley Lieber
2021-08-16 15:46 ` Skylar Bleed
2021-08-15 19:03 ` hiro
2021-08-16 16:40 ` kvik
2021-08-16 19:25 ` Stuart Morrow
2021-08-16 19:40 ` Kurt H Maier
2021-08-17 2:05 ` Stanley Lieber
2021-08-16 20:04 ` hiro
2021-08-16 20:13 ` hiro
2021-08-17 1:10 ` Xiao-Yong Jin
2021-08-17 8:11 ` hiro
2021-08-12 0:12 ` hiro
2021-08-15 4:29 ` ori
2021-08-16 19:40 ` ori
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFSF3XOUL6QPyW_MrpK6HE3PjxRniH9qfzYjj8O5sEtB-VN8mQ@mail.gmail.com \
--to=23hiro@gmail.com \
--cc=9front@9front.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.
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 NNTP newsgroup(s).