Hi all,
Am 10.02.21 um 13:10 schrieb Alessandro Rubini:
> The problem your describe is that of bashisms. I agree we should use
> /bin/sh in published scripts (and ensure our own sh is not some
> featureful derivation).
I think one should not publish any shell scripts any more except for
the
Hello.
I don't think FSFE should provide coding standard: everybody is
already doing that. Some coding standard make no sense, some are ugly,
some are good; you only need to choose yours -- or be forced by your
employer.
The problem your describe is that of bashisms. I agree we should use
Hi kreyren,
On Wednesday, 2021-02-10 08:46:15 +, krey...@rixotstudio.cz wrote:
> Justify bad code and elaborate on bad mail user agents.
No. But if these produce text I can't read and cripple "source code" to
be discussed there's no incentive to even follow a discussion.
Eike
--
Hi Valerio,
On Wednesday, 2021-02-10 09:13:35 +0100, Valerio Bellizzomi wrote:
> On Tue, 2021-02-09 at 22:40 +0100, Eike Rathke wrote:
> > Before discussing coding standards we should rule out bad Mail User
> > Agents that produce totally unusable text/plain from text/html in
> > their
> >
On Tue, 2021-02-09 at 22:40 +0100, Eike Rathke wrote:
> Hi,
>
> On Monday, 2021-02-08 10:56:43 +, Jacob Hrbek wrote:
>
> > Should FSFE provide some kind of platform for community to discuss
> > and propose coding standards?
>
> Before discussing coding standards we should rule out bad Mail
On 2/9/21 10:40 PM, Eike Rathke wrote:
> Hi,
>
> On Monday, 2021-02-08 10:56:43 +, Jacob Hrbek wrote:
>
>> Should FSFE provide some kind of platform for community to discuss and
>> propose coding standards?
> Before discussing coding standards we should rule out bad Mail User
> Agents that
Hi,
On Monday, 2021-02-08 10:56:43 +, Jacob Hrbek wrote:
> Should FSFE provide some kind of platform for community to discuss and
> propose coding standards?
Before discussing coding standards we should rule out bad Mail User
Agents that produce totally unusable text/plain from text/html
