From: Linas Vepstas <linasvepstas@gmail.com>
To: vimml@selgrad.org
Cc: guile-user@gnu.org
Subject: Re: scm_shell in C-Thread - Quit vs. Terminal Corruption
Date: Fri, 16 Oct 2009 21:42:49 -0500 [thread overview]
Message-ID: <3ae3aa420910161942y67d04163kb270dba9b05f61b3@mail.gmail.com> (raw)
In-Reply-To: <20091016190925.GA26534@shoikan>
2009/10/16 <vimml@selgrad.org>:
> application and guile). When I enter
> (quit)
> in the terminal scm_shell calls exit(), which does not care much for my
> application cleanup.
wouldn't atexit() solve this problem?
--linas
next prev parent reply other threads:[~2009-10-17 2:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 19:09 scm_shell in C-Thread - Quit vs. Terminal Corruption vimml
2009-10-17 2:42 ` Linas Vepstas [this message]
2009-10-17 17:36 ` kai.selgrad
2009-10-18 15:05 ` Neil Jerram
2009-10-18 15:48 ` kai.selgrad
2009-10-17 2:49 ` Linas Vepstas
2009-10-17 12:44 ` Ludovic Courtès
2009-10-17 17:43 ` vimml
2009-10-17 17:47 ` vimml
2009-10-17 12:52 ` Ludovic Courtès
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3ae3aa420910161942y67d04163kb270dba9b05f61b3@mail.gmail.com \
--to=linasvepstas@gmail.com \
--cc=guile-user@gnu.org \
--cc=vimml@selgrad.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 read-only IMAP folder(s) and NNTP newsgroup(s).