On 22 May 2013 22:27, G David Modica wrote:
>
> On 11:06 Wed 22 May , Thorsten Glaser wrote:
> > How about:
> >
> > script man foo q exit
> >
> gdm@gdmThink ~$ script man foo q exit
> bash: syntax error near unexpected token `newline'
> gdm@gdmThink ~$
I'm not sure whether to laugh or c
On 05/22/2013 04:27 PM, G David Modica wrote:
Guilty, systemd is one of the banes of my existence but I've not found anything
I like better than Arch.
Search again.
--
7heo
Thorsten Glaser wrote:
> Doing anything else (well, file download is also okay),
> such as this XMLRPC crap, or even tunneling, over HTTP
> instead of just using plain TCP is probably the thing
> the original poster disagreed with. Me too, btw… it’s
> an illness of the age of the “webdesigner” ☹
There are quite a few problems with HTTP like you cannot parse it
because the grammer allows anything, most importantly:
- Multiple HTTP Accept Headers (with empty entries) allowed
- Newline or Carriage Return or both or whatever
Because of this great flexibility you can enjoy undeterministic
res
On Wed, May 22, 2013 at 4:24 PM, Thorsten Glaser wrote:
> Andrew Gwozdziewycz dixit:
>
> >Not really, given that HTML has *nothing* to do with HTTP.
>
> Both are overused, really.
>
You won't find me arguing against this statement.
>Of course, you often retrieve HTML documents via HTTP
>
> Doin
* Thorsten Glaser [2013-05-22 22:29]:
AFAIK they mandate that XHTML be served as application/xml+xhtml
instead of text/html, which the XHTML standard itself says
to use for compatibility reasons (they also try to weasel
in the application/xml+xhtml content type, but realise it
won’t work). Nice
Andrew Gwozdziewycz dixit:
>Not really, given that HTML has *nothing* to do with HTTP.
Both are overused, really.
>Of course, you often retrieve HTML documents via HTTP
Doing anything else (well, file download is also okay),
such as this XMLRPC crap, or even tunneling, over HTTP
instead of just
yes; gmail changed my preferences again.
On Wed, May 22, 2013 at 3:54 PM, Gregor Best wrote:
> On Wed, May 22, 2013 at 03:19:46PM -0400, Jacob Todd wrote:
>> no.
>> [...]
>
> Isn't it kinda ironic that this mail came as HTML?
>
> --
> Gregor Best
>
On Wed, May 22, 2013 at 3:54 PM, Gregor Best wrote:
> On Wed, May 22, 2013 at 03:19:46PM -0400, Jacob Todd wrote:
> > no.
> > [...]
>
> Isn't it kinda ironic that this mail came as HTML?
Not really, given that HTML has *nothing* to do with HTTP.
Of course, you often retrieve HTML documents via
On Wed, May 22, 2013 at 03:19:46PM -0400, Jacob Todd wrote:
> no.
> [...]
Isn't it kinda ironic that this mail came as HTML?
--
Gregor Best
no.
On Wed, May 22, 2013 at 2:50 PM, Thomas Dean <78...@web.de> wrote:
> On Wed, May 22, 2013 at 20:37:47 +0200, seb.cato wrote:
> > I'm not a hater most of the time though. HTTP and by extension the
> > web is quite organic. It's like a rain forest. There's a lot of
> > things in there, and a l
On Wed, May 22, 2013 at 20:37:47 +0200, seb.cato wrote:
> I'm not a hater most of the time though. HTTP and by extension the
> web is quite organic. It's like a rain forest. There's a lot of
> things in there, and a lot of it is redundant and some things serves
> no real purpose, but at the same ti
I don't know about the author, but I think the whole web application stack of
today is overly complex.
Auth can be done in request headers, POST-data or even as a part of the URI in
a GET request, if you want to.
HTTP state management... You know, GET requests were supposed to not have any
e
G David Modica dixit:
>On 11:06 Wed 22 May , Thorsten Glaser wrote:
>> How about:
>>
>> script man foo q exit
>gdm@gdmThink ~$ script man foo q exit
>bash: syntax error near unexpected token `newline'
>gdm@gdmThink ~$
This is something to print out, frame and hang on the wall.
… Hon
On the http://harmful.cat-v.org/software/ I've found very interesting
statment about HTTP: "or best of all: don't use HTTP". Can someone
explain me why the author claims that? What is bad in http?
Regards,
Szymon
On 13:16 Wed 22 May , Maximilian Dietrich wrote:
> I had the same problem. I fixed it by changing defaultitalic and
> defaultunderline in the st config to a readable color.
>
> Cheers,
> Maximilian D.
That is it! Thank you all.
On 11:06 Wed 22 May , Thorsten Glaser wrote:
> Fernando C.V. dixit:
>
> >rendered, but unreadable.. can you copy-paste the invisible spaces
> >between the "[-c ]"?
>
> How about:
>
> script man foo q exit
>
gdm@gdmThink ~$ script man foo q exit
bash: syntax error near unexpected
On 11:56 Wed 22 May , Fernando C.V. wrote:
> Maybe you altered your st colors somehow and the highlights make the
> characters hard to see... my guess is that the words are there
> rendered, but unreadable.. can you copy-paste the invisible spaces
> between the "[-c ]"?
>
Yes, the missing
On 11:50 Wed 22 May , Fernando C.V. wrote:
> or better:
>
> set | grep LESS
gdm@gdmThink ~$ set | grep LESS
gdm@gdmThink ~$
On 11:48 Wed 22 May , Fernando C.V. wrote:
> Maybe you have some custom less settings?
> try this:
>
> echo $LESS
> echo $LESS_TERMCAP_mb - $LESS_TERMCAP_md - $LESS_TERMCAP_so -
> $LESS_TERMCAP_us
> echo $LESS_TERMCAP_me - $LESS_TERMCAP_se - $LESS_TERMCAP_so -
> $LESS_TERMCAP_ue
>
On Tue, May 21, 2013 at 08:52:52PM -0400, G David Modica wrote:
> Hi,
>
> I just noticed that man pages are not rendered properly under st-0.4.1 tip.
> For example in "man st" the SYNOPSYS line shows as:
>st [-a] [-c ] [-f ] [-g ] [-o ] [-t ] [-w
> ]
Fernando C.V. dixit:
>rendered, but unreadable.. can you copy-paste the invisible spaces
>between the "[-c ]"?
How about:
script man foo q exit
Then send in the typescript, gzip(1)d.
bye,
//mirabilos
--
Sorry, I’m annoyed today and you came by as an Arch user. These are the
perfect
Maybe you altered your st colors somehow and the highlights make the
characters hard to see... my guess is that the words are there
rendered, but unreadable.. can you copy-paste the invisible spaces
between the "[-c ]"?
(sorry for the 3 mails in a row... I just I kept thinking about it)
--
or better:
set | grep LESS
--
Fernando
On Wed, May 22, 2013 at 11:48 AM, Fernando C.V. wrote:
> On Wed, May 22, 2013 at 11:23 AM, G David Modica
> wrote:
>> I believe it defaults to "less".
>
> Maybe you have some custom less settings?
> try this:
>
> echo $LESS
> echo $LESS_TERMCAP
On Wed, May 22, 2013 at 11:23 AM, G David Modica
wrote:
> I believe it defaults to "less".
Maybe you have some custom less settings?
try this:
echo $LESS
echo $LESS_TERMCAP_mb - $LESS_TERMCAP_md - $LESS_TERMCAP_so -
$LESS_TERMCAP_us
echo $LESS_TERMCAP_me - $LESS_TERMCAP_se - $LESS_TE
On 11:47 Wed 22 May , Chris Down wrote:
> You have misunderstood the question -- what is your $PAGER?
gdm@gdmThink ~$ echo $PAGER
gdm@gdmThink ~$
I believe it defaults to "less".
26 matches
Mail list logo
