Boyd thought Sudoko sucked, I wrote a limbo program that serves a webpage.
brucee
On 13 January 2014 15:28, andrey mirtchovski mirtchov...@gmail.com wrote:
you can borrow the ui from here:
http://mirtchovski.com/p9/sudoku/
On Sun, Jan 12, 2014 at 9:20 PM, lu...@proxima.alt.za wrote:
I
When I first met plan9 (2nd ed) I realized that /n was a very powerful
ordering concept. (Since then I usually create a /n or ~/n on every
unix where I will use mount to customize my ns.)
I'd like to know
- what's the story of /n? (why was it invented?)
- what does n stand for? (a set of n
/n was introduced (i believe) in 8th edition for weinberger's neta (and
later netb) remote filesystem.
there was a directory in /n for each remote machine. the gmount() system
call was used to mount a stream, usually a datakit connection, to the
remote machine. it was great.
brucee
On 13
Can anyone explain to me the rationale of Dump dropping acme.dump in $HOME
instead of $PWD?
I know I can pass it a different filename, but it seems odd to put it in
$HOME instead of where acme is called from.
My use case is this: I'm working on two projects, and so want to maintain
two long-term
On Monday 13 of January 2014 08:42:22 Paul Lalonde wrote:
Can anyone explain to me the rationale of Dump dropping acme.dump in $HOME
instead of $PWD?
I know I can pass it a different filename, but it seems odd to put it in
$HOME instead of where acme is called from.
My use case is this: I'm
On 13 January 2014 16:42, Paul Lalonde paul.a.lalo...@gmail.com wrote:
Can anyone explain to me the rationale of Dump dropping acme.dump in $HOME
instead of $PWD?
alternatively, if started with acme -l dumpfile, why not write it back to
the same file?
Yes, I understand the current behaviour. I don't understand why $home was
privileged this way, instead of the startup directory. So for instance, if
I drop the dump filename in the top-level tag, and chord it against dump, I
get the right thing - it's deposited in the directory where acme was
That seems even more magical, I think.
I've been running with Dump's $HOME lookup changed to $PWD for a few days
now with nary a glitch.
Unless someone tells me otherwise I'll start pushing for a patch :-)
Paul
On Mon, Jan 13, 2014 at 8:57 AM, Charles Forsyth
charles.fors...@gmail.comwrote:
Because this way there is one default dump file.
Maybe it should be $home/lib/acme.dump
But when i turn on my terminal it runs acme -l $home/acme.dump
automatically. And before i turn it off i just press dump.
If I need to preserve a state for longer i can do
Dump otherfile. For me this seems the
Your described behaviour is unaffected by the patch unless you are running
acme (automatically) from another directory.
Paul
On Mon, Jan 13, 2014 at 10:53 AM, Bence Fábián beg...@gmail.com wrote:
Because this way there is one default dump file.
Maybe it should be $home/lib/acme.dump
But
On 13 January 2014 18:30, Paul Lalonde paul.a.lalo...@gmail.com wrote:
That seems even more magical, I think.
The idea is that the dump file is a snapshot of a particular state, and it
made sense to me to update
the given state, instead of putting it back in the default file despite
being
The idea is that the dump file is a snapshot of a particular state, and it
made sense to me to update
the given state, instead of putting it back in the default file despite
being given an explicit state.
That seemed to me a bit contrary.
agree.
- erik
The idea is that the dump file is a snapshot of a particular state, and it
made sense to me to update
the given state, instead of putting it back in the default file despite
being given an explicit state.
That seemed to me a bit contrary.
also if a snapshot is wanted, then we have a tool
It certainly addresses my use case. I'll give it a spin when I next have 5
minutes to mess with it.
Paul
On Mon, Jan 13, 2014 at 11:17 AM, Charles Forsyth charles.fors...@gmail.com
wrote:
On 13 January 2014 18:30, Paul Lalonde paul.a.lalo...@gmail.com wrote:
That seems even more
On 2014年01月13日 18:30, Paul Lalonde wrote:
I've been running with Dump's $HOME lookup changed to $PWD for a few days
now with nary a glitch.
I think using $PWD might give you a few problems. I had written a
wrapper script around acme that bound ./acme.dump over $home/acme.dump,
and when ./
when user does read of exactly 12*12 bytes on draw
ctl file, the snprint() adds one more \0 byte writing
beyond the user buffer and corrupting memory.
fix this by not snprint()ing the final space and add
it manually:
--- /sys/src/9/port/devdraw.c Wed Dec 25 13:55:16 2013 UTC
+++
Yeah. I don't disagree with Boyd's views on Sudoku, as filtered through
Brucee. Although, I feel that Boyd would have expressed them by saying
something like When I hear the word Sudoku, I reach for my insert your
weapon of choice here. However, I have the solver code, thanks to Knuth.
The UI,
+++ /sys/src/9/port/devdraw.c Mon Jan 13 23:22:13 2014 UTC
@@ -1187,10 +1187,11 @@
error(Enodrawimage);
i = di-image;
}
- n =
sprint(a, %11d %11d %11s %11d %11d %11d %11d %11d %11d %11d %11d %11d ,
+
Hello everyone,
I am new to the list and to Plan 9. I have been trying to set up an
OpenBSD venti server for a few days now, but to no success. My
intention was to use it as the default venti server for my Plan 9
machine.
I partitioned the disk using fdisk to create one large OpenBSD
partition,
just saw, sources seems to have already fixed this
by using snprint()...
so never mind :)
--
cinap
20 matches
Mail list logo
