Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #100632 > unrolled thread

How to ignore error with anon-zero exit status

Back to article view | Back to comp.lang.python

Contents

  How to ignore error with anon-zero exit status Ganesh Pal <ganesh1pal@gmail.com> - 2015-12-20 23:00 +0530
    Ignore error with non-zero exit status (was: How to ignore error with anon-zero exit status) Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-12-20 22:22 +0100
      Re: Ignore error with non-zero exit status (was: How to ignore error with anon-zero exit status) Chris Angelico <rosuav@gmail.com> - 2015-12-21 08:56 +1100
        Re: Ignore error with non-zero exit status Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-12-20 23:46 +0100
          Re: Ignore error with non-zero exit status Chris Angelico <rosuav@gmail.com> - 2015-12-21 10:09 +1100
            Re: Ignore error with non-zero exit status Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-12-21 08:51 +0100
              Re: Ignore error with non-zero exit status Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-12-21 12:58 +0000
                Re: Ignore error with non-zero exit status Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-12-21 14:19 +0100
                  Re: Ignore error with non-zero exit status Chris Angelico <rosuav@gmail.com> - 2015-12-22 00:23 +1100
                    Re: Ignore error with non-zero exit status Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-12-21 15:05 +0100
                      Re: Ignore error with non-zero exit status Chris Angelico <rosuav@gmail.com> - 2015-12-22 01:11 +1100
                        Re: Ignore error with non-zero exit status Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-12-21 15:19 +0100
                          Re: Ignore error with non-zero exit status Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-12-21 16:07 +0000
                            Re: Ignore error with non-zero exit status Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-12-21 23:30 +0100
                          Re: Ignore error with non-zero exit status Random832 <random832@fastmail.com> - 2015-12-21 11:30 -0500
                            Re: Ignore error with non-zero exit status Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-12-21 23:27 +0100
                              Re: Ignore error with non-zero exit status Steven D'Aprano <steve@pearwood.info> - 2015-12-22 10:32 +1100
                      Re: Ignore error with non-zero exit status Terry Reedy <tjreedy@udel.edu> - 2015-12-21 18:53 -0500
                        Re: Ignore error with non-zero exit status Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-12-22 13:17 +0100
                      Re: Ignore error with non-zero exit status Chris Angelico <rosuav@gmail.com> - 2015-12-22 11:05 +1100
                      Re: Ignore error with non-zero exit status Ian Kelly <ian.g.kelly@gmail.com> - 2015-12-21 17:17 -0700
                      Re: Ignore error with non-zero exit status Chris Angelico <rosuav@gmail.com> - 2015-12-22 11:25 +1100
          Re: Ignore error with non-zero exit status Ian Kelly <ian.g.kelly@gmail.com> - 2015-12-21 13:30 -0700
          Meaning and purpose of the Subject field (was: Ignore error with non-zero exit status) Ben Finney <ben+python@benfinney.id.au> - 2015-12-22 07:58 +1100
          Re: Meaning and purpose of the Subject field (was: Ignore error with non-zero exit status) Ian Kelly <ian.g.kelly@gmail.com> - 2015-12-21 14:16 -0700
            Re: Meaning and purpose of the Subject field (was: Ignore error with non-zero exit status) Jon Ribbens <jon+usenet@unequivocal.co.uk> - 2015-12-21 21:44 +0000
              Re: Meaning and purpose of the Subject field Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-12-21 23:55 +0100
              Re: Meaning and purpose of the Subject field (was: Ignore error with non-zero exit status) Steven D'Aprano <steve@pearwood.info> - 2015-12-22 10:14 +1100
                Re: Meaning and purpose of the Subject field (was: Ignore error with non-zero exit status) Jon Ribbens <jon+usenet@unequivocal.co.uk> - 2015-12-21 23:24 +0000
                  Re: Meaning and purpose of the Subject field (was: Ignore error with non-zero exit status) Ian Kelly <ian.g.kelly@gmail.com> - 2015-12-21 16:57 -0700
                  Re: Meaning and purpose of the Subject field (was: Ignore error with non-zero exit status) Tim Chase <python.list@tim.thechases.com> - 2015-12-22 09:56 -0600
                Re: Meaning and purpose of the Subject field (was: Ignore error with non-zero exit status) Cameron Simpson <cs@zip.com.au> - 2015-12-22 14:36 +1100
                Re: Meaning and purpose of the Subject field Random832 <random832@fastmail.com> - 2015-12-21 23:22 -0500
                  Re: Meaning and purpose of the Subject field Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-12-22 13:26 +0100
                Re: Meaning and purpose of the Subject field (was: Ignore error with non-zero exit status) Grant Edwards <invalid@invalid.invalid> - 2015-12-22 15:17 +0000
                  Re: Meaning and purpose of the Subject field (was: Ignore error with non-zero exit status) Ian Kelly <ian.g.kelly@gmail.com> - 2015-12-22 08:28 -0700
                    Re: Meaning and purpose of the Subject field (was: Ignore error with non-zero exit status) Grant Edwards <invalid@invalid.invalid> - 2015-12-22 22:32 +0000
          Re: Meaning and purpose of the Subject field (was: Ignore error with non-zero exit status) Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2015-12-21 16:55 -0500
      Re: Ignore error with non-zero exit status (was: How to ignore error with anon-zero exit status) Ganesh Pal <ganesh1pal@gmail.com> - 2015-12-21 08:22 +0530
        Re: Ignore error with non-zero exit status Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-12-21 08:54 +0100

