9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "boyd, rounin" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] sam chatter
Date: Sun,  6 Jul 2003 05:15:14 +0200	[thread overview]
Message-ID: <002301c3436c$d1cb5ac0$d2944251@insultant.net> (raw)
In-Reply-To: <8a9325cdd68f97de578300418820a09d@mightycheese.com>

no, i don't want to pull on the edge of a transperant object.

that's what 'resize' is for.



  reply	other threads:[~2003-07-06  3:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-04  9:21 steve.simon
2003-07-04 15:42 ` Derek Fawcus
2003-07-05 18:34 ` Dan Cross
2003-07-05 18:44   ` rob pike, esq.
2003-07-06  3:15     ` boyd, rounin [this message]
2003-07-07  8:42       ` John Murdie
2003-07-07 10:56         ` John Murdie
2003-07-07 15:11         ` Douglas A. Gwyn
2003-07-07 15:54           ` rob pike, esq.
2003-07-07 20:42             ` boyd, rounin
2003-07-05 22:18   ` Bruce Ellis
2003-07-08  9:05   ` Markus Friedl
2003-07-08 13:38     ` andrey mirtchovski

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='002301c3436c$d1cb5ac0$d2944251@insultant.net' \
    --to=boyd@insultant.net \
    --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).