Gnus development mailing list
 help / color / mirror / Atom feed
From: Justin Sheehy <justin@linus.mitre.org>
Subject: Re: Loss of ticks and marks
Date: 05 Apr 1999 11:28:18 -0400	[thread overview]
Message-ID: <glmvhfbkrxp.fsf@caffeine.mitre.org> (raw)
In-Reply-To: Alexandre Oliva's message of "04 Apr 1999 07:57:37 -0300"

Alexandre Oliva <oliva@dcc.unicamp.br> writes:

> I thought code that must not be interrupted would be protected against
> C-g, so that I couldn't screw things up with the keyboard even if I
> wanted :-)

It's not code that _must_ not be interrupted, it is code that _should_ 
not be interrupted.  It's not a good idea in general, but could be
necessary in some cases.  If you send a break signal, you should plan
on dealing with the consequences.

Protecting all sorts of code from C-g would make it very difficult for 
users to deal with a situation that actually hung their emacs.

No one prevents you from pulling your computer's plug out of the wall, 
but that doesn't make it a good idea...

-- 
Justin Sheehy

In a cloud bones of steel.
  




  reply	other threads:[~1999-04-05 15:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-21  7:59 Alexandre Oliva
1999-03-28 16:41 ` Lars Magne Ingebrigtsen
1999-03-29  0:56   ` Alexandre Oliva
1999-04-02 13:53     ` Lars Magne Ingebrigtsen
1999-04-04 10:57       ` Alexandre Oliva
1999-04-05 15:28         ` Justin Sheehy [this message]
1999-04-05 21:24           ` Alexandre Oliva
1999-04-05 21:34             ` Justin Sheehy
1999-04-05 22:08               ` Dmitry Yaitskov
1999-04-06 21:35               ` Alexandre Oliva
1999-04-06 22:02                 ` Alan Shutko
1999-04-13  7:08           ` Hrvoje Niksic
1999-04-17  6:20         ` Lars Magne Ingebrigtsen
1999-04-17 20:27           ` Alexandre Oliva

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=glmvhfbkrxp.fsf@caffeine.mitre.org \
    --to=justin@linus.mitre.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).