David:
> "Oh, you mean you block browsers which don't adhere to the Microsoft
>standards... not the w3c standards... I see..."
...and as I've just been saying elsewhere, manufacturer-controlled standards
are no standards at all.
> Incidentally, I'm thinking of converting the
> I don't think any of the top-level capitalized docs should be turned
> into XML. They are for people to bring up in an editor (emacs, of
> course :-), not a web browser.
...and before a release is made, they are run through the proper
style sheet to turn them into 7-bit ascii format s
On Tue, Oct 30, 2001, Bill Janssen wrote:
> But I could see putting the FAQ, and maybe NEWS into the docs
> subdirectory and turning them into XML.
AUTHORS, COPYING, NEWS, README, and TODO should always be available
in the top dir or autoconf will complain.
/Mike
> Incidentally, I'm thinking of converting the basic README/FAQ/etc.
> text files in the CVS into an easily parsable format (XML, likely), so that
> I can pull them directly from the cvs to the website for viewing (i.e.
> index.pl/faq) and maintain one copy.
I don't think any of the top-lev
rs,
>
> If you want 24x7 support then expect to pay (a lot) for it ;-)
>
> Otherwise you need some patience (it was only 5 hours between your
> messages:)
>
> > I modified the file "debug.c", and changed all the serial code to POSE
> > HostControl API func
> Unless you're in the MS world, which seems to have completely junked use
> of the In-Reply-To and References headers. Outlook in particular is a
> bad offender in this area.
...and as Microsoft would have it's users believe, market share
dominance seems to be what determines standards
> subject is definately not the mechanism used to
> determine threading.
Unless you're in the MS world, which seems to have completely junked
use of the In-Reply-To and References headers. Outlook in particular
is a bad offender in this area.
Bill
On Mon, Oct 29, 2001, Max Bian wrote:
> I haven't heard anything back from developers,
If you want 24x7 support then expect to pay (a lot) for it ;-)
Otherwise you need some patience (it was only 5 hours between your
messages:)
> I modified the file "debug.c", and change
> Really sorry about that. I was just being lazy so I could avoid typing
> the To: address. I did, however, change the subject line. I am not sure
> what underlaying mechanism is used to signal a new thread. I thought it
> was the suject line.
Typically, threading is handled by the MU
On Mon, Oct 29, 2001, Max Bian wrote:
> There are some functions to send the debug messages to serial port.
> My question is how to access these messages at real time?
I haven't used the debug printouts in ages and I'm not sure the old
serial manager code still work.
BTW, please don't use an ex
On Tuesday 30 October 2001 00:34, you wrote:
> Hi,
>
> I haven't heard anything back from developers, but I got a solution to the
> problem.
>
> I modified the file "debug.c", and changed all the serial code to POSE
> HostControl API functions. Now I can
Hi,
I haven't heard anything back from developers, but I got a solution to the
problem.
I modified the file "debug.c", and changed all the serial code to POSE
HostControl API functions. Now I can use "tail -f" to watch my debugging
messages in a terminal without the
Hi.
I am interested in hacking plucker. I found debug.c interesting. There are some functions to send the debug messages to serial port. My question is how to access these messages at real time?
In POSE, the serial port is mapped to localhost:6416 in the default setup. I am not sure how I read
13 matches
Mail list logo
