Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.php > #17392 > unrolled thread

Problem between PHP and JavaScript with json

Back to article view | Back to comp.lang.php

Contents

  Problem between PHP and JavaScript with json Une Bévue <unbewusst.sein@fai.invalid> - 2017-05-02 15:31 +0200
    Re: Problem between PHP and JavaScript with json "Christoph M. Becker" <cmbecker69@arcor.de> - 2017-05-02 15:56 +0200
      Re: Problem between PHP and JavaScript with json Une Bévue <unbewusst.sein@fai.invalid> - 2017-05-02 17:27 +0200
        Re: Problem between PHP and JavaScript with json "Christoph M. Becker" <cmbecker69@arcor.de> - 2017-05-02 17:40 +0200
          Re: Problem between PHP and JavaScript with json Une Bévue <unbewusst.sein@fai.invalid> - 2017-05-02 19:03 +0200
            Re: Problem between PHP and JavaScript with json Une Bévue <unbewusst.sein@fai.invalid> - 2017-05-02 19:17 +0200
            Re: Problem between PHP and JavaScript with json "Christoph M. Becker" <cmbecker69@arcor.de> - 2017-05-02 19:35 +0200
              Re: Problem between PHP and JavaScript with json Une Bévue <unbewusst.sein@fai.invalid> - 2017-05-03 07:11 +0200
                Re: Problem between PHP and JavaScript with json "Christoph M. Becker" <cmbecker69@arcor.de> - 2017-05-03 13:37 +0200
                  Re: Problem between PHP and JavaScript with json Une Bévue <unbewusst.sein@fai.invalid> - 2017-05-03 17:35 +0200
                  Re: Problem between PHP and JavaScript with json Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2017-05-05 10:24 +0200
                    Re: Problem between PHP and JavaScript with json Une Bévue <unbewusst.sein@fai.invalid> - 2017-05-05 10:44 +0200
                      Re: Problem between PHP and JavaScript with json Jerry Stuckle <jstucklex@attglobal.net> - 2017-05-05 09:48 -0400
                        Re: Problem between PHP and JavaScript with json Richard Yates <richard@yatesguitar.com> - 2017-05-05 07:05 -0700
                          Re: Problem between PHP and JavaScript with json Jerry Stuckle <jstucklex@attglobal.net> - 2017-05-05 12:15 -0400
                          Re: Problem between PHP and JavaScript with json Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2017-05-16 00:01 +0200
                            Re: Problem between PHP and JavaScript with json Jerry Stuckle <jstucklex@attglobal.net> - 2017-05-15 20:49 -0400
                              Re: Problem between PHP and JavaScript with json Richard Yates <richard@yatesguitar.com> - 2017-05-16 21:26 -0700
                                Re: Problem between PHP and JavaScript with json Jerry Stuckle <jstucklex@attglobal.net> - 2017-05-17 10:07 -0400
                        Re: Problem between PHP and JavaScript with json Une Bévue <unbewusst.sein@fai.invalid> - 2017-05-06 07:08 +0200
                      Re: Problem between PHP and JavaScript with json "Christoph M. Becker" <cmbecker69@arcor.de> - 2017-05-05 15:57 +0200
                        Re: Problem between PHP and JavaScript with json Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2017-05-05 17:20 +0200
                        Re: Problem between PHP and JavaScript with json Une Bévue <unbewusst.sein@fai.invalid> - 2017-05-06 07:11 +0200
                          Re: Problem between PHP and JavaScript with json Luuk <luuk@invalid.lan> - 2017-05-06 11:50 +0200
                            Re: Problem between PHP and JavaScript with json Une Bévue <unbewusst.sein@fai.invalid> - 2017-05-06 17:04 +0200
                              Re: Problem between PHP and JavaScript with json Une Bévue <unbewusst.sein@fai.invalid> - 2017-05-07 11:27 +0200
                                Re: Problem between PHP and JavaScript with json Jerry Stuckle <jstucklex@attglobal.net> - 2017-05-07 07:41 -0400
                                  Re: Problem between PHP and JavaScript with json Une Bévue <unbewusst.sein@fai.invalid> - 2017-05-07 16:57 +0200
                                  Re: Problem between PHP and JavaScript with json Une Bévue <unbewusst.sein@fai.invalid> - 2017-05-07 17:03 +0200
                                    Re: Problem between PHP and JavaScript with json Jerry Stuckle <jstucklex@attglobal.net> - 2017-05-07 13:45 -0400
                                      Re: Problem between PHP and JavaScript with json Une Bévue <unbewusst.sein@fai.invalid> - 2017-05-08 07:48 +0200
                                        Re: Problem between PHP and JavaScript with json Jerry Stuckle <jstucklex@attglobal.net> - 2017-05-08 07:59 -0400
                            Re: Problem between PHP and JavaScript with json Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2017-05-06 19:54 +0200
                              Re: Problem between PHP and JavaScript with json Luuk <luuk@invalid.lan> - 2017-05-07 15:52 +0200
                                Re: Problem between PHP and JavaScript with json Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2017-05-07 16:15 +0200
                              Re: Problem between PHP and JavaScript with json Luuk <luuk@invalid.lan> - 2017-05-07 15:59 +0200
                                Re: Problem between PHP and JavaScript with json Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2017-05-07 16:16 +0200
                                Re: Problem between PHP and JavaScript with json Jerry Stuckle <jstucklex@attglobal.net> - 2017-05-07 13:46 -0400
                                  Re: Problem between PHP and JavaScript with json Luuk <luuk@invalid.lan> - 2017-05-07 21:05 +0200
                                    Re: Problem between PHP and JavaScript with json Jerry Stuckle <jstucklex@attglobal.net> - 2017-05-07 15:33 -0400
                                      Re: Problem between PHP and JavaScript with json Luuk <luuk@invalid.lan> - 2017-05-07 22:05 +0200