Page 2 of 2 — ← Prev page 1 [2]

#100711 — Re: Ignore error with non-zero exit status

On Dec 21, 2015 4:55 PM, "Terry Reedy" <tjreedy@udel.edu> wrote:
>
> Nothing has changed since except for
> https://www.python.org/dev/peps/pep-0498/
> already added to 3.6.

https://xkcd.com/927/

[toc] | [prev] | [next] | [standalone]

#100713 — Re: Ignore error with non-zero exit status

On Tue, Dec 22, 2015 at 11:17 AM, Ian Kelly <ian.g.kelly@gmail.com> wrote:
> On Dec 21, 2015 4:55 PM, "Terry Reedy" <tjreedy@udel.edu> wrote:
>>
>> Nothing has changed since except for
>> https://www.python.org/dev/peps/pep-0498/
>> already added to 3.6.
>
> https://xkcd.com/927/

The 927ness of it was discussed at length prior to implementation. PEP
498 isn't really another competing string format operation; it's more
like an alternative expression format. It's more in competition with
this:

msg = "The sum of " + str(x) + " and " + str(y) + " is " + str(x+y) + "."

which puts the interpolated expressions at the "correct place" in the
string - but at the cost of being verbose, messy, and error-prone.
Compare:

msg = f"The sum of {x} and {y} is {x+y}."

(Yes, there's a slight semantic difference; the latter uses format()
rather than str(). But otherwise, it's compiled to the "".join(...)
equivalent of the repeated concatenation example.)

ChrisA

[toc] | [prev] | [next] | [standalone]

#100695 — Re: Ignore error with non-zero exit status

On Sun, Dec 20, 2015 at 3:46 PM, Thomas 'PointedEars' Lahn
<PointedEars@web.de> wrote:
> Chris Angelico wrote:
>
>> On Mon, Dec 21, 2015 at 8:22 AM, Thomas 'PointedEars' Lahn
>> <PointedEars@web.de> wrote:
>
> It is supposed to be an attribution *line*, _not_ an attribution novel.
> Also, the “(was: …)” part is to be removed from the Subject header field
> value to complete the change of subject in a thread.

Better yet, please don't change the Subject header for trivial reasons
in the first place. This isn't just a Usenet group; it's also a
mailing list, and many MUAs rely on the Subject header for proper
threading.

[toc] | [prev] | [next] | [standalone]

#100696 — Meaning and purpose of the Subject field (was: Ignore error with non-zero exit status)

Ian Kelly <ian.g.kelly@gmail.com> writes:

> Better yet, please don't change the Subject header for trivial reasons
> in the first place.

When the subject of the ongoing discussion changes, it's normal to
change the Subject field accordingly.

