9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Sander van Dijk" <a.h.vandijk@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] 'stuck' windows.
Date: Sat, 21 Jun 2008 20:21:17 +0200	[thread overview]
Message-ID: <ba0d3bc70806211121y59be548ycb41a958c10a8ac5@mail.gmail.com> (raw)

Hi,

When I open a window in rio, run 9fat:, and then exit, the window gets
'stuck'. That is, it just sits there, I can't type anything in it
anymore.
Apparently, it is waiting for dossrv to exit (which gets started by
9fat:): when I open a second window, and run 'kill dossrv | rc', the
first window disappears.
Also, when this first window is still waiting, and I run 9fat: from a
second window, I can exit the second window without problems (because
9fat: only starts dossrv if it isn't there already, and in this case
the first window has already started it).

This (being unable to exit the window without killing dossrv) seems a
bit strange to me. I can of course destroy the window using the
'Delete' option in rio's menu, but I think that's not the 'right' way
to do it.
Am I doing something wrong (is there a way I can actually exit said
window without killing dossrv)?
Has it always been this way (I believe I vaguely remember that
somewhere in the past I could exit from the window that started dossrv
without problems)?

Greetings, Sander.



             reply	other threads:[~2008-06-21 18:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-21 18:21 Sander van Dijk [this message]
2008-06-21 21:39 ` erik quanstrom
2008-06-22  7:36   ` Sander van Dijk
2008-06-21 23:48 ` Pietro Gagliardi
2008-06-22  0:44   ` Russ Cox
2008-06-22  0:50 ` Russ Cox
2008-06-22  7:45   ` Sander van Dijk
2008-06-22 11:47     ` erik quanstrom
2008-06-22 11:59       ` erik quanstrom
2008-06-22 11:50     ` Russ Cox
2008-06-22 12:58       ` Sander van Dijk
2008-06-22 14:22         ` Russ Cox
2008-06-23 14:50           ` Dave Eckhardt
2008-06-24  8:53           ` Sander van Dijk

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=ba0d3bc70806211121y59be548ycb41a958c10a8ac5@mail.gmail.com \
    --to=a.h.vandijk@gmail.com \
    --cc=9fans@9fans.net \
    /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).