(Pulling in an old message across the subject change. Hopefully I got it right.)
On Sat, Oct 25, 2014 at 1:12 PM, Daniel Camolês wrote:
> Breaking compatibility would be essential.
Let's pretend we could do it. Would you break compatibility once and
then fix everything and then try again to be c
> No, that was not what I was talking about. In this browser discussion,
> I am not interested in ways to understand complexity as your proposed
> solution. I think the fact that the browser needs to be this huge is a
> signal that things are very, very wrong, and a new solution for
> application d
> Am I alone? Is there any hope out there?
I'm working on this problem. I think the solution is white-box testing
from the ground up, so that software encodes not just the rules about
what to do but the specific scenarios that the programmer considered.
Because we only encode rules and not intenti
> Your ls is aliased in your shell startup scripts.
> Unset it or execute the program directly.
Ack, you're right.
I've cloned all the repositories enumerated in
http://morpheus.2f30.org and I could build sbase and ubase. What order
should I build the rest in, to get to mk?
I just got sbase cloned and built without trouble. Awesome!
But I don't know how to run ls:
$ ls
usage: ls [-1adFilrtU] [FILE...]
$ ls .
usage: ls [-1adFilrtU] [FILE...]
$ ls -d .
usage: ls [-1adFilrtU] [FILE...]
$ ls *
usage: ls [-1adFilrtU] [FILE...]
$ ls -l
usage: ls [-1adFilrtU] [FILE...]
$ l
On Thu, Oct 2, 2014 at 5:49 PM, Eric Pruitt wrote:
> How about creating new threads instead of replying to messages with
> something completed unrelated to the topic at hand? Normally, I can deal
> with bad email habits..
Sorry, realized after I hit send.
I asked Quentin this off-list:
> > http://c9x.me/irc
> >
> > "Following suckless habits, I plan to provide some extensions as patches."
> >
> > I'm new here. Can you think of any pointers describing this and/or other
> > suckless habits?
And got back a great list:
> Here is a list of things I th
> > automatically insert the comment sign at the beginning of the next line
>
> How does this work in vim?
Based on 'textwidth', lines are wrapped automatically to the next line
as you type. If the lines start with a comment leader like '#', the
leader is copied into the next line along with whit
> I'd like to draw attention to plover steno knight as well.
Link in case someone else is curious: http://openstenoproject.org
Fascinating, thanks.
Kartik
http://akkartik.name/about
I just joined this list. Are there downloadable archives somewhere
(ideally in mbox format) for offline browsing?
Kartik
http://akkartik.name/about
11 matches
Mail list logo
