headers
erik quanstrom | 1 Jul 2009 04:09
Favicon

ndb/tozone

i need to push my zones to a site that accepts
only bind zones.

for some strange reason i thought it would be
easier write a program to do the conversion from
ndb file than to keep doing it by hand.

i was wrong.

but for very interesting reasons.  it's interesting
to note that a.b.example.com and example.com
may be in the same zone.  this would be like allowing
'/' in file names.  it's impossible to know
without first knowing the complete set of soa
records.

isn't that fun!

anyway, i pushed the results out as a contrib:
quanstro/tozone.  you will need to modify
/sys/src/cmd/ndb/mkfile by hand to complile
the source yourself.

enjoy.

- erik
Permalink | Reply | 0 comments |
headers
J.R. Mauro | 1 Jul 2009 06:31
Picon

Scrolling for plan9port sam

could someone help clean this crappy patch up a bit? i'm drunk and sam
not being able to understand my scrollwheel is really pissing me off.
at least this works despite it being ugly and steeped in cheap
whiskey...

--jorden

diff -r 5f1b36ecd9db src/cmd/samterm/main.c
--- a/src/cmd/samterm/main.c	Tue Jun 09 09:26:13 2009 -0700
+++ b/src/cmd/samterm/main.c	Wed Jul 01 00:29:48 2009 -0400
 <at>  <at>  -142,6 +142,10  <at>  <at> 
 					scroll(which, 3);
 				else
 					menu3hit();
+			} else if((mousep->buttons&8)) {
+				scroll(nwhich, 1);
+			} else if((mousep->buttons&16)) {
+				scroll(nwhich, 3);
 			}
 			mouseunblock();
 		}
diff -r 5f1b36ecd9db src/cmd/samterm/scroll.c
--- a/src/cmd/samterm/scroll.c	Tue Jun 09 09:26:13 2009 -0700
+++ b/src/cmd/samterm/scroll.c	Wed Jul 01 00:29:48 2009 -0400
 <at>  <at>  -100,7 +100,7  <at>  <at> 
 void
 scroll(Flayer *l, int but)
 {
-	int in = 0, oin;
+	int in = 0, oin, scw = 0;
(Continue reading)

Permalink | Reply | 1 comment |
headers
Richard Miller | 1 Jul 2009 09:47

Re: 9p on Yeeloong (gNewSense Linux)

> lucio <at> proxima.alt.za:

> but I know that I haven't yet
> found a CPU architecture I dislike more then the Intel i386

Ever tried the 6502?
Permalink | Reply | 0 comments |
headers
Aaron W. Hsu | 1 Jul 2009 10:56
Picon
Gravatar

Guide to using Acme effectively?

Hello everyone,

I am taking the Acme workflow for a spin. I am coming from Emacs and Vi. I  
have read the manual and the original paper discussing the motivations  
behind its design. I am familiar with mouse based editing in the NEdit  
style to ane extent that I can use it properly with NEdit, but I am having  
trouble understanding just how the workflows of Acme work with real world  
type questions. Is there anything out there that would help me connect  
some of the tasks I often wish to do with the efficient Acme approach? I'm  
missing small things, like how to select and move all the text in one  
window to another in a fast manner, but I'm also missing big things like  
how to quickly navigate through to specific parts of a file and how to  
reduce redundancy of typing and movement.

Does anyone have any suggestions?

	Aaron W. Hsu

--

-- 
Of all tyrannies, a tyranny sincerely exercised for the good of its  
victims may be the most oppressive. -- C. S. Lewis
Permalink | Reply | 71 comments |
headers
erik quanstrom | 1 Jul 2009 16:31
Favicon

Re: Guide to using Acme effectively?

> some of the tasks I often wish to do with the efficient Acme approach? I'm
> missing small things, like how to select and move all the text in one
> window to another in a fast manner, 

there are a couple of options "Edit ," will select all the text in
a window.  but "|cat $file" will replace the dot with the contents
of $file.  i'm not sure that this is either non-obvious or helpful.
that's not something i do with acme.

> but I'm also missing big things like
> how to quickly navigate through to specific parts of a file and how to
> reduce redundancy of typing and movement.

i'm not sure what kind of text file you're talking about.
i generally put unique text for each of the sections i'm
currently intereted in in the tag.

- erik
Permalink | Reply | 0 comments |
headers
john | 1 Jul 2009 17:58
Picon
Favicon

Re: Guide to using Acme effectively?

> [...] but I'm also missing big things like
> how to quickly navigate through to specific parts of a file and how to
> reduce redundancy of typing and movement.
> 

Here's how I navigate through my various files in acme:

The old standard, the arrow keys.  Type ":100" in the tag and
left-click to go to line 100.  Mid-click and hold on the scrollbar to
scroll efficiently.  Type text in the tag and left-click to search.

If you're going to complain about redundancy of movement regarding the
hand to the keyboard, acme might not be for you.  I think Tog's
conclusions (the single set of studies put forth whenever this thing
comes up) are poorly made and that there is a lot to be said for
efficient keyboard use, but acme really works quite nicely for me--I
don't feel that I'm wasting time mousing around, for the most part.

Just give it a shot.  There's no magical trick to using acme quickly
and effectively; just like any editor, you'll have to get used to it
and figure out how you want to use it.

John
Permalink | Reply | 61 comments |
headers
Charles Forsyth | 1 Jul 2009 18:46

Re: Guide to using Acme effectively?

>I think Tog's conclusions (the single set of studies put forth whenever this thing
>comes up) are poorly made ...

