9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bug in libcomplete?
Date: Sat, 14 Feb 2004 11:49:39 -0500	[thread overview]
Message-ID: <5b31fe1f39da38505a559c9a6b2a0291@plan9.bell-labs.com> (raw)
In-Reply-To: <D85938EA-5F0B-11D8-A6FF-000A95B984D8@mightycheese.com>

[-- Attachment #1: Type: text/plain, Size: 24 bytes --]

done and sources updated

[-- Attachment #2: Type: message/rfc822, Size: 3012 bytes --]

From: Rob Pike <rob@mightycheese.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bug in libcomplete?
Date: Sat, 14 Feb 2004 08:35:48 -0800
Message-ID: <D85938EA-5F0B-11D8-A6FF-000A95B984D8@mightycheese.com>

no, the bug is rio. it doesn't set /dev/wdir in this case.

add
	if(dir)
		w->dir = estrdup(dir)
after the call to wsetname() in new() in /sys/src/cmd/rio/rio.c

-rob

On Saturday, February 14, 2004, at 07:15 AM, andrey mirtchovski wrote:

> libcomplete depends on 'cd' to find our which directory the user is
> in.  this breaks its behaviour with respect to programs which
> implicitly chdir when started, one example is the 'window' command --
> cd /tmp and run window, hit the complete key and you'll get the
> contents of your $home.  The following example is a freshly created
> window in the /tmp directory:
>
>
>
> 	home% pwd
> 	/tmp
> 	[bin/ lib/ tmp/]
> 	home% cd `{pwd}
> 	[58 files]
> 	home%
>
> pwd shows i'm in /tmp, completion thinks i'm in $home, then the same
> thing after "cd `{pwd}"
>
> andrey

  reply	other threads:[~2004-02-14 16:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-14 15:15 andrey mirtchovski
2004-02-14 16:35 ` Rob Pike
2004-02-14 16:49   ` David Presotto [this message]
2004-02-14 18:18     ` andrey mirtchovski
2004-02-14 17:56       ` andrey mirtchovski
2004-02-14 19:09       ` Rob Pike
2004-02-14 21:57         ` boyd, rounin
2004-02-14 19:01 Rob 'Commander' Pike

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=5b31fe1f39da38505a559c9a6b2a0291@plan9.bell-labs.com \
    --to=presotto@closedmind.org \
    --cc=9fans@cse.psu.edu \
    /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).