> * I did try using 'send' but it gives me a ?bad delimiter `e' error.
send is a command on the middle-click menu in samterm, not part of the
sam language.
--
9fans: 9fans
Permalink:
> The sam window is not always responsive to commands. Under what specific
> conditions is this the case?
I can think of a few cases:
* You issued an I/O command (shell, read file, write file, etc.) and
it's still in progress (there will always be output you can wait for
in these cases, e.g.
> #!/bin/sed '/^#/d'
apologies. quotes do not belong there.
#!/bin/sed /^#/d
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T10b1d559ae7d981e-Mfff65af821d77519fd6c8034
Delivery options:
# is, for better or for worse, an address in sam:
#n The empty string after character n; #0 is the beginning
of the file.
If you're talking about running the script with ^, it's just an
executable. You can put whatever you want in the shebang line; I tend
to use the
> I have yet gotten to this usage of "g" after "s".
The key difference here is not in the behavior of suffixed 'g', but in
how selections are made and operated on in the first place.
Ed's "selection" (aka dot, as you can reference it with '.') is always
a full, single line. It can *iterate* over
> In any case, Plan 9's ed has a nice "browse" command which sam can't match. I
> used to issue "0bn", then just "b" once per page. Or, if you don't want line
> numbers, leave out the "n".
"+,+20p" does it. Doesn't work near the end of the file, though; not
sure if that can be improved within
> often switching files, Sam's menus are practically worse than Acme
> The weakest point in sam -d is still switching files, you have to type
> whole filenames
X/pathregex/b
sam will dump a warning about an expected blank, but it'll otherwise
do what you hope for (switch to the open file
