From: Paul Lalonde <plalonde@telus.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Long tags in acme
Date: Mon, 14 Mar 2005 17:17:26 -0800 [thread overview]
Message-ID: <297c1afb3ee490d7adf706a6a397fb76@telus.net> (raw)
In-Reply-To: <cfa3880436f77973b812693704886ce1@telus.net>
I lied. I didn't do the other work I should have been doing.
Here's a patch that adds the Expand toggle, if anyone else wants it.
Paul
Index: exec.c
===================================================================
RCS file: /cvs/plan9/src/cmd/acme/exec.c,v
retrieving revision 1.20
diff -r1.20 exec.c
23a24
> void togexp(Text*, Text*, Text*, int, int, Rune*, int);
79a81
> static Rune LExpand[] = { 'E', 'x', 'p', 'a', 'n', 'd', 0 };
89a92
> { LExpand, togexp, FALSE, XXX, XXX },
969a973,986
> togexp(Text *et, Text *_0, Text *_1, int _2, int _3, Rune *_4, int _5)
> {
> int colidx, winidx;
> dodollarsigns = !dodollarsigns;
> for(colidx = 0; colidx < row.ncol; ++colidx)
> {
> for(winidx = 0; winidx < row.col[colidx]->nw; ++winidx)
> {
> winsettag(row.col[colidx]->w[winidx]);
> }
> }
> }
>
> void
On 14-Mar-05, at 4:57 PM, Paul Lalonde wrote:
> This seems not bad; but it still needs the $env trick: Try editing
> deep in a tree like /Users/plalonde/dev/tuna/RT/contingency/... and
> you quickly find yourself wasting most of the tag space, which
> multi-line doesn't help: you still wind up with piles of tag you wish
> you could put to better use.
> A useful thing would be to expose the $env expansion switch on a verb,
> maybe Expand or somesuch, for those times when you do need to see the
> path.
> I have a partial hack done for this, but now have to figure out how to
> re-interpret and update all the tags; I have other work to do before
> that.
>
> Paul
>
> On 14-Mar-05, at 4:11 PM, andrey mirtchovski wrote:
>
>>> I already hate the little
>>> window handles,
>>
>> how about a resize-able window titlebar? i.e. you can make it as
>> many lines as you want to accomodate all your text by just dragging
>> the lower line of the titlebar.
>>
>
prev parent reply other threads:[~2005-03-15 1:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 18:43 Paul Lalonde
2005-03-14 19:04 ` Russ Cox
2005-03-14 19:45 ` andrey mirtchovski
2005-03-14 21:30 ` Rob Pike
2005-03-14 21:57 ` rog
2005-03-14 22:04 ` Russ Cox
2005-03-14 23:50 ` Heiko Dudzus
2005-03-15 0:05 ` Paul Lalonde
2005-03-15 0:11 ` andrey mirtchovski
2005-03-15 0:57 ` Paul Lalonde
2005-03-15 1:17 ` Paul Lalonde [this message]
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=297c1afb3ee490d7adf706a6a397fb76@telus.net \
--to=plalonde@telus.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).