Page 1 of 3  [1] 2 3  Next page →

#17392 — Problem between PHP and JavaScript with json

I'm using Php to get a background image.
The php script scans a directory and choose a random image:

     $dir    = '/Users/yt/Sites/global/backgrounds';
     $files = array();
     chdir($dir);
     foreach (glob("*.jpg", GLOB_NOSORT) as $filename) {
         $files[] = $filename;
     }
     foreach (glob("*.png", GLOB_NOSORT) as $filename) {
         $files[] = $filename;
     }
     $count = count($files);
     $rand = rand(0, $count);
     $background = '/global/backgrounds/'. $files[$rand];


Then the script sends that to Javascript using json_encode( $data ) :

     $data['text'] = 'html {
   background: transparent url(http://mbp.local/global/backgrounds/'. 
$files[$rand] . ') no-repeat center center fixed;background-size: cover;}';
     $data['background'] = 'transparent 
url(http://mbp.local/global/backgrounds/'. $files[$rand] . ') no-repeat 
center center fixed';
     $data['background-image'] = 
'url(http://mbp.local/global/backgrounds/'. $files[$rand] . ')';
     $data['backgroundSize'] = 'cover';
     echo json_encode( $data );

The JavaScript call this script like that :

JSON.fetch = function(url, callback) {
   fetch(url)
   .then(function (response) {
     return response.json();
   })
   .then(function (json) {
     callback(json);
   });
};

used as :
   getBackground () {
     JSON.fetch("http://mbp.local/php/background-json.php", 
this.setBackground);
   };

with the callback :


   setBackground(json) {
     if(json.hasOwnProperty('background-image')) {
       document.body.style.backgroundImage = json['background-image'];
     }
   };

This is working well however, in the browser console I get this error :
SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the 
JSON data [Learn More]

The "[Learn More]" is link to this MDN page :
SyntaxError: JSON.parse: bad parsing
<https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Errors/JSON_bad_parse?utm_source=mozilla&utm_medium=firefox-console-errors&utm_campaign=default>



I don't know how to debugg that, that's to say how to get the raw json 
from the PHP script "background-json.php".

[toc] | [next] | [standalone]

#17393

On 02.05.2017 at 15:31, Une Bévue wrote:

>   getBackground () {
>     JSON.fetch("http://mbp.local/php/background-json.php",
> this.setBackground);
>   };
> 
> I don't know how to debugg that, that's to say how to get the raw json
> from the PHP script "background-json.php".

Well, what happens if you request this URI from the browser directly?
Don't you get the raw JSON then?

-- 
Christoph M. Becker

[toc] | [prev] | [next] | [standalone]

#17394

Le 02/05/2017 à 15:56, Christoph M. Becker a écrit :
> Well, what happens if you request this URI from the browser directly?
> Don't you get the raw JSON then?

Yes, of course, i get :
{"text":"html { \n  background: transparent 
url(http:\/\/mbp.local\/global\/backgrounds\/cerveaulent_recadre.png) 
no-repeat center center fixed;background-size: 
cover;}","background":"transparent 
url(http:\/\/mbp.local\/global\/backgrounds\/cerveaulent_recadre.png) 
no-repeat center center 
fixed","background-image":"url(http:\/\/mbp.local\/global\/backgrounds\/cerveaulent_recadre.png)","backgroundSize":"cover"}

even using :
$ wget http://mbp.local/php/background-json.php

i get the same, the first character being "{" and the last one "}"

the reason why i don't understand the error message (about the same 
using "Firefox Developer Edition" or "Safari Techical Preview")...

[toc] | [prev] | [next] | [standalone]

#17395

On 02.05.2017 at 17:27, Une Bévue wrote:

> Le 02/05/2017 à 15:56, Christoph M. Becker a écrit :
>
>> Well, what happens if you request this URI from the browser directly?
>> Don't you get the raw JSON then?
> 
> Yes, of course, i get :
> {"text":"html { \n  background: transparent
> url(http:\/\/mbp.local\/global\/backgrounds\/cerveaulent_recadre.png)
> no-repeat center center fixed;background-size:
> cover;}","background":"transparent
> url(http:\/\/mbp.local\/global\/backgrounds\/cerveaulent_recadre.png)
> no-repeat center center
> fixed","background-image":"url(http:\/\/mbp.local\/global\/backgrounds\/cerveaulent_recadre.png)","backgroundSize":"cover"}
> 
> 
> even using :
> $ wget http://mbp.local/php/background-json.php
> 
> i get the same, the first character being "{" and the last one "}"
> 
> the reason why i don't understand the error message (about the same
> using "Firefox Developer Edition" or "Safari Techical Preview")...

