From: Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net>
To: 9front@9front.org
Subject: Re: [9front] bc and < >
Date: Mon, 10 Jan 2022 13:29:03 +0100 [thread overview]
Message-ID: <87o84jg4fk.fsf@turtle-trading.net> (raw)
In-Reply-To: <20220110131413.30f7c0ad@gmx.de> (Eckard Brauer's message of "Mon, 10 Jan 2022 13:14:13 +0100")
Hi Eckard,
Eckard Brauer writes:
> maybe as a workaround:
Thanks. Yes, there are a number of workarounds.
benny
next prev parent reply other threads:[~2022-01-10 13:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 11:49 Benjamin Riefenstahl
2022-01-10 12:14 ` Eckard Brauer
2022-01-10 12:29 ` Benjamin Riefenstahl [this message]
2022-01-10 12:14 ` 有澤 健治
2022-01-10 13:25 ` Benjamin Riefenstahl
2022-01-10 12:23 ` Eckard Brauer
2022-01-10 13:24 ` Benjamin Riefenstahl
2022-01-10 14:00 ` Eckard Brauer
2022-01-11 6:29 ` cinap_lenrek
2022-01-12 8:00 ` Eckard Brauer
2022-01-12 9:13 ` Marc Chantreux
2022-01-13 5:22 ` umbraticus
2022-01-13 12:17 ` sirjofri
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=87o84jg4fk.fsf@turtle-trading.net \
--to=b.riefenstahl@turtle-trading.net \
--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).