I agree with your admonition against trivial alterations to that field;
I hope you agree with me that it is not trivial, but rather is normal
and helpful, to update the Subject field to track significant changes in
the subject of the discussion.

> This isn't just a Usenet group; it's also a mailing list, and many
> MUAs rely on the Subject header for proper threading.

If such MUAs do that, they're misinterpreting the Subject field. Other
fields are available with the explicit meaning of relating messages to
each other regardless of what they discuss.

If the correct fields are being mangled, then the correct place to apply
pressure is on those who can fix that error. Let's not overload the
Subject field to make up the lack.

-- 
 \           “Self-respect: The secure feeling that no one, as yet, is |
  `\                                    suspicious.” —Henry L. Mencken |
_o__)                                                                  |
Ben Finney

[toc] | [prev] | [next] | [standalone]

#100697 — Re: Meaning and purpose of the Subject field (was: Ignore error with non-zero exit status)

On Mon, Dec 21, 2015 at 1:58 PM, Ben Finney <ben+python@benfinney.id.au> wrote:
> Ian Kelly <ian.g.kelly@gmail.com> writes:
>> This isn't just a Usenet group; it's also a mailing list, and many
>> MUAs rely on the Subject header for proper threading.
>
> If such MUAs do that, they're misinterpreting the Subject field. Other
> fields are available with the explicit meaning of relating messages to
> each other regardless of what they discuss.
>
> If the correct fields are being mangled, then the correct place to apply
> pressure is on those who can fix that error. Let's not overload the
> Subject field to make up the lack.

It might just be Gmail.

http://webapps.stackexchange.com/questions/965/how-does-gmail-decide-to-thread-email-messages

I can't specifically recall if I've used any MUA other than Gmail that
even attempts threading email messages.

[toc] | [prev] | [next] | [standalone]

#100698 — Re: Meaning and purpose of the Subject field (was: Ignore error with non-zero exit status)

On 2015-12-21, Ian Kelly <ian.g.kelly@gmail.com> wrote:
> On Mon, Dec 21, 2015 at 1:58 PM, Ben Finney <ben+python@benfinney.id.au> wrote:
>> Ian Kelly <ian.g.kelly@gmail.com> writes:
>>> This isn't just a Usenet group; it's also a mailing list, and many
>>> MUAs rely on the Subject header for proper threading.
>>
>> If such MUAs do that, they're misinterpreting the Subject field. Other
>> fields are available with the explicit meaning of relating messages to
>> each other regardless of what they discuss.
>>
>> If the correct fields are being mangled, then the correct place to apply
>> pressure is on those who can fix that error. Let's not overload the
>> Subject field to make up the lack.
>
> It might just be Gmail.
>
> http://webapps.stackexchange.com/questions/965/how-does-gmail-decide-to-thread-email-messages
>
> I can't specifically recall if I've used any MUA other than Gmail that
> even attempts threading email messages.

Also: Thunderbird, The Bat!, Eudora, Gnus, Outlook, Outlook Express,
Pegasus Mail, Pine, Apple Mail, Windows Live Mail, Yahoo Mail,
Evolution, SquirrelMail, KMail, Windows Mail, etc.

Trying to suggest that MUAs should never look at the Subject line for
threading is, unfortunately, ridiculous. Yes, in theory it shouldn't
be necessary but in practice enough people are using poor clients that
don't provide enough context in the proper headers that it can't be
avoided.

And, yes, fixing the mail clients of "everybody else in the world"
might be a lovely idea but it is a little impractical to implement.

[toc] | [prev] | [next] | [standalone]

#100703 — Re: Meaning and purpose of the Subject field

Jon Ribbens wrote:

> On 2015-12-21, Ian Kelly <ian.g.kelly@gmail.com> wrote:
>> I can't specifically recall if I've used any MUA other than Gmail that
>> even attempts threading email messages.
> 
> Also: Thunderbird, The Bat!, Eudora, Gnus, Outlook, Outlook Express,
> Pegasus Mail, Pine, Apple Mail, Windows Live Mail, Yahoo Mail,
> Evolution, SquirrelMail, KMail, Windows Mail, etc.

Yes, of course.
 
> Trying to suggest that MUAs should never look at the Subject line for
> threading is, unfortunately, ridiculous.

No, it is what the Internet message standard says instead:

,-<http://tools.ietf.org/html/rfc5322#section-3.6.4>
| 
| 3.6.4.  Identification Fields
| 
| Though listed as optional in the table in section 3.6, every message
| SHOULD have a "Message-ID:" field.  Furthermore, reply messages
| SHOULD have "In-Reply-To:" and "References:" fields as appropriate
| and as described below.
| 
| The "Message-ID:" field contains a single unique message identifier.
| The "References:" and "In-Reply-To:" fields each contain one or more
| unique message identifiers, optionally separated by CFWS.

(“SHOULD” in an RFC means: “do as I say unless you can give me a very good 
reason not to do it”.  See RFC 2119 for details.)

vs.

,-<http://tools.ietf.org/html/rfc5322#section-3.6.5>
| 
| 3.6.5.  Informational Fields
| 
| The informational fields are all optional.  The "Subject:" and
| "Comments:" fields are unstructured fields as defined in section
| 2.2.1, and therefore may contain text or folding white space. […]

> Yes, in theory it shouldn't be necessary

It is not.

> but in practice enough people are using poor clients that don't provide
> enough context in the proper headers that it can't be avoided.

That Internet communication is made more difficult for *all* because a 
*perceived* majority of *perceived* clients is broken, is putting upside 
down the good Internet principle of “be conservative in what to send, 
liberal in what to receive”.

Those b0rked clients should either be fixed at once or not be used, period.

Instead, in practice, the Python mailing list software is b0rked since I 
know of the mailing list’s/newsgroups’ existence (several years ago): it is 
b0rked in the regard that its distributor does not consider that it is also 
posted to a Usenet newsgroup where articles require a References header 
field to be properly threaded.  Incidentally, that References header field 
is, in the absence of an In-Reply-To header field, used by hybrid e 
mail/NetNews agents such as Thunderbird, in full compliance with the NetNews 
message standard:

,-<http://tools.ietf.org/html/rfc5536#section-3>
| 
| 3.  News Header Fields
| 
|    The following news header fields extend those defined in Section 3.6
|    of [RFC5322]:
| 
| […]
| 3.2.10.  References
| 
|    The References header field is the same as that specified in Section
|    3.6.4 of [RFC5322], with the added restrictions detailed above in
|    Section 2.2 and those listed below: […]

One could kill two birds with one stone here by fixing this, but it is not 
done.  Why?

> And, yes, fixing the mail clients of "everybody else in the world"
> might be a lovely idea but it is a little impractical to implement.

I find your argument strewn with gaping defects in logic.

-- 
PointedEars

Twitter: @PointedEars2
Please do not cc me. / Bitte keine Kopien per E-Mail.

[toc] | [prev] | [next] | [standalone]

#100704 — Re: Meaning and purpose of the Subject field (was: Ignore error with non-zero exit status)

On Tue, 22 Dec 2015 08:44 am, Jon Ribbens wrote about mail clients that use
the Subject line to thread messages:

> Also: Thunderbird, The Bat!, Eudora, Gnus, Outlook, Outlook Express,
> Pegasus Mail, Pine, Apple Mail, Windows Live Mail, Yahoo Mail,
> Evolution, SquirrelMail, KMail, Windows Mail, etc.

I understand that at least some of those will only use the Subject as a
fallback when other threading information is not available. That's a
reasonable strategy to take.

As for mail clients that *always* and *exclusively* use the subject line to
implement threading, they are horrifically broken. It is completely
unreasonable to insist that people using non-broken tools must change their
habits to support those with completely broken tools.

So as far as I am concerned, if changes of subject line breaks threading for
you, so sad, too bad. Go without threading or use a better mail client.


> Trying to suggest that MUAs should never look at the Subject line for
> threading is, unfortunately, ridiculous. Yes, in theory it shouldn't
> be necessary but in practice enough people are using poor clients that
> don't provide enough context in the proper headers that it can't be
> avoided.

*shrug*

The whole purpose of the change of subject is to indicate in a human-visible
way that the subject of the thread has changed, i.e. that it is a new
thread derived from the old one. If that breaks threading, oh well, it
breaks threading.


> And, yes, fixing the mail clients of "everybody else in the world"
> might be a lovely idea but it is a little impractical to implement.

Less impractical than insisting that "everybody else in the world" must
change their posting habits to suit those using broken mail clients.

The fact is, even if nobody ever changed the subject line, sometimes
threading will be broken. I can't find the energy to care about something
which already only sometimes works.




-- 
Steven

[toc] | [prev] | [next] | [standalone]

#100705 — Re: Meaning and purpose of the Subject field (was: Ignore error with non-zero exit status)

On 2015-12-21, Steven D'Aprano <steve@pearwood.info> wrote:
> On Tue, 22 Dec 2015 08:44 am, Jon Ribbens wrote about mail clients that use
> the Subject line to thread messages:
>> Also: Thunderbird, The Bat!, Eudora, Gnus, Outlook, Outlook Express,
>> Pegasus Mail, Pine, Apple Mail, Windows Live Mail, Yahoo Mail,
>> Evolution, SquirrelMail, KMail, Windows Mail, etc.
>
> I understand that at least some of those will only use the Subject as a
> fallback when other threading information is not available. That's a
> reasonable strategy to take.
>
> As for mail clients that *always* and *exclusively* use the subject
> line to implement threading, they are horrifically broken.

Yes, that would be bizarre and clearly wrong. Are there any such clients?
I wouldn't put it past Microsoft to do such a thing, of course ;-)

> So as far as I am concerned, if changes of subject line breaks
> threading for you, so sad, too bad. Go without threading or use a
> better mail client.

I have no comment on that.

> The whole purpose of the change of subject is to indicate in a human-visible
> way that the subject of the thread has changed, i.e. that it is a new
> thread derived from the old one. If that breaks threading, oh well, it
> breaks threading.

That sounds a bit confused - if the *intention* of changing the
subject line is to create a new thread, then breaking the thread
is not "breaking threading" ;-)

>> And, yes, fixing the mail clients of "everybody else in the world"
>> might be a lovely idea but it is a little impractical to implement.
>
> Less impractical than insisting that "everybody else in the world" must
> change their posting habits to suit those using broken mail clients.

Fortunately I haven't suggested that.

[toc] | [prev] | [next] | [standalone]

#100709 — Re: Meaning and purpose of the Subject field (was: Ignore error with non-zero exit status)

On Mon, Dec 21, 2015 at 4:24 PM, Jon Ribbens
<jon+usenet@unequivocal.co.uk> wrote:
> On 2015-12-21, Steven D'Aprano <steve@pearwood.info> wrote:
>> The whole purpose of the change of subject is to indicate in a human-visible
>> way that the subject of the thread has changed, i.e. that it is a new
>> thread derived from the old one. If that breaks threading, oh well, it
>> breaks threading.
>
> That sounds a bit confused - if the *intention* of changing the
> subject line is to create a new thread, then breaking the thread
> is not "breaking threading" ;-)
>
>>> And, yes, fixing the mail clients of "everybody else in the world"
>>> might be a lovely idea but it is a little impractical to implement.
>>
>> Less impractical than insisting that "everybody else in the world" must
>> change their posting habits to suit those using broken mail clients.
>
> Fortunately I haven't suggested that.

Yes, I only requested that people not change the subject headers for
trivial reasons, by which I meant things like fixing typos (as in the
subject header change that brought about this thread). I also only
intended my request in the context of this forum, which is shared
between Usenet and mailing list users. Changing the subject header to
indicate a change in subject is, of course, fine.

[toc] | [prev] | [next] | [standalone]

#100737 — Re: Meaning and purpose of the Subject field (was: Ignore error with non-zero exit status)

On 2015-12-21 23:24, Jon Ribbens wrote:
> That sounds a bit confused - if the *intention* of changing the
> subject line is to create a new thread, then breaking the thread
> is not "breaking threading" ;-)

I'm pretty sure that the purpose is not to *break* the thread, but to
suggest that the sub-thread's topic has shifted away that of the
parent thread.

-tkc

[toc] | [prev] | [next] | [standalone]

#100715 — Re: Meaning and purpose of the Subject field (was: Ignore error with non-zero exit status)

On 22Dec2015 10:14, Steven D'Aprano <steve@pearwood.info> wrote:
>On Tue, 22 Dec 2015 08:44 am, Jon Ribbens wrote about mail clients that use
>the Subject line to thread messages:
>
>> Also: Thunderbird, The Bat!, Eudora, Gnus, Outlook, Outlook Express,
>> Pegasus Mail, Pine, Apple Mail, Windows Live Mail, Yahoo Mail,
>> Evolution, SquirrelMail, KMail, Windows Mail, etc.
>
>I understand that at least some of those will only use the Subject as a
>fallback when other threading information is not available. That's a
>reasonable strategy to take.
>
>As for mail clients that *always* and *exclusively* use the subject line to
>implement threading, they are horrifically broken.

A big +1 here. Even as big as +2.

>It is completely
>unreasonable to insist that people using non-broken tools must change their
>habits to support those with completely broken tools.
>
>So as far as I am concerned, if changes of subject line breaks threading for
>you, so sad, too bad. Go without threading or use a better mail client.
[...snip...]

Besides, changing the Subject line is _supposed_ to break the threading in 
these contexts: such clients clearly consider the discussion topic (subject) as 
sufficient definition of a thread, and changing the topic should imply a new 
thread to such simplistic clients.

Cheers,
Cameron Simpson <cs@zip.com.au>

[toc] | [prev] | [next] | [standalone]

#100717 — Re: Meaning and purpose of the Subject field

Cameron Simpson <cs@zip.com.au> writes:
> Besides, changing the Subject line is _supposed_ to break the
> threading in these contexts: such clients clearly consider the
> discussion topic (subject) as sufficient definition of a thread, and
> changing the topic should imply a new thread to such simplistic
> clients.

This makes sense for the change from "old" to "new (was: old)",
which nobody was advocating against (after all, there's semantic
content - they wouldn't have changed the subject line if they
didn't consider it a new discussion topic), but I think there is
a reasonable argument that changing it a second time from
"new (was: old)" to "new" is frivolous.

[toc] | [prev] | [next] | [standalone]

#100725 — Re: Meaning and purpose of the Subject field

Random832 wrote:

> This makes sense for the change from "old" to "new (was: old)",
> which nobody was advocating against (after all, there's semantic
> content - they wouldn't have changed the subject line if they
> didn't consider it a new discussion topic), but I think there is
> a reasonable argument that changing it a second time from
> "new (was: old)" to "new" is frivolous.

Nonsense.  It is complete nonsense to carry around the old Subject
for the rest of the thread.

-- 
PointedEars

Twitter: @PointedEars2
Please do not cc me. / Bitte keine Kopien per E-Mail.

[toc] | [prev] | [next] | [standalone]

#100730 — Re: Meaning and purpose of the Subject field (was: Ignore error with non-zero exit status)

On 2015-12-21, Steven D'Aprano <steve@pearwood.info> wrote:

> So as far as I am concerned, if changes of subject line breaks threading for
> you, so sad, too bad. Go without threading or use a better mail client.

Same here.  After getting what is effectively a "F*&# Y*& I'm too lazy
to do things right" from multiple people every day for the past 20
years, I think they deserve to be treated with equal respect.

-- 
Grant Edwards               grant.b.edwards        Yow! I'm thinking about
                                  at               DIGITAL READ-OUT systems
                              gmail.com            and computer-generated
                                                   IMAGE FORMATIONS ...

[toc] | [prev] | [next] | [standalone]

#100732 — Re: Meaning and purpose of the Subject field (was: Ignore error with non-zero exit status)

On Tue, Dec 22, 2015 at 8:17 AM, Grant Edwards <invalid@invalid.invalid> wrote:
> On 2015-12-21, Steven D'Aprano <steve@pearwood.info> wrote:
>
>> So as far as I am concerned, if changes of subject line breaks threading for
>> you, so sad, too bad. Go without threading or use a better mail client.
>
> Same here.  After getting what is effectively a "F*&# Y*& I'm too lazy
> to do things right" from multiple people every day for the past 20
> years, I think they deserve to be treated with equal respect.

Can you elaborate? If there's something I could be doing better in my
communications, I'm happy to entertain it.

[toc] | [prev] | [next] | [standalone]

#100752 — Re: Meaning and purpose of the Subject field (was: Ignore error with non-zero exit status)

On 2015-12-22, Ian Kelly <ian.g.kelly@gmail.com> wrote:
> On Tue, Dec 22, 2015 at 8:17 AM, Grant Edwards <invalid@invalid.invalid> wrote:
>> On 2015-12-21, Steven D'Aprano <steve@pearwood.info> wrote:
>>
>>> So as far as I am concerned, if changes of subject line breaks threading for
>>> you, so sad, too bad. Go without threading or use a better mail client.
>>
>> Same here.  After getting what is effectively a "F*&# Y*& I'm too lazy
>> to do things right" from multiple people every day for the past 20
>> years, I think they deserve to be treated with equal respect.
>
> Can you elaborate? If there's something I could be doing better in my
> communications, I'm happy to entertain it.

I was talking about the general case of people who top-post, send
html-only, misidentified charsets, incorrect file types, attach all
sorts of company logos, "intendended-recipient" boilerplate, and so
on.  Once in a while, you just can't take it any longer and have to do
"the right thing" and let all the people with broken MUAs, NNTP
clients, or brains deal with it...

-- 
Grant Edwards               grant.b.edwards        Yow! Somewhere in DOWNTOWN
                                  at               BURBANK a prostitute is
                              gmail.com            OVERCOOKING a LAMB CHOP!!

[toc] | [prev] | [next] | [standalone]

#100699 — Re: Meaning and purpose of the Subject field (was: Ignore error with non-zero exit status)

On Mon, 21 Dec 2015 14:16:13 -0700, Ian Kelly <ian.g.kelly@gmail.com>
declaimed the following:

>
>I can't specifically recall if I've used any MUA other than Gmail that
>even attempts threading email messages.

	Forte Agent might -- but I don't have it configured for mail servers,
only news servers, so can't be sure. Eudora is configured to /group by
subject/ (with some filtered mailboxes also adding /sort by
unread|priority|date|subject/; but the option for Message List Pane is
"thread by subject" 
-- 
	Wulfraed                 Dennis Lee Bieber         AF6VN
    wlfraed@ix.netcom.com    HTTP://wlfraed.home.netcom.com/

[toc] | [prev] | [next] | [standalone]

#100642 — Re: Ignore error with non-zero exit status (was: How to ignore error with anon-zero exit status)

> (Polite people would *ask* a *question*.)

I am a polite person , sorry if the wording was harsh.

> (“_a non-zero_”, with a space in-between.  “anon” can be misunderstood as
an
> abbreviation for “anonymous”.)

It was a typo.

> Most simple solution for this: Do not use a loop.  More "complicated"
> solution: Use an “if” statement.

I want to stick on to loop and try modifying the code with if. Should I use
some comparison operation with if  ?

[toc] | [prev] | [next] | [standalone]

#100649 — Re: Ignore error with non-zero exit status

Ganesh Pal wrote:

[repaired Subject, restored attribution]

> Thomas 'PointedEars' Lahn wrote:
>> Most simple solution for this: Do not use a loop.  More "complicated"
>> solution: Use an “if” statement.
> 
> I want to stick on to loop and try modifying the code with if. Should I
> use some comparison operation with if  ?

Yes.

Please see, again, <http://www.catb.org/~esr/faqs/smart-questions.html>

-- 
PointedEars

Twitter: @PointedEars2
Please do not cc me. / Bitte keine Kopien per E-Mail.

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | comp.lang.python

csiph-web