it turns out that there is rather older work that supports
much the same conclusion, which i probably saw mentioned in HCI Remixed,
since that's one i've read recently.
Permalink | Reply | 59 comments |
headers
J. R. Mauro | 1 Jul 2009 20:53
Picon

Re: Guide to using Acme effectively?


On Jul 1, 2009, at 12:46, Charles Forsyth <forsyth <at> terzarima.net> wrote:

>> I think Tog's conclusions (the single set of studies put forth  
>> whenever this thing
>> comes up) are poorly made ...
>
> it turns out that there is rather older work that supports
> much the same conclusion, which i probably saw mentioned in HCI  
> Remixed,
> since that's one i've read recently.
>

I've seen a couple of independent time trials from the mid 80s that  
supported the same conclusion.
Permalink | Reply | 58 comments |
headers
J. R. Mauro | 1 Jul 2009 20:54
Picon

Re: Guide to using Acme effectively?


On Jul 1, 2009, at 11:58, john <at> csplan9.rit.edu wrote:

>> [...] but I'm also missing big things like
>> how to quickly navigate through to specific parts of a file and how  
>> to
>> reduce redundancy of typing and movement.
>>
>
> Here's how I navigate through my various files in acme:
>
> The old standard, the arrow keys.  Type ":100" in the tag and
> left-click to go to line 100.  Mid-click and hold on the scrollbar to
> scroll efficiently.  Type text in the tag and left-click to search.

There's also the End key.

>
>
> If you're going to complain about redundancy of movement regarding the
> hand to the keyboard, acme might not be for you.  I think Tog's
> conclusions (the single set of studies put forth whenever this thing
> comes up) are poorly made and that there is a lot to be said for
> efficient keyboard use, but acme really works quite nicely for me--I
> don't feel that I'm wasting time mousing around, for the most part.
>
> Just give it a shot.  There's no magical trick to using acme quickly
> and effectively; just like any editor, you'll have to get used to it
> and figure out how you want to use it.
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
blstuart | 1 Jul 2009 21:24

Re: Guide to using Acme effectively?

> On Jul 1, 2009, at 12:46, Charles Forsyth <forsyth <at> terzarima.net> wrote:
> 
>>> I think Tog's conclusions (the single set of studies put forth  
>>> whenever this thing
>>> comes up) are poorly made ...
>>
>> it turns out that there is rather older work that supports
>> much the same conclusion, which i probably saw mentioned in HCI  
>> Remixed,
>> since that's one i've read recently.
>>
> 
> I've seen a couple of independent time trials from the mid 80s that  
> supported the same conclusion.

I won't dispute the conclusions on the time criteria.
I'm just not sure time is the right thing to measure.
I spend relatively little of my time actually typing
or moving the cursor, etc.  The majority of my time
is spent thinking, so I'm much more interested in
what distracts me less and what causes the least
irritation.  And I do find moving my hand back and
forth between the keyboard and mouse to be a
bit irritating.  I will say, however, that I find acme
to be the least irritating of the pointer-based
applications I've used.

BLS
(Continue reading)

Permalink | Reply | 22 comments |

Gmane