Have you checked the response in a hex editor?  I wouldn't be surprised
if it starts with

  EF BB BF

-- 
Christoph M. Becker

[toc] | [prev] | [next] | [standalone]

#17396

Le 02/05/2017 à 17:40, Christoph M. Becker a écrit :
> Have you checked the response in a hex editor?

No...

> I wouldn't be surprised
> if it starts with
>
>   EF BB BF

Here it is :

7B227465             - {"te

and ends with :

76657222 7D          - ver"}

following :
<http://www.asciitable.com/>

7B seems to be correct for "{"
7D seems to be correct for "}"

then ?

[toc] | [prev] | [next] | [standalone]

#17397

Le 02/05/2017 à 19:03, Une Bévue a écrit :
> then ?

may be the BOM ???

[toc] | [prev] | [next] | [standalone]

#17398

ON 02.05.2017 at 19:03, Une Bévue wrote:

> Le 02/05/2017 à 17:40, Christoph M. Becker a écrit :
>
> Here it is :
> 
> 7B227465             - {"te
> 
> and ends with :
> 
> 76657222 7D          - ver"}
> 
> following :
> <http://www.asciitable.com/>
> 
> 7B seems to be correct for "{"
> 7D seems to be correct for "}"
> 
> then ?

Hm, that is correct for ISO-8859-1, for instance.  Does the JSON
response specify an appropriate Content-Type header including the
correct charset?

-- 
Christoph M. Becker

[toc] | [prev] | [next] | [standalone]

#17399

Le 02/05/2017 à 19:35, Christoph M. Becker a écrit :
> Hm, that is correct for ISO-8859-1,

the code is also US-ASCII then UTF-8 for those caracters (common to 
US-ASCII, UTF-8 and ISO-8859-1).


> for instance.  Does the JSON
> response specify an appropriate Content-Type header including the
> correct charset?

yes :

header('Content-Type: application/json; charset=utf-8');

[toc] | [prev] | [next] | [standalone]

#17400

On 03.05.2017 at 07:11, Une Bévue wrote:

> Le 02/05/2017 à 19:35, Christoph M. Becker a écrit :
>
>> Hm, that is correct for ISO-8859-1,
> 
> the code is also US-ASCII then UTF-8 for those caracters (common to
> US-ASCII, UTF-8 and ISO-8859-1).

Of course, you're right.  Sorry for the noise.

>> for instance.  Does the JSON
>> response specify an appropriate Content-Type header including the
>> correct charset?
> 
> yes :
> 
> header('Content-Type: application/json; charset=utf-8');

That appears to be correct.

Don't know for what else to look.  Maybe you should consider asking in
JavaScript/ECMAScript related newsgroup.

-- 
Christoph M. Becker

[toc] | [prev] | [next] | [standalone]

#17401

Le 03/05/2017 à 13:37, Christoph M. Becker a écrit :
> Don't know for what else to look.  Maybe you should consider asking in
> JavaScript/ECMAScript related newsgroup.

yes, U're right, thanks.

[toc] | [prev] | [next] | [standalone]

#17402

Christoph M. Becker wrote:

> On 03.05.2017 at 07:11, Une Bévue wrote:
>> Le 02/05/2017 à 19:35, Christoph M. Becker a écrit :
>>> for instance.  Does the JSON
>>> response specify an appropriate Content-Type header including the
>>> correct charset?
>> 
>> yes :
>> 
>> header('Content-Type: application/json; charset=utf-8');
> 
> That appears to be correct.
> 
> Don't know for what else to look.  Maybe you should consider asking in
> JavaScript/ECMAScript related newsgroup.
  ^^^^^^^^^^^^^^^^^^^^^
Among other things it looks like the old “method referenced as function” 
blunder:

| getBackground () {
|   JSON.fetch("http://mbp.local/php/background-json.php",
|     this.setBackground);
      ^^^^^^^^^^^^^^^^^^
| };

Of course, the first thing to look for when one sees JSON.parse() issuing an 
error message is *the offending JSON.parse() call*.  One does not go to the 
dentist if one’s foot hurts.

If the OP would *finally* post with RFC-5536- *and* Netiquette-compliant 
headers, one might even read their postings directly, and advise them, *even 
if they were off topic*.  But no name, no address – *no cookies*.

-- 
PointedEars
Zend Certified PHP Engineer <http://www.zend.com/en/yellow-pages/ZEND024953>
<https://github.com/PointedEars> | <http://PointedEars.de/wsvn>
Twitter: @PointedEars2 | Please do not cc me./Bitte keine Kopien per E-Mail.

[toc] | [prev] | [next] | [standalone]

#17403

Le 05/05/2017 à 10:24, Thomas 'PointedEars' Lahn a écrit :
> Of course, the first thing to look for when one sees JSON.parse() issuing an
> error message is *the offending JSON.parse() call*.

JSONLint - The JSON Validator
<https://jsonlint.com/>

with the returned json of "http://mbp.local/php/background-json.php" :
{"text":"html { \n  background: transparent 
url(http:\/\/mbp.local\/global\/backgrounds\/postimage_1.jpg) no-repeat 
center center fixed;background-size: cover;}","background":"transparent 
url(http:\/\/mbp.local\/global\/backgrounds\/postimage_1.jpg) no-repeat 
center center 
fixed","background-image":"url(http:\/\/mbp.local\/global\/backgrounds\/postimage_1.jpg)","backgroundSize":"cover"}

i get :

Results

Valid JSON

[toc] | [prev] | [next] | [standalone]

#17404

On 5/5/2017 4:44 AM, Une Bévue wrote:
> Le 05/05/2017 à 10:24, Thomas 'PointedEars' Lahn a écrit :
>> Of course, the first thing to look for when one sees JSON.parse()
>> issuing an
>> error message is *the offending JSON.parse() call*.
> 
> JSONLint - The JSON Validator
> <https://jsonlint.com/>
> 
> with the returned json of "http://mbp.local/php/background-json.php" :
> {"text":"html { \n  background: transparent
> url(http:\/\/mbp.local\/global\/backgrounds\/postimage_1.jpg) no-repeat
> center center fixed;background-size: cover;}","background":"transparent
> url(http:\/\/mbp.local\/global\/backgrounds\/postimage_1.jpg) no-repeat
> center center
> fixed","background-image":"url(http:\/\/mbp.local\/global\/backgrounds\/postimage_1.jpg)","backgroundSize":"cover"}
> 
> 
> i get :
> 
> Results
> 
> Valid JSON
> 
> 
> 

Don't worry about "Pointed Head".  He's well-known as a troll in several
newsgroups.  He adds nothing to a discussion except insults and
complaints when your headers don't meet *his* expectations. You're much
better off ignoring his posts.

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#17406

On Fri, 5 May 2017 09:48:26 -0400, Jerry Stuckle
<jstucklex@attglobal.net> wrote:

>On 5/5/2017 4:44 AM, Une Bévue wrote:
>> Le 05/05/2017 à 10:24, Thomas 'PointedEars' Lahn a écrit :
>>> Of course, the first thing to look for when one sees JSON.parse()
>>> issuing an
>>> error message is *the offending JSON.parse() call*.
>> 
>> JSONLint - The JSON Validator
>> <https://jsonlint.com/>
>> 
>> with the returned json of "http://mbp.local/php/background-json.php" :
>> {"text":"html { \n  background: transparent
>> url(http:\/\/mbp.local\/global\/backgrounds\/postimage_1.jpg) no-repeat
>> center center fixed;background-size: cover;}","background":"transparent
>> url(http:\/\/mbp.local\/global\/backgrounds\/postimage_1.jpg) no-repeat
>> center center
>> fixed","background-image":"url(http:\/\/mbp.local\/global\/backgrounds\/postimage_1.jpg)","backgroundSize":"cover"}
>> 
>> 
>> i get :
>> 
>> Results
>> 
>> Valid JSON
>> 
>> 
>> 
>
>Don't worry about "Pointed Head".  He's well-known as a troll in several
>newsgroups.  He adds nothing to a discussion except insults and
>complaints when your headers don't meet *his* expectations. You're much
>better off ignoring his posts.

Any chance of you guys upgrading the quality and variety of your
exchanges? This may help: 
https://xkcd.com/1833/

[toc] | [prev] | [next] | [standalone]

#17408

On 5/5/2017 10:05 AM, Richard Yates wrote:
> On Fri, 5 May 2017 09:48:26 -0400, Jerry Stuckle
> <jstucklex@attglobal.net> wrote:
> 
>> On 5/5/2017 4:44 AM, Une Bévue wrote:
>>> Le 05/05/2017 à 10:24, Thomas 'PointedEars' Lahn a écrit :
>>>> Of course, the first thing to look for when one sees JSON.parse()
>>>> issuing an
>>>> error message is *the offending JSON.parse() call*.
>>>
>>> JSONLint - The JSON Validator
>>> <https://jsonlint.com/>
>>>
>>> with the returned json of "http://mbp.local/php/background-json.php" :
>>> {"text":"html { \n  background: transparent
>>> url(http:\/\/mbp.local\/global\/backgrounds\/postimage_1.jpg) no-repeat
>>> center center fixed;background-size: cover;}","background":"transparent
>>> url(http:\/\/mbp.local\/global\/backgrounds\/postimage_1.jpg) no-repeat
>>> center center
>>> fixed","background-image":"url(http:\/\/mbp.local\/global\/backgrounds\/postimage_1.jpg)","backgroundSize":"cover"}
>>>
>>>
>>> i get :
>>>
>>> Results
>>>
>>> Valid JSON
>>>
>>>
>>>
>>
>> Don't worry about "Pointed Head".  He's well-known as a troll in several
>> newsgroups.  He adds nothing to a discussion except insults and
>> complaints when your headers don't meet *his* expectations. You're much
>> better off ignoring his posts.
> 
> Any chance of you guys upgrading the quality and variety of your
> exchanges? This may help: 
> https://xkcd.com/1833/
> 

Just warning the OP about Pointed Head, that's all.


-- 
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#17443

Richard Yates wrote:

> On Fri, 5 May 2017 09:48:26 -0400, Jerry Stuckle
> <jstucklex@attglobal.net> wrote:
>>Don't worry about "Pointed Head".  He's well-known as a troll in several
>>newsgroups.

It takes one to know one.

>>He adds nothing to a discussion except insults and
>>complaints when your headers don't meet *his* expectations. You're much
>>better off ignoring his posts.
> 
> Any chance of you guys upgrading the quality and variety of your
> exchanges? This may help:
> https://xkcd.com/1833/

It is just Jerry who is stuckled in the mud there, wildly throwing it around 
himself in the hope that something of it may stick ;-)  I pity him for 
having chosen to waste his life like this, but that aside I could not care 
less about what he writes about me.  As a result, my quality of life has 
improved a lot.  Had you not quoted him, I would not even have noticed it.  
The only problem (for the rest) is that he still does not understand that.

HTH

-- 
PointedEars
Zend Certified PHP Engineer <http://www.zend.com/en/yellow-pages/ZEND024953>
<https://github.com/PointedEars> | <http://PointedEars.de/wsvn>
Twitter: @PointedEars2 | Please do not cc me./Bitte keine Kopien per E-Mail.

[toc] | [prev] | [next] | [standalone]

#17444

On 5/15/2017 6:01 PM, Thomas 'PointedEars' Lahn wrote:
> Richard Yates wrote:
> 
>> On Fri, 5 May 2017 09:48:26 -0400, Jerry Stuckle
>> <jstucklex@attglobal.net> wrote:
>>> Don't worry about "Pointed Head".  He's well-known as a troll in several
>>> newsgroups.
> 
> It takes one to know one.
>

Yes, and you know them all.  But then that's the typical third-grade
response from a troll.

>>> He adds nothing to a discussion except insults and
>>> complaints when your headers don't meet *his* expectations. You're much
>>> better off ignoring his posts.
>>
>> Any chance of you guys upgrading the quality and variety of your
>> exchanges? This may help:
>> https://xkcd.com/1833/
> 
> It is just Jerry who is stuckled in the mud there, wildly throwing it around 
> himself in the hope that something of it may stick ;-)  I pity him for 
> having chosen to waste his life like this, but that aside I could not care 
> less about what he writes about me.  As a result, my quality of life has 
> improved a lot.  Had you not quoted him, I would not even have noticed it.  
> The only problem (for the rest) is that he still does not understand that.
> 
> HTH
> 

