[9fans] Long tags in acme

[9fans] Long tags in acme

[Paul Lalonde]

I'm sure I'm missing something.
I'm being forced to work with obscenely long paths that I don't
control, and that's causing my tags to overflow the width of the
columns.  Short of making my acme window span another monitor is there
something I can do to have it abbreviate the filenames? I'm running a
recent p9port on OS X.

Thanks,
	Paul

Re: [9fans] Long tags in acme

[Russ Cox]

There is a tagged version of acme in the CVS repository that
abbreviates tags using environment variables, but it's not
the default because doing it right requires letting the plumber
know about environment variables too.

I typically create some symlinks and just use those, although
it can get confusing when you end up with windows using
both the symlink'ed name and the real name.

Russ

On Mon, 14 Mar 2005 10:43:12 -0800, Paul Lalonde <plalonde@telus.net> wrote:
> I'm sure I'm missing something.
> I'm being forced to work with obscenely long paths that I don't
> control, and that's causing my tags to overflow the width of the
> columns.  Short of making my acme window span another monitor is there
> something I can do to have it abbreviate the filenames? I'm running a
> recent p9port on OS X.
>
> Thanks,
>         Paul
>
>

Re: [9fans] Long tags in acme

[andrey mirtchovski]

> I'm sure I'm missing something.
> I'm being forced to work with obscenely long paths that I don't
> control, and that's causing my tags to overflow the width of the
> columns.  Short of making my acme window span another monitor is there
> something I can do to have it abbreviate the filenames? I'm running a
> recent p9port on OS X.
>
> Thanks,
> 	Paul

you can think of the titlebar as a multi-line window and switch
between lines with the mouse -- left click on an acme titlebar with a
file name (or commands) wider than the window itself and move it down
and up to switch between the different 'lines' (though the '\n' is
only implicit).

Re: [9fans] Long tags in acme

[Rob Pike]

tags should fold.

Re: [9fans] Long tags in acme

[rog]

folding'd be nice, but does anyone else get kinda mesmerised
by the sight of all those almost-identical path prefixes?

even if tags folded i reckon i'd still find that a problem.

i was wondering earlier whether a possible solution might
be to add an Alias primitive; e.g.

Alias /mnt/term/n/c/usr/rog/c/other/blah/diddoodah blah

then any pathnames prefixed by the first argument
would show up as non-rooted pathnames prefixed by the
second (relative pathnames not really being used in acme tags).

similar in a way to the environment variable thing, but
more explicit; also similar to russ's symlink trick or
doing a local bind, but means that plumbing would
still work seamlessly.

i bet it'd be really quite simple to implement too.
there's probably a good reason why it's a bad idea...

Re: [9fans] Long tags in acme

[Russ Cox]

I put the dollar sign code back in as acme -'$' in plan9port.
The CVS tag version had gotten quite out-of-date.
It's undocumented and intentionally hard to type, but
maybe someone will start there and figure out a better
solution to the problem.

There's a big comment on it explaining why it's not such
a great idea, but at the same time I know a handful of people
have found it useful and were maintaining it themselves.

I've recently moved to a 1024x768 laptop screen (from a
large 1400x1050) and spent a half hour today making things
fit better on my screen: smaller fonts, different acme.dump,
etc.  I also tried the $env tags again.  They're a big win on
the small screen.  Folding tag lines might be sufficient in my
case, but the $env tags are easier to implement.  At least
now I can run with multiple columns *and* see the Put verb
in my tags.

Russ

Re: [9fans] Long tags in acme

[Heiko Dudzus]

> I've recently moved to a 1024x768 laptop screen (from a
> large 1400x1050) and spent a half hour today making things
> fit better on my screen: smaller fonts, different acme.dump,
> etc.  I also tried the $env tags again.  They're a big win on
> the small screen.  Folding tag lines might be sufficient in my
> case, but the $env tags are easier to implement.  At least
> now I can run with multiple columns *and* see the Put verb
> in my tags.

How about to make button 1 to scroll the tag line to the left and
button 3 to scroll it to the left?

Sure, it would need reserved space in the tag line where one could
commit the "click", because button 1&3 on the tag verbs means
something else.  (perhaps a square on the righthand side of the tag
line; like the one on the left side for positioning?)

Re: [9fans] Long tags in acme

[Paul Lalonde]

I'm most partial to Russ' $env tag, to date.
Alias is complicated by the fact that alias interpretation would have
to be added to the meaning of text selected in the tag; that's in
addition to the environment variable handling that needs to go into the
plumber anyhow.
As for special regions to click to scroll, I already hate the little
window handles, I'd rather see fewer special places than more.  Tag
scrolling with the first mouse button works fine for those (now) rare
cases where the tag is too long.

Paul



On 14-Mar-05, at 3:50 PM, Heiko Dudzus wrote:

>> I've recently moved to a 1024x768 laptop screen (from a
>> large 1400x1050) and spent a half hour today making things
>> fit better on my screen: smaller fonts, different acme.dump,
>> etc.  I also tried the $env tags again.  They're a big win on
>> the small screen.  Folding tag lines might be sufficient in my
>> case, but the $env tags are easier to implement.  At least
>> now I can run with multiple columns *and* see the Put verb
>> in my tags.
>
> How about to make button 1 to scroll the tag line to the left and
> button 3 to scroll it to the left?
>
> Sure, it would need reserved space in the tag line where one could
> commit the "click", because button 1&3 on the tag verbs means
> something else.  (perhaps a square on the righthand side of the tag
> line; like the one on the left side for positioning?)
>

Re: [9fans] Long tags in acme

[andrey mirtchovski]

> 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.

Re: [9fans] Long tags in acme

[Paul Lalonde]

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.
>

Re: [9fans] Long tags in acme

[Paul Lalonde]

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.
>>
>