From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9front@googlegroups.com
Subject: Re: mothra ignores <br>, funky text entry
Date: Sun, 8 Jul 2012 05:15:00 +0100 [thread overview]
Message-ID: <20120708051500.4fb1b896@vardo.ethans.dre.am> (raw)
In-Reply-To: <ac10c6480fbcf0085cfc94b2d42c1f8e@sp.inri.net>
On Sat, 7 Jul 2012 13:08:10 -0500
sl@9front.org wrote:
> > > Have you verified that the forums in question are actually
> > > presenting a <br> and not something else?
> >
> > Right. What it's not parsing correctly is <br/>. It also doesn't parse
> > <hr/> although it parses <hr> correctly. Both errors can be seen at
> > http://ethan.uk.to/static/brtest.html
>
> Note: I have not yet updated to the newest changes committed
> while I was asleep last night.
>
> It seems <br> and <br /> were handled more ore less correctly,
> while <br/> was treated as what appears to be two spaces. It
> is true that multiple consecutive tags were treated as only one.
I think it was treated as nothing at all if there was no whitespace
between the tags. *nods*
>
> term% webfs -d >[2]out
> term% hget http://ethan.uk.to/static/brtest.html
> hget: too many errors with no progress host unreachable
> term% cat out
> term% ip/ping -n 3 ethan.uk.to
> sending 3 64 byte messages 1000 ms apart to icmp!ethan.uk.to!1
> 0: rtt 163652 µs, avg rtt 163652 µs, ttl = 40
> 1: rtt 157109 µs, avg rtt 160380 µs, ttl = 40
> 2: rtt 140876 µs, avg rtt 153879 µs, ttl = 40
Yeah, Ethernet lead slipped out again. A couple more weeks & I'll get a
t61 and then I can stop trying to use my CPU server as a terminal.
--
This is obviously some strange usage of the
word "simple" that I was previously unaware of.
next prev parent reply other threads:[~2012-07-08 4:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-07 1:31 Ethan Grammatikidis
2012-07-07 1:36 ` sl
2012-07-07 11:12 ` Ethan Grammatikidis
2012-07-07 13:13 ` cinap_lenrek
2012-07-07 16:03 ` Ethan Grammatikidis
2012-07-07 18:08 ` sl
2012-07-08 4:15 ` Ethan Grammatikidis [this message]
2012-07-07 12:22 ` cinap_lenrek
2012-07-07 13:39 ` cinap_lenrek
2012-07-07 15:46 ` Ethan Grammatikidis
2012-07-07 17:11 ` cinap_lenrek
2012-07-07 18:09 ` sl
2012-07-07 18:10 ` sl
2012-07-07 23:31 ` Ethan Grammatikidis
2012-07-08 0:07 ` cinap_lenrek
2012-07-08 5:34 ` Ethan Grammatikidis
2012-07-08 21:00 ` Matthew Veety
2012-07-09 4:16 ` Ethan Grammatikidis
2012-07-09 15:01 ` Julius Schmidt
2012-07-07 17:31 ` cinap_lenrek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120708051500.4fb1b896@vardo.ethans.dre.am \
--to=eekee57@fastmail.fm \
--cc=9front@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).