ROFLMAO!  How about all of the other newsgroups where you are a well
known troll - for instance, comp.lang.javascript?  And several others?

But then if you didn't care what I wrote about you, you wouldn't spend
the effort responding, would you?  But you can't stand people knowing
what the REAL Pointed Head is.

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#17446

On Mon, 15 May 2017 20:49:32 -0400, Jerry Stuckle
<jstucklex@attglobal.net> wrote:

>On 5/15/2017 6:01 PM, Thomas 'PointedEars' Lahn wrote:
>> Richard Yates wrote:
>> 
>>> On Fri, 5 May 2017 09:48:26 -0400, Jerry Stuckle
>>> <jstucklex@attglobal.net> wrote:
>>>> Don't worry about "Pointed Head".  He's well-known as a troll in several
>>>> newsgroups.
>> 
>> It takes one to know one.
>>
>
>Yes, and you know them all.  But then that's the typical third-grade
>response from a troll.
>
>>>> He adds nothing to a discussion except insults and
>>>> complaints when your headers don't meet *his* expectations. You're much
>>>> better off ignoring his posts.
>>>
>>> Any chance of you guys upgrading the quality and variety of your
>>> exchanges? This may help:
>>> https://xkcd.com/1833/
>> 
>> It is just Jerry who is stuckled in the mud there, wildly throwing it around 
>> himself in the hope that something of it may stick ;-)  I pity him for 
>> having chosen to waste his life like this, but that aside I could not care 
>> less about what he writes about me.  As a result, my quality of life has 
>> improved a lot.  Had you not quoted him, I would not even have noticed it.  
>> The only problem (for the rest) is that he still does not understand that.
>> 
>> HTH
>> 
>
>ROFLMAO!  How about all of the other newsgroups where you are a well
>known troll - for instance, comp.lang.javascript?  And several others?
>
>But then if you didn't care what I wrote about you, you wouldn't spend
>the effort responding, would you?  But you can't stand people knowing
>what the REAL Pointed Head is.

