ralph

15 ms·

1.
by ralph 10y ago
I find searching bash(1) just fine with less(1) and do it quite often. The groff mailing list, the main discussion point for all things troff, is slowly chipping away at adding more semantic information to man pages. The BSDs have been maki
2.
by ralph 10y ago
`info foo | less' has it produce the whole "page" as plain text, suitable for easy reading and regexp searching.
3.
Google+ accepts and ignores parameters in URL path segments(plus.google.com)
2 points by ralph 13y ago|0 comments
4.
by ralph 13y ago
If it's not thought interesting then it won't meet the front page?
5.
by ralph 13y ago
Dupe. https://news.ycombinator.com/item?id=5872550
6.
by ralph 13y ago
Is this not equivalent and avoids running grep(1) once for each path? find -exec grep -iH ${1?} {} + Though it still runs grep on directories.
7.
by ralph 13y ago
OK, I've gone and read the OP's text rather than just the quoted part. It seems he's talking about combining multiple X screens into one logical coordinate space, like I expect one or more of the existing extensions do, e.g.
8.
by ralph 13y ago
Coordinates in the X protocol are signed 16-bit so a screen can run from 0 to 32,767 along an edge. I agree though, the initial complaint is unclear and may be about something else.
9.
by ralph 13y ago
Yes, C across AIX, Suns, Silicon Graphics, whatever those HP ones were, and others. Platform differences were common, bugs rare because many had been before me and they could always be worked around; I didn't have to fix a C compiler. When
10.
by ralph 13y ago
Yes, because of the stableness of the C compiler, bigger test audience, etc., compared to a new language under rapid development.
11.
by ralph 13y ago
This is flawed AFAICS. It assumes that because 1.0 is fixed in specification that there are no bugs in the implementation. To return to my original point, these smart guys are on the record stating that's why they didn't do a self-hosting c
12.
by ralph 13y ago
Sorry, I don't understand. You seem to be saying there's only two versions of the compiler, one written in a foreign language, e.g. C, the other in a subset, e.g. Gosub, called G-2. But then there's "whatever is the current version of the l
13.
by ralph 13y ago
That's not how the books say to do it, and you're right, given who created Go you'd think they'd know this stuff. :-) Many generations of the compiler are created. Let's say the compiler-in-C is worked on until it compiles subset Gosub1 whi
14.
by ralph 13y ago
Seemingly often enough that it deterred them with Go. No, you may not be able to revert to before the bug was introduced as it may be the bug was there ever since that feature was added. As soon as it is self-hosted, the old compiler become
15.
by ralph 13y ago
The Go developers have said they deliberately didn't try and write Go in Go because they've done that with other languages, possibly Alef, I forget, and a bug can arise where the fix is obvious if it wasn't that the bug exists and would be
16.
by ralph 13y ago
But then the debugger can't be called ogle.
17.
by ralph 13y ago
Pre-vim, one would get quite proficient at judging line distances, e.g. 11yy, through practice. Mind you, that was probably helped by text being a fixed size on a serial terminal and bigger than much text today. However, I do wonder if the
18.
by ralph 13y ago
Here's a £ sign for someone to edit in.
19.
by ralph 13y ago
It's not that I'd use Perl for the task, just that I don't think rsync is special. Indeed, rsync has the overhead of forking a child and communicating empty/'s bareness.
20.
by ralph 13y ago
This Perl beats rsync by quite a margin here. perl -e 'opendir D, "."; @f = grep {$_ ne "." && $_ ne ".."} readdir D; unlink(@f) == $#f + 1 or die' It goes a bit quicker still if @f and the error handling are omitte
21.
by ralph 13y ago
I often think it would be useful for a filesystem to provide a digest of a file's content. It's the FS that knows when the file's content changes and the digest is out of date, and it also only needs to recalculate if anything asks. It woul
22.
by ralph 13y ago
This team of about 10, was it at Google or elsewhere? Wasn't sure given the higher-level context.
23.
by ralph 13y ago
It could be better bash, e.g. using [[ instead of [. Also, curl -s https://api.github.com/users/$2/events/public | grep "\"gravatar_id\":" | sed -e's/[,|"]//g' | head -n 1 | awk '{print $(NF)}' can be curl -sS
24.
by ralph 13y ago
Would be nice if the title had a few words describing what it is.
25.
by ralph 13y ago
I assume he's thinking of things like http://www.xemacs.org/
26.
by ralph 13y ago
I agree with your general point. Are you aware that j and k work in multi-column format too, though k seems to not move enough to make the top of the post visible from under the fixed horizontal bar.
27.
by ralph 13y ago
The go command does more than just compile. http://golang.org/doc/cmd
28.
by ralph 13y ago
No, not always. That's a poor example biased to simple string handling.
29.
by ralph 13y ago
In bash: cd ${PWD/foo/bar}
30.
by ralph 13y ago
http://en.wikiquote.org/wiki/Xun_Zi doesn't seem to have it; perhaps an update's required?

More ›