From: YAMANASHI Takeshi <uncover@beat.cc.titech.ac.jp>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] acme design
Date: Sat, 5 Jun 2004 15:09:14 +0900 [thread overview]
Message-ID: <dfef7628ab8857769fb76d9bba79aa90@orthanc.cc.titech.ac.jp> (raw)
In-Reply-To: <7a15e66ba352a47776e1561e3a9256c0@vitanuova.com>
> as someone else said, if you want more text than will fit in a tag,
> just click on "New" and use it as a scratch window.
As someone else said, Edit commands typed in the New'ly
created scratch window can't be applied to contents in
other windows, if I'm correct. And when everytime I want
to execute one of them, snarf&paste it into the intended
tagline and execute it is painful.
Rather, I have something like this at the top of a Zerox'ed
window and use them.
| |-----------------------------------------------
[=]/usr/nashi/src/9skk.c Del Snarf | Look
| |-----------------------------------------------
| |/*
| | Edit 5,10x/hogefuga what ever long edit commands here
| | Edit x/yet another long commands here
| |*/
| |-----------------------------------------------
[=]/usr/nashi/src/9skk.c Del Snarf | Look Edit =
| |-----------------------------------------------
| |void
| |main(int argc, char **argv)
| | ...
# Sorry to disturb you for merely showing my custom.
> there's not enough space in a tag for scrollbars.
Agreed. But autoscrolling horizontaly without any scrollbar
when typing past the right end of a tagline could be helpful.
--
next prev parent reply other threads:[~2004-06-05 6:09 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 8:07 cej
2004-06-03 8:52 ` plan9
2004-06-03 12:38 ` [9fans] unix acme (was: acme design) Axel Belinfante
2004-06-03 13:53 ` [9fans] acme design rog
2004-06-03 13:55 ` rog
2004-06-05 6:09 ` YAMANASHI Takeshi [this message]
2004-06-05 10:07 ` Charles Forsyth
2004-06-05 13:48 ` YAMANASHI Takeshi
2004-06-05 15:50 ` Rob Pike
2004-06-06 2:23 ` YAMANASHI Takeshi
2004-06-06 3:25 ` Rob Pike
2004-06-06 7:24 ` YAMANASHI Takeshi
2004-06-06 8:54 ` vdharani
-- strict thread matches above, loose matches on Subject: below --
2004-06-07 8:22 cej
2004-06-07 13:43 ` Russ Cox
2004-06-07 13:47 ` boyd, rounin
2004-06-04 11:22 cej
2004-06-04 9:12 cej
2004-06-03 11:21 cej
2004-06-03 14:59 ` a
2004-06-03 8:37 cej
2004-06-03 7:58 cej
2004-06-03 8:54 ` Kenji Okamoto
2004-06-02 12:57 cej
2004-06-02 13:20 ` a
2004-06-02 15:18 ` plan9
2004-06-03 13:48 ` rog
2004-06-03 14:17 ` lucio
2004-06-03 14:34 ` rog
2004-06-03 15:38 ` kiwane
2004-06-03 15:45 ` rog
2004-06-04 9:19 ` Bengt Kleberg
2004-06-04 10:29 ` Axel Belinfante
2004-06-03 0:54 ` Kenji Okamoto
2004-06-03 0:56 ` Kenji Okamoto
2004-06-03 8:35 ` WLad
2004-06-03 8:40 ` vdharani
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=dfef7628ab8857769fb76d9bba79aa90@orthanc.cc.titech.ac.jp \
--to=uncover@beat.cc.titech.ac.jp \
--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).