[TxMt] os forking doesn't work from a TextMate command?

Kevin Ballard kevin at sb.org
Fri Sep 16 18:23:35 UTC 2005

Gerd Knops's double-fork trick is probably what you want (generally  
referred to as "daemonizing"). The reason for this is when you run a  
command, TextMate waits for the command to finish, and apparently  
when you fork it's still waiting for the forked process to finish.  
But double-forking (and probably closing file descriptors) should  
solve that issue.

On Sep 16, 2005, at 11:31 AM, Kumar McMillan wrote:

> Does anyone have an idea why using Python's os.fork() to start a
> daemon process from within TextMate doesn't work?  Why would I want to
> do this, you ask?  It seems the most logical way to browse local
> Python documentation (via pydoc).  The doc commands that already exist
> are great if you know exactly what you're looking for, but I still
> find myself starting up the doc server every now and again to go
> poking around.  My thought was to run a command "Browse Python
> Documentation" or whatever from TextMate that opens a web browser to
> the local server.  If the server isn't running then it needs to start
> lazily.  This works great from the shell.  From within TextMate the
> server starts fine but the process doesn't appear to be properly
> forked because TextMate just hangs like it's waiting.  The script is
> attached for reference.

Kevin Ballard
kevin at sb.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2378 bytes
Desc: not available
URL: <http://lists.macromates.com/textmate/attachments/20050916/066d638c/attachment.p7s>

More information about the textmate mailing list