To clarify: I did spend quite a bit of time diving into `sed` myself (experiments, tests, etc.) and wrote an initial draft in French.
I then used ChatGPT to help me structure and refine the article in English to reach more people. But the core ideas and understanding come from my own exploration.
That said, I understand the concern, and for future articles I'll try to rely less on that kind of tooling for structure.
Happy to clarify or go deeper on any part of the article if needed.
This is the true power of vim. Even now decades later the unix toolbelt holds up, and is still unmatched for productivity.
Vim is in the end just a small piece of the puzzle. You use small tools for your problem, mix and match.
Its kind of like functional programming. Compose and reduce.
Then I realized I already knew Perl (and Perl one-liners), so there it sat unused on the shelf.
:loop N; s/\n[[:space:]]\+/ /g; t loop; p
In sam, the equivalent is: x/(.+\n)*/ x/\n */ c/ /
It reads like this: loop over paragraphs of non-empty lines, loop over newline followed by spaces, replace with a single space. It's surprisingly close to SQL in its eloquence.Another example:
N; h; s/\n/->/g ;p; g; D
In sam, an equivalent would be {
1,$-2 x/./ {
a/->/
/./ t .
}
$-1 d
}
Again, it's readable from top to bottom: from the first line to the second from the end, loop over each symbol, put "->" after it and copy the next symbol next to it; delete the last line.Let's see how far we can get. Another example:
N; h; s/\n/->/g; p; G; D
In sam, an equivalent would be: {
d
1,$-2 x/./ {
1,/./ x/.|\n/ {
g/./ t $
g/\n/ $ c/->/
}
$ c/\n/
}
}
It reads like this: delete the whole thing; from the first line to the second from the end, loop over each character; on each iteration, from the first line to the next character, run an inner loop over each character or newline; if it's a character, put it at the end; otherwise, put "->" at the end; once the inner loop is done, put a newline at the end.The final example from the post is too long to have it here (15 lines). Here's just the sam equivalent for it:
x/(.+\n)+|\n+/ {
g/./ x/\n/ c/ /
v/./ c/\n/
}
It reads like this: loop over paragraphs of non-empty lines or sequences of newline characters; if it has any symbol (that is, it's a paragraph), replace each newline symbol with a space; if it doesn't have a symbol (that is, it's a sequence of newline symbols), replace it with a single newline.What I have learned from this is that a tool with limited but well-chosen primitives is more convenient than a universal state machine.
(My examples may not be the exact same algorithms, since I do not understand (or need) sed concepts, but they do produce the same output.)
Is there a port to Apple silicon?
I find the X command extremely powerful, and can't see any way to
have a streaming implementation that will look at multiple files
simultaneously.
> Is there a port to Apple silicon?plan9port works on it. It compiled without any errors on my Apple Silicon Mac.
[1]: https://9fans.github.io/plan9port/man/man1/ssam.html
[2]: https://9fans.github.io/plan9port
[3]: https://9fans.topicbox.com/groups/9fans/Tdf6095a105816f01-M3...
So if I understand correctly, it’s selection-based, right? You first select a region, and then you can apply further selections inside it?
So you kind of build nested selections to match exactly what you want (almost like a conditional tree).
And then you apply operations on the current selection
For example substitution with something like c/PATTERN/, is that correct?
. The dot (".") never matches newlines, which keeps line-oriented idioms from accidentally spanning newlines [1]
. Changes must be sequential and non-overlapping (that's why I deleted the whole thing before processing in the third example).
. Sam matches only the original input, not past changes.
. Addresses (expressions before commands) select a single range, x commands select multiple ranges and loop over it.
[1]: https://p9f.org/sys/doc/sam/sam.html, Regular expressions