I was wrong.A better cultural reference is this one: 
http://www.startrek.com/uploads/assets/articles/insetbalkwhite.jpg

[toc] | [prev] | [next] | [standalone]

#17447

On 5/17/2017 12:26 AM, Richard Yates wrote:
> On Mon, 15 May 2017 20:49:32 -0400, Jerry Stuckle
> <jstucklex@attglobal.net> wrote:
> 
>> On 5/15/2017 6:01 PM, Thomas 'PointedEars' Lahn wrote:
>>> Richard Yates wrote:
>>>
>>>> On Fri, 5 May 2017 09:48:26 -0400, Jerry Stuckle
>>>> <jstucklex@attglobal.net> wrote:
>>>>> Don't worry about "Pointed Head".  He's well-known as a troll in several
>>>>> newsgroups.
>>>
>>> It takes one to know one.
>>>
>>
>> Yes, and you know them all.  But then that's the typical third-grade
>> response from a troll.
>>
>>>>> He adds nothing to a discussion except insults and
>>>>> complaints when your headers don't meet *his* expectations. You're much
>>>>> better off ignoring his posts.
>>>>
>>>> Any chance of you guys upgrading the quality and variety of your
>>>> exchanges? This may help:
>>>> https://xkcd.com/1833/
>>>
>>> It is just Jerry who is stuckled in the mud there, wildly throwing it around 
>>> himself in the hope that something of it may stick ;-)  I pity him for 
>>> having chosen to waste his life like this, but that aside I could not care 
>>> less about what he writes about me.  As a result, my quality of life has 
>>> improved a lot.  Had you not quoted him, I would not even have noticed it.  
>>> The only problem (for the rest) is that he still does not understand that.
>>>
>>> HTH
>>>
>>
>> ROFLMAO!  How about all of the other newsgroups where you are a well
>> known troll - for instance, comp.lang.javascript?  And several others?
>>
>> But then if you didn't care what I wrote about you, you wouldn't spend
>> the effort responding, would you?  But you can't stand people knowing
>> what the REAL Pointed Head is.
> 
> I was wrong.A better cultural reference is this one: 
> http://www.startrek.com/uploads/assets/articles/insetbalkwhite.jpg
> 

Richard, do you really believe I give a damn what you think?

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#17409

Le 05/05/2017 à 15:48, Jerry Stuckle a écrit :
> Don't worry about "Pointed Head".  He's well-known as a troll in several
> newsgroups.  He adds nothing to a discussion except insults and
> complaints when your headers don't meet *his* expectations. You're much
> better off ignoring his posts.

fine thanks !

[toc] | [prev] | [next] | [standalone]

Page 1 of 3  [1] 2 3  Next page →

Back to top | Article view | comp.lang.php

csiph-web