Re: Hooking Mechanism when Entering and Leaving a Try Block

References	(1 earlier) <CALwzidkBoDo1TZj2CWfimYtagtArN9r9dvw1Ke9HqcthdipV4Q@mail.gmail.com> <55CB6EAC.5040004@mail.de> <CAPTjJmoqg9sA-QB3RoRPQFx1osOYyBzff-UX8f2zrzxWpt7sYQ@mail.gmail.com> <55CB9425.5050109@mail.de> <mqgbpa$ffi$1@ger.gmane.org>
Date	2015-08-13 10:45 +1000
Subject	Re: Hooking Mechanism when Entering and Leaving a Try Block
From	Chris Angelico <rosuav@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.153.1439426727.3627.python-list@python.org> (permalink)

Show all headers | View raw

On Thu, Aug 13, 2015 at 6:54 AM, Mark Lawrence <breamoreboy@yahoo.co.uk> wrote:
> On 12/08/2015 19:44, Sven R. Kunze wrote:
>>
>> On 12.08.2015 18:11, Chris Angelico wrote:
>>>
>>> (Please don't top-post.)
>>
>>
>> Is this some guideline? I actually quite dislike pick somebody's mail to
>> pieces. It actually pulls things out of context. But if this is a rule
>> for this, so be it.
>>
>
> The rules here are very simple.  Snip what you don't wish to reply to (yes I
> know I forget sometimes), intersperse your answers to what you do want to
> respond to.

As Mark says, the key is to intersperse your answers with the context.
In some email clients, you can highlight a block of text and hit
Reply, and it'll quote only that text. (I was so happy when Gmail
introduced that feature. It was the one thing I'd been most missing
from it.)

ChrisA

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Hooking Mechanism when Entering and Leaving a Try Block Chris Angelico <rosuav@gmail.com> - 2015-08-13 10:45 +1000

csiph-web