Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > uk.comp.sys.mac > #116616 > unrolled thread
| Started by | Steve <hamrun@gmail.com> |
|---|---|
| First post | 2017-03-22 08:21 -0700 |
| Last post | 2017-03-24 13:54 +1300 |
| Articles | 20 on this page of 91 — 20 participants |
Back to article view | Back to uk.comp.sys.mac
Short Lightning and USB mini/micro cables Steve <hamrun@gmail.com> - 2017-03-22 08:21 -0700
Re: Short Lightning and USB mini/micro cables Ian McCall <ian@eruvia.org> - 2017-03-22 15:52 +0000
Re: Short Lightning and USB mini/micro cables Chris Ridd <chrisridd@mac.com> - 2017-03-22 21:05 +0000
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-03-22 17:10 -0400
Re: Short Lightning and USB mini/micro cables Steve Hodgson <hamrun@gmail.com> - 2017-03-23 16:37 +0000
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-03-23 12:52 -0400
Re: Short Lightning and USB mini/micro cables Chris Ridd <chrisridd@mac.com> - 2017-03-22 21:11 +0000
Re: Short Lightning and USB mini/micro cables Steve <hamrun@gmail.com> - 2017-03-25 14:21 -0700
Re: Short Lightning and USB mini/micro cables Chris Ridd <chrisridd@mac.com> - 2017-03-26 08:58 +0100
Re: Short Lightning and USB mini/micro cables Krzysztof Staniorowski <nospam@ksx4system.net> - 2017-04-15 02:29 +0000
Re: Short Lightning and USB mini/micro cables Ian McCall <ian@eruvia.org> - 2017-04-15 07:41 +0100
Re: Short Lightning and USB mini/micro cables dempson@actrix.gen.nz (David Empson) - 2017-04-15 19:10 +1200
Re: Short Lightning and USB mini/micro cables Ian McCall <ian@eruvia.org> - 2017-04-15 09:31 +0100
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-15 12:10 -0400
Re: Short Lightning and USB mini/micro cables Ian McCall <ian@eruvia.org> - 2017-04-15 18:21 +0100
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-15 15:09 -0400
Re: Short Lightning and USB mini/micro cables real-not-anti-spam-address@apple-juice.co.uk (D.M. Procida) - 2017-04-16 17:39 +0100
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-16 13:42 -0400
Re: Short Lightning and USB mini/micro cables David Kennedy <davidkennedy@nospamherethankyou.invalid> - 2017-04-16 22:57 +0100
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-16 19:22 -0400
Re: Short Lightning and USB mini/micro cables David Kennedy <davidkennedy@nospamherethankyou.invalid> - 2017-04-17 09:13 +0100
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-17 09:32 -0400
Re: Short Lightning and USB mini/micro cables David Kennedy <davidkennedy@nospamherethankyou.invalid> - 2017-04-17 22:55 +0100
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-17 18:09 -0400
Re: Short Lightning and USB mini/micro cables David Kennedy <davidkennedy@nospamherethankyou.invalid> - 2017-04-17 23:52 +0100
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-17 20:39 -0400
Re: Short Lightning and USB mini/micro cables real-not-anti-spam-address@apple-juice.co.uk (D.M. Procida) - 2017-04-17 09:16 +0100
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-17 09:32 -0400
Re: Short Lightning and USB mini/micro cables David Kennedy <davidkennedy@nospamherethankyou.invalid> - 2017-04-17 22:57 +0100
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-17 18:09 -0400
Re: Short Lightning and USB mini/micro cables Graham J <graham@invalid.com> - 2017-04-17 10:11 +0100
Re: Short Lightning and USB mini/micro cables nospam@de-ster.demon.nl (J. J. Lodder) - 2017-04-17 19:40 +0200
Re: Short Lightning and USB mini/micro cables Paul Sture <nospam@sture.ch> - 2017-04-17 20:17 +0200
Re: Short Lightning and USB mini/micro cables Paul Sture <nospam@sture.ch> - 2017-04-17 20:19 +0200
Re: Short Lightning and USB mini/micro cables richard@cogsci.ed.ac.uk (Richard Tobin) - 2017-04-17 23:53 +0000
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-17 14:36 -0400
Re: Short Lightning and USB mini/micro cables Chris <ithinkiam@gmail.com> - 2017-04-18 17:28 +0000
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-18 14:19 -0400
Re: Short Lightning and USB mini/micro cables nospam@de-ster.demon.nl (J. J. Lodder) - 2017-04-18 21:55 +0200
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-18 16:22 -0400
Re: Short Lightning and USB mini/micro cables Ian McCall <ian@eruvia.org> - 2017-04-19 10:53 +0100
Re: Short Lightning and USB mini/micro cables real-not-anti-spam-address@apple-juice.co.uk (D.M. Procida) - 2017-04-19 11:14 +0100
Re: Short Lightning and USB mini/micro cables Sara Merriman <saramerriman@blueyonder.co.uk> - 2017-04-19 12:48 +0100
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-19 08:47 -0400
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-19 08:47 -0400
Re: Short Lightning and USB mini/micro cables Ian McCall <ian@eruvia.org> - 2017-04-20 08:35 +0100
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-20 10:22 -0400
Re: Short Lightning and USB mini/micro cables richard@cogsci.ed.ac.uk (Richard Tobin) - 2017-04-20 14:51 +0000
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-20 11:57 -0400
Re: Short Lightning and USB mini/micro cables David Kennedy <davidkennedy@nospamherethankyou.invalid> - 2017-04-20 21:00 +0100
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-20 16:20 -0400
Re: Short Lightning and USB mini/micro cables richard@cogsci.ed.ac.uk (Richard Tobin) - 2017-04-20 20:07 +0000
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-20 16:20 -0400
Re: Short Lightning and USB mini/micro cables richard@cogsci.ed.ac.uk (Richard Tobin) - 2017-04-20 20:51 +0000
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-20 17:15 -0400
Re: Short Lightning and USB mini/micro cables richard@cogsci.ed.ac.uk (Richard Tobin) - 2017-04-20 21:36 +0000
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-20 17:43 -0400
Re: Short Lightning and USB mini/micro cables {$PW$}@womar.co.uk (Paul Womar) - 2017-04-21 12:49 +0100
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-21 10:13 -0400
Re: Short Lightning and USB mini/micro cables thnews@poboxmolar.com.invalid (Tim Hodgson) - 2017-04-21 17:28 +0100
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-21 12:34 -0400
Re: Short Lightning and USB mini/micro cables thnews@poboxmolar.com.invalid (Tim Hodgson) - 2017-04-21 17:51 +0100
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-21 13:25 -0400
Re: Short Lightning and USB mini/micro cables nospam@de-ster.demon.nl (J. J. Lodder) - 2017-04-21 19:18 +0200
Re: Short Lightning and USB mini/micro cables {$PW$}@womar.co.uk (Paul Womar) - 2017-04-22 11:31 +0100
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-23 19:56 -0400
Re: Short Lightning and USB mini/micro cables David Kennedy <davidkennedy@nospamherethankyou.invalid> - 2017-04-24 08:48 +0100
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-24 10:31 -0400
Re: Short Lightning and USB mini/micro cables real-not-anti-spam-address@apple-juice.co.uk (D.M. Procida) - 2017-04-24 17:36 +0100
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-24 13:00 -0400
Re: Short Lightning and USB mini/micro cables real-not-anti-spam-address@apple-juice.co.uk (D.M. Procida) - 2017-04-24 18:13 +0100
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-24 13:33 -0400
Re: Short Lightning and USB mini/micro cables David Kennedy <davidkennedy@nospamherethankyou.invalid> - 2017-04-24 23:03 +0100
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-25 12:57 -0400
Re: Short Lightning and USB mini/micro cables real-not-anti-spam-address@apple-juice.co.uk (D.M. Procida) - 2017-04-25 22:34 +0100
Re: Short Lightning and USB mini/micro cables David Kennedy <davidkennedy@nospamherethankyou.invalid> - 2017-04-24 23:02 +0100
Re: Short Lightning and USB mini/micro cables {$PW$}@womar.co.uk (Paul Womar) - 2017-04-25 16:32 +0100
Re: Short Lightning and USB mini/micro cables Ian McCall <ian@eruvia.org> - 2017-04-25 16:35 +0100
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-25 12:57 -0400
Re: Short Lightning and USB mini/micro cables Ian McCall <ian@eruvia.org> - 2017-04-25 20:25 +0100
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-25 16:06 -0400
Re: Short Lightning and USB mini/micro cables RJH <patchmoney@gmx.com> - 2017-04-27 03:39 +0100
Re: Short Lightning and USB mini/micro cables Ian McCall <ian@eruvia.org> - 2017-04-27 09:35 +0100
Re: Short Lightning and USB mini/micro cables Jaimie Vandenbergh <jaimie@sometimes.sessile.org> - 2017-04-27 23:20 +0100
Re: Short Lightning and USB mini/micro cables Graeme Wall <rail@greywall.demon.co.uk> - 2017-04-27 13:52 +0100
Re: Short Lightning and USB mini/micro cables David Kennedy <davidkennedy@nospamherethankyou.invalid> - 2017-04-20 20:59 +0100
Re: Short Lightning and USB mini/micro cables nospam <nospam@nospam.invalid> - 2017-04-15 12:10 -0400
Re: Short Lightning and USB mini/micro cables Steve Hodgson <hamrun@gmail.com> - 2017-03-23 16:35 +0000
Re: Short Lightning and USB mini/micro cables dempson@actrix.gen.nz (David Empson) - 2017-03-23 10:14 +1300
Re: Short Lightning and USB mini/micro cables Steve Hodgson <hamrun@gmail.com> - 2017-03-23 16:39 +0000
Re: Short Lightning and USB mini/micro cables dempson@actrix.gen.nz (David Empson) - 2017-03-24 13:54 +1300
Page 3 of 5 — ← Prev page 1 2 [3] 4 5 Next page →
| From | Ian McCall <ian@eruvia.org> |
|---|---|
| Date | 2017-04-19 10:53 +0100 |
| Message-ID | <eloqd7F39rqU1@mid.individual.net> |
| In reply to | #117252 |
On 2017-04-18 20:22:00 +0000, nospam <nospam@nospam.invalid> said: > In article <1n4p4sh.xbw1kqqrgxfzN@de-ster.xs4all.nl>, J. J. Lodder > <nospam@de-ster.demon.nl> wrote: > >> I still think building the Bondi Blue like they did >> was the right choice, > > it was, but not having a cd burner was still a mistake. > > perhaps a minor one in retrospect, but still a mistake. From memory, in the Jobs biography they talk about his disappointment with the CD-ROM. The answer wasn't really an Apple thing, it was that burners weren't available in large numbers in slot form, and Jobs insisted on having a slot not a tray loader. He really, really didn't like the 1st gen iMacs that had tray loaders. Cheers, Ian
[toc] | [prev] | [next] | [standalone]
| From | real-not-anti-spam-address@apple-juice.co.uk (D.M. Procida) |
|---|---|
| Date | 2017-04-19 11:14 +0100 |
| Message-ID | <1n4q6t2.13afscgixgnq1N%real-not-anti-spam-address@apple-juice.co.uk> |
| In reply to | #117256 |
Ian McCall <ian@eruvia.org> wrote: > On 2017-04-18 20:22:00 +0000, nospam <nospam@nospam.invalid> said: > > > In article <1n4p4sh.xbw1kqqrgxfzN@de-ster.xs4all.nl>, J. J. Lodder > > <nospam@de-ster.demon.nl> wrote: > > > >> I still think building the Bondi Blue like they did > >> was the right choice, > > > > it was, but not having a cd burner was still a mistake. > > > > perhaps a minor one in retrospect, but still a mistake. > > From memory, in the Jobs biography they talk about his disappointment > with the CD-ROM. The answer wasn't really an Apple thing, it was that > burners weren't available in large numbers in slot form, and Jobs > insisted on having a slot not a tray loader. > > He really, really didn't like the 1st gen iMacs that had tray loaders. I miss Steve Jobs's obsessive and unreasonable demands. Half the time he was completely wrong about the value of what he wanted, but it meant there was always a direction and and aim. The idea that someone spent 9 months refusing to allow a certain iPhone to be manufactured because it would be the wrong shade of white is the kind of small detail that makes the world worth living in. Not because of the colour, just because someone cared. I think that's what I want: that someone cares, and cares about things that are in some sense unfathomable. Daniele
[toc] | [prev] | [next] | [standalone]
| From | Sara Merriman <saramerriman@blueyonder.co.uk> |
|---|---|
| Date | 2017-04-19 12:48 +0100 |
| Message-ID | <190420171248469769%saramerriman@blueyonder.co.uk> |
| In reply to | #117257 |
In article <1n4q6t2.13afscgixgnq1N%real-not-anti-spam-address@apple-juice.co.uk>, D.M. Procida <real-not-anti-spam-address@apple-juice.co.uk> wrote: > Ian McCall <ian@eruvia.org> wrote: > > > On 2017-04-18 20:22:00 +0000, nospam <nospam@nospam.invalid> said: > > > > > In article <1n4p4sh.xbw1kqqrgxfzN@de-ster.xs4all.nl>, J. J. Lodder > > > <nospam@de-ster.demon.nl> wrote: > > > > > >> I still think building the Bondi Blue like they did > > >> was the right choice, > > > > > > it was, but not having a cd burner was still a mistake. > > > > > > perhaps a minor one in retrospect, but still a mistake. > > > > From memory, in the Jobs biography they talk about his disappointment > > with the CD-ROM. The answer wasn't really an Apple thing, it was that > > burners weren't available in large numbers in slot form, and Jobs > > insisted on having a slot not a tray loader. > > > > He really, really didn't like the 1st gen iMacs that had tray loaders. > > I miss Steve Jobs's obsessive and unreasonable demands. Half the time he > was completely wrong about the value of what he wanted, but it meant > there was always a direction and and aim. > > The idea that someone spent 9 months refusing to allow a certain iPhone > to be manufactured because it would be the wrong shade of white is the > kind of small detail that makes the world worth living in. Not because > of the colour, just because someone cared. > > I think that's what I want: that someone cares, and cares about things > that are in some sense unfathomable. > I know what you mean. I was really shocked when the gold MacBook was a very different colour to the gold iPhone. I had one of the latter and was thinking of getting one of the former, but ended up with an MBP instead. The colour was a not insignofocant part of the decision.
[toc] | [prev] | [next] | [standalone]
| From | nospam <nospam@nospam.invalid> |
|---|---|
| Date | 2017-04-19 08:47 -0400 |
| Message-ID | <190420170847494723%nospam@nospam.invalid> |
| In reply to | #117257 |
In article <1n4q6t2.13afscgixgnq1N%real-not-anti-spam-address@apple-juice.co.uk>, D.M. Procida <real-not-anti-spam-address@apple-juice.co.uk> wrote: > > I miss Steve Jobs's obsessive and unreasonable demands. Half the time he > was completely wrong about the value of what he wanted, but it meant > there was always a direction and and aim. > > The idea that someone spent 9 months refusing to allow a certain iPhone > to be manufactured because it would be the wrong shade of white is the > kind of small detail that makes the world worth living in. Not because > of the colour, just because someone cared. not quite. what happened was apple had all sorts of problems making the white iphone 4 without it discolouring, plus the white had an effect on the camera when the flash was used. they fucked up and the nearly 1 year delay was an embarrassment.
[toc] | [prev] | [next] | [standalone]
| From | nospam <nospam@nospam.invalid> |
|---|---|
| Date | 2017-04-19 08:47 -0400 |
| Message-ID | <190420170847474621%nospam@nospam.invalid> |
| In reply to | #117256 |
In article <eloqd7F39rqU1@mid.individual.net>, Ian McCall <ian@eruvia.org> wrote: > >> I still think building the Bondi Blue like they did > >> was the right choice, > > > > it was, but not having a cd burner was still a mistake. > > > > perhaps a minor one in retrospect, but still a mistake. > > From memory, in the Jobs biography they talk about his disappointment > with the CD-ROM. The answer wasn't really an Apple thing, it was that > burners weren't available in large numbers in slot form, and Jobs > insisted on having a slot not a tray loader. except that the first imac had a tray loader so the availability of slot load burners was not an issue > He really, really didn't like the 1st gen iMacs that had tray loaders. he didn't like a lot of things. sometimes they made sense and sometimes not.
[toc] | [prev] | [next] | [standalone]
| From | Ian McCall <ian@eruvia.org> |
|---|---|
| Date | 2017-04-20 08:35 +0100 |
| Message-ID | <elr6mrFhf8qU1@mid.individual.net> |
| In reply to | #117259 |
On 2017-04-19 12:47:47 +0000, nospam <nospam@nospam.invalid> said: > In article <eloqd7F39rqU1@mid.individual.net>, Ian McCall > <ian@eruvia.org> wrote: > >> From memory, in the Jobs biography they talk about his disappointment >> with the CD-ROM. The answer wasn't really an Apple thing, it was that >> burners weren't available in large numbers in slot form, and Jobs >> insisted on having a slot not a tray loader. > > except that the first imac had a tray loader so the availability of > slot load burners was not an issue https://books.google.co.uk/books?id=6e4cDvhrKhgC&pg=PA356&lpg=PA356&dq=steve+jobs+slot+loading+cd+imac&source=bl&ots=ckySBeS4aa&sig=KbP2YyOEsx0i0GoS9u7XrFc6niA&hl=en&sa=X&ved=0ahUKEwj8mNjv3rHTAhXOUlAKHcHfAQUQ6AEITjAG#v=onepage&q=steve%20jobs%20slot%20loading%20cd%20imac&f=false Cheers, Ian
[toc] | [prev] | [next] | [standalone]
| From | nospam <nospam@nospam.invalid> |
|---|---|
| Date | 2017-04-20 10:22 -0400 |
| Message-ID | <200420171022034344%nospam@nospam.invalid> |
| In reply to | #117266 |
In article <elr6mrFhf8qU1@mid.individual.net>, Ian McCall <ian@eruvia.org> wrote: > > > >> From memory, in the Jobs biography they talk about his disappointment > >> with the CD-ROM. The answer wasn't really an Apple thing, it was that > >> burners weren't available in large numbers in slot form, and Jobs > >> insisted on having a slot not a tray loader. > > > > except that the first imac had a tray loader so the availability of > > slot load burners was not an issue > > > https://books.google.co.uk/books?id=6e4cDvhrKhgC&pg=PA356&lpg=PA356&dq=steve+j > obs+slot+loading+cd+imac&source=bl&ots=ckySBeS4aa&sig=KbP2YyOEsx0i0GoS9u7XrFc6 > niA&hl=en&sa=X&ved=0ahUKEwj8mNjv3rHTAhXOUlAKHcHfAQUQ6AEITjAG#v=onepage&q=steve > %20jobs%20slot%20loading%20cd%20imac&f=false links need to be delimited with <> and that link already expired.
[toc] | [prev] | [next] | [standalone]
| From | richard@cogsci.ed.ac.uk (Richard Tobin) |
|---|---|
| Date | 2017-04-20 14:51 +0000 |
| Message-ID | <odaht6$2gbj$1@macpro.inf.ed.ac.uk> |
| In reply to | #117269 |
In article <200420171022034344%nospam@nospam.invalid>, nospam <nospam@nospam.invalid> wrote: >> https://books.google.co.uk/books?id=6e4cDvhrKhgC&pg=PA356&lpg=PA356&dq=steve+j >> obs+slot+loading+cd+imac&source=bl&ots=ckySBeS4aa&sig=KbP2YyOEsx0i0GoS9u7XrFc6 >> niA&hl=en&sa=X&ved=0ahUKEwj8mNjv3rHTAhXOUlAKHcHfAQUQ6AEITjAG#v=onepage&q=steve >> %20jobs%20slot%20loading%20cd%20imac&f=false > links need to be delimited with <> That's entirely a matter of the newsreader you're using. > and that link already expired. Works fine for me. -- Richard
[toc] | [prev] | [next] | [standalone]
| From | nospam <nospam@nospam.invalid> |
|---|---|
| Date | 2017-04-20 11:57 -0400 |
| Message-ID | <200420171157186424%nospam@nospam.invalid> |
| In reply to | #117271 |
In article <odaht6$2gbj$1@macpro.inf.ed.ac.uk>, Richard Tobin <richard@cogsci.ed.ac.uk> wrote: > >> https://books.google.co.uk/books?id=6e4cDvhrKhgC&pg=PA356&lpg=PA356&dq=stev > >> e+j > >> > >> obs+slot+loading+cd+imac&source=bl&ots=ckySBeS4aa&sig=KbP2YyOEsx0i0GoS9u7Xr > >> Fc6 > >> > >> niA&hl=en&sa=X&ved=0ahUKEwj8mNjv3rHTAhXOUlAKHcHfAQUQ6AEITjAG#v=onepage&q=st > >> eve > >> %20jobs%20slot%20loading%20cd%20imac&f=false > > > links need to be delimited with <> > > That's entirely a matter of the newsreader you're using. absolutely wrong. <> delimiters are specified in an rfc for a reason, so that *any* app (not just newsreaders) can detect a url even if it has embedded line breaks, whitespace and even quote characters as well as making the entire url (not just part of it) clickable. any software that does not support delimiters is broken. > > and that link already expired. > > Works fine for me. not for me. i see page not available. links to pages in books on google will expire and are often tied to the person linking them too.
[toc] | [prev] | [next] | [standalone]
| From | David Kennedy <davidkennedy@nospamherethankyou.invalid> |
|---|---|
| Date | 2017-04-20 21:00 +0100 |
| Message-ID | <Lp6dnZ47qIv-jmTFnZ2dnUU78d-dnZ2d@brightview.co.uk> |
| In reply to | #117272 |
On 20/04/2017 16:57, nospam wrote: > In article <odaht6$2gbj$1@macpro.inf.ed.ac.uk>, Richard Tobin > <richard@cogsci.ed.ac.uk> wrote: > >>>> https://books.google.co.uk/books?id=6e4cDvhrKhgC&pg=PA356&lpg=PA356&dq=stev >>>> e+j >>>> >>>> obs+slot+loading+cd+imac&source=bl&ots=ckySBeS4aa&sig=KbP2YyOEsx0i0GoS9u7Xr >>>> Fc6 >>>> >>>> niA&hl=en&sa=X&ved=0ahUKEwj8mNjv3rHTAhXOUlAKHcHfAQUQ6AEITjAG#v=onepage&q=st >>>> eve >>>> %20jobs%20slot%20loading%20cd%20imac&f=false >> >>> links need to be delimited with <> >> >> That's entirely a matter of the newsreader you're using. > > absolutely wrong. > Absolutely right. > <> delimiters are specified in an rfc for a reason, so that *any* app > (not just newsreaders) can detect a url even if it has embedded line > breaks, whitespace and even quote characters as well as making the > entire url (not just part of it) clickable. > > any software that does not support delimiters is broken. > >>> and that link already expired. >> >> Works fine for me. > > not for me. i see page not available. > > links to pages in books on google will expire and are often tied to the > person linking them too. > It worked fine here. -- David Kennedy http://www.anindianinexile.com
[toc] | [prev] | [next] | [standalone]
| From | nospam <nospam@nospam.invalid> |
|---|---|
| Date | 2017-04-20 16:20 -0400 |
| Message-ID | <200420171620303982%nospam@nospam.invalid> |
| In reply to | #117278 |
In article <Lp6dnZ47qIv-jmTFnZ2dnUU78d-dnZ2d@brightview.co.uk>, David Kennedy <davidkennedy@nospamherethankyou.invalid> wrote: > >>> links need to be delimited with <> > >> > >> That's entirely a matter of the newsreader you're using. > > > > absolutely wrong. > > > Absolutely right. nope. <> delimiters have nothing whatsoever to do with newsreaders.
[toc] | [prev] | [next] | [standalone]
| From | richard@cogsci.ed.ac.uk (Richard Tobin) |
|---|---|
| Date | 2017-04-20 20:07 +0000 |
| Message-ID | <odb4eu$2pgk$1@macpro.inf.ed.ac.uk> |
| In reply to | #117272 |
In article <200420171157186424%nospam@nospam.invalid>,
nospam <nospam@nospam.invalid> wrote:
>> > links need to be delimited with <>
>> That's entirely a matter of the newsreader you're using.
>absolutely wrong.
>
><> delimiters are specified in an rfc for a reason, so that *any* app
>(not just newsreaders) can detect a url even if it has embedded line
>breaks, whitespace and even quote characters as well as making the
>entire url (not just part of it) clickable.
>
>any software that does not support delimiters is broken.
You're just making that up. Here is what the relevant RFC (3986)
really says:
In practice, URIs are delimited in a variety of ways, but usually
within double-quotes "http://example.com/", angle brackets
<http://example.com/>, or just by using whitespace:
http://example.com/
These wrappers do not form part of the URI.
In some cases, extra whitespace (spaces, line-breaks, tabs, etc.)
may have to be added to break a long URI across lines. The
whitespace should be ignored when the URI is extracted.
[...]
Using <> angle brackets around each URI is especially recommended
as a delimiting style for a reference that contains embedded
whitespace.
So, angle bracket delimiters are just one of several ways to do it,
and since the URI didn't contain whitespace, they're not even
especially recommended. It's not a normative requirement, even if the
newsreader claims to conform to the RFC, and it's certainly not a
requirement on authors.
Your statement "links need to be delimited with <>" is just completely
false.
>> > and that link already expired.
>> Works fine for me.
>not for me. i see page not available.
>
>links to pages in books on google will expire and are often tied to the
>person linking them too.
Since it worked for me, obviously neither of those excuses applies.
-- Richard
[toc] | [prev] | [next] | [standalone]
| From | nospam <nospam@nospam.invalid> |
|---|---|
| Date | 2017-04-20 16:20 -0400 |
| Message-ID | <200420171620304017%nospam@nospam.invalid> |
| In reply to | #117279 |
In article <odb4eu$2pgk$1@macpro.inf.ed.ac.uk>, Richard Tobin <richard@cogsci.ed.ac.uk> wrote: > In article <200420171157186424%nospam@nospam.invalid>, > nospam <nospam@nospam.invalid> wrote: > > >> > links need to be delimited with <> > > >> That's entirely a matter of the newsreader you're using. > > >absolutely wrong. > > > ><> delimiters are specified in an rfc for a reason, so that *any* app > >(not just newsreaders) can detect a url even if it has embedded line > >breaks, whitespace and even quote characters as well as making the > >entire url (not just part of it) clickable. > > > >any software that does not support delimiters is broken. > > You're just making that up. nope. > Here is what the relevant RFC (3986) > really says: > > In practice, URIs are delimited in a variety of ways, but usually > within double-quotes "http://example.com/", angle brackets > <http://example.com/>, or just by using whitespace: > > http://example.com/ > > These wrappers do not form part of the URI. > > In some cases, extra whitespace (spaces, line-breaks, tabs, etc.) > may have to be added to break a long URI across lines. The > whitespace should be ignored when the URI is extracted. > > [...] > > Using <> angle brackets around each URI is especially recommended > as a delimiting style for a reference that contains embedded > whitespace. by providing the link, you *prove* i didn't make it up. > So, angle bracket delimiters are just one of several ways to do it, <> are the de facto standard. quotes are *very* rarely used. > and since the URI didn't contain whitespace, it did. > they're not even > especially recommended. it is recommended as defined by the very link you provided. > It's not a normative requirement, even if the > newsreader claims to conform to the RFC, and it's certainly not a > requirement on authors. <> delimiters allows apps (not just newsreaders, another one of your mistakes) to identify a url, particularly one that spans lines and also make it clickable. adding just two characters makes things easier for everyone and has zero effect on the person adding them. it's a courtesy. > Your statement "links need to be delimited with <>" is just completely > false. it's very true and you even showed the relevant link. perhaps you should reread it.
[toc] | [prev] | [next] | [standalone]
| From | richard@cogsci.ed.ac.uk (Richard Tobin) |
|---|---|
| Date | 2017-04-20 20:51 +0000 |
| Message-ID | <odb71d$2que$1@macpro.inf.ed.ac.uk> |
| In reply to | #117281 |
In article <200420171620304017%nospam@nospam.invalid>, nospam <nospam@nospam.invalid> wrote: >by providing the link, you *prove* i didn't make it up. It doesn't say what you said it did. Which is unsurprising, since you never actually provide references yourself, but just assert that they exist, presumably from a faulty memory. >> and since the URI didn't contain whitespace, >it did. Here's the URI again. Feel free to point to the whitespace in it: https://books.google.co.uk/books?id=6e4cDvhrKhgC&pg=PA356&lpg=PA356&dq=steve+jobs+slot+loading+cd+imac&source=bl&ots=ckySBeS4aa&sig=KbP2YyOEsx0i0GoS9u7XrFc6niA&hl=en&sa=X&ved=0ahUKEwj8mNjv3rHTAhXOUlAKHcHfAQUQ6AEITjAG#v=onepage&q=steve%20jobs%20slot%20loading%20cd%20imac&f=false Perhaps your newsreader incorrectly displayed it with whitespace? That would explain why you can't follow it while others can. ><> delimiters allows apps (not just newsreaders, another one of your >mistakes) to identify a url, particularly one that spans lines and also >make it clickable. > >adding just two characters makes things easier for everyone and has >zero effect on the person adding them. it's a courtesy. Blah blah blah. First it was "links need to be delimited with <>", now it just "makes things easier for everyone", and even that isn't true. -- Richard
[toc] | [prev] | [next] | [standalone]
| From | nospam <nospam@nospam.invalid> |
|---|---|
| Date | 2017-04-20 17:15 -0400 |
| Message-ID | <200420171715221524%nospam@nospam.invalid> |
| In reply to | #117282 |
In article <odb71d$2que$1@macpro.inf.ed.ac.uk>, Richard Tobin <richard@cogsci.ed.ac.uk> wrote: > >by providing the link, you *prove* i didn't make it up. > > It doesn't say what you said it did. yes it does. > Which is unsurprising, since you > never actually provide references yourself, but just assert that they > exist, presumably from a faulty memory. i *always* provide references when asked, and in this case, you provided the reference for me. > >> and since the URI didn't contain whitespace, > > >it did. > > Here's the URI again. Feel free to point to the whitespace in it: at the end of every line. and before you try to argue that's not whitespace, you should check the rfc for what whitespace actually *is*: > In some cases, extra whitespace (spaces, line-breaks, tabs, etc.) > may have to be added to break a long URI across lines. The > whitespace should be ignored when the URI is extracted. > https://books.google.co.uk/books?id=6e4cDvhrKhgC&pg=PA356&lpg=PA356&dq=steve+j > obs+slot+loading+cd+imac&source=bl&ots=ckySBeS4aa&sig=KbP2YyOEsx0i0GoS9u7XrFc6 > niA&hl=en&sa=X&ved=0ahUKEwj8mNjv3rHTAhXOUlAKHcHfAQUQ6AEITjAG#v=onepage&q=steve > %20jobs%20slot%20loading%20cd%20imac&f=false > > Perhaps your newsreader incorrectly displayed it with whitespace? unless a url fits in one line, which the above one clearly does not, there is guaranteed to be whitespace. that's why <> delimiters are needed, so that software can properly identify urls regardless of whitespace. > That would explain why you can't follow it while others can. wrong again. when i copy/paste, which i had to do because there were no delimiters, i see this: <http://i.imgur.com/FXf1o9Y.png> blame google, not me. > ><> delimiters allows apps (not just newsreaders, another one of your > >mistakes) to identify a url, particularly one that spans lines and also > >make it clickable. > > > >adding just two characters makes things easier for everyone and has > >zero effect on the person adding them. it's a courtesy. > > Blah blah blah. First it was "links need to be delimited with <>", they do > now it just "makes things easier for everyone", it does. > and even that isn't > true. it is. there is *no* downside in delimiting urls.
[toc] | [prev] | [next] | [standalone]
| From | richard@cogsci.ed.ac.uk (Richard Tobin) |
|---|---|
| Date | 2017-04-20 21:36 +0000 |
| Message-ID | <odb9l3$2s0d$1@macpro.inf.ed.ac.uk> |
| In reply to | #117283 |
In article <200420171715221524%nospam@nospam.invalid>, nospam <nospam@nospam.invalid> wrote: >> Here's the URI again. Feel free to point to the whitespace in it: >at the end of every line. No, there are no line breaks in it. Your newsreader must be inserting them. It's a single long line. >when i copy/paste, which i had to do because there were no delimiters, >i see this: ><http://i.imgur.com/FXf1o9Y.png> When *I* cut and paste it, I see the correct page. -- Richard
[toc] | [prev] | [next] | [standalone]
| From | nospam <nospam@nospam.invalid> |
|---|---|
| Date | 2017-04-20 17:43 -0400 |
| Message-ID | <200420171743504028%nospam@nospam.invalid> |
| In reply to | #117285 |
In article <odb9l3$2s0d$1@macpro.inf.ed.ac.uk>, Richard Tobin <richard@cogsci.ed.ac.uk> wrote: > >when i copy/paste, which i had to do because there were no delimiters, > >i see this: > ><http://i.imgur.com/FXf1o9Y.png> > > When *I* cut and paste it, I see the correct page. at some point, you won't. links to specific pages in books *expire*.
[toc] | [prev] | [next] | [standalone]
| From | {$PW$}@womar.co.uk (Paul Womar) |
|---|---|
| Date | 2017-04-21 12:49 +0100 |
| Message-ID | <1n4u0sx.e49cjk11yttbfN%{$PW$}@womar.co.uk> |
| In reply to | #117283 |
nospam <nospam@nospam.invalid> wrote: > In article <odb71d$2que$1@macpro.inf.ed.ac.uk>, Richard Tobin > <richard@cogsci.ed.ac.uk> wrote: > > https://books.google.co.uk/books?id=6e4cDvhrKhgC&pg=PA356&lpg=PA356&dq=s > > teve+j > > obs+slot+loading+cd+imac&source=bl&ots=ckySBeS4aa&sig=KbP2YyOEsx0i0GoS9u > > 7XrFc6 > > niA&hl=en&sa=X&ved=0ahUKEwj8mNjv3rHTAhXOUlAKHcHfAQUQ6AEITjAG#v=onepage&q > > =steve %20jobs%20slot%20loading%20cd%20imac&f=false > > > > Perhaps your newsreader incorrectly displayed it with whitespace? > > unless a url fits in one line, which the above one clearly does not, > there is guaranteed to be whitespace. In my newsreader it is made abundantly clear that it DOES fit on one line, it won't let me repost it as one long line though, > > Blah blah blah. First it was "links need to be delimited with <>", > > they do The text gives multiple options for delimiters, <> being one of them, therefore you are wrong. -- -> The email address used in this message *IS* valid <-
[toc] | [prev] | [next] | [standalone]
| From | nospam <nospam@nospam.invalid> |
|---|---|
| Date | 2017-04-21 10:13 -0400 |
| Message-ID | <210420171013515743%nospam@nospam.invalid> |
| In reply to | #117288 |
In article <1n4u0sx.e49cjk11yttbfN%{$PW$}@womar.co.uk>, Paul Womar
<{$PW$}@womar.co.uk> wrote:
>
> The text gives multiple options for delimiters, <> being one of them,
> therefore you are wrong.
<> is the de facto standard. which makes *you* wrong.
[toc] | [prev] | [next] | [standalone]
| From | thnews@poboxmolar.com.invalid (Tim Hodgson) |
|---|---|
| Date | 2017-04-21 17:28 +0100 |
| Message-ID | <1n4udoh.w86zp5kpc9kzN%thnews@poboxmolar.com.invalid> |
| In reply to | #117289 |
nospam <nospam@nospam.invalid> wrote:
> In article <1n4u0sx.e49cjk11yttbfN%{$PW$}@womar.co.uk>, Paul Womar
> <{$PW$}@womar.co.uk> wrote:
>
> >
> > The text gives multiple options for delimiters, <> being one of them,
> > therefore you are wrong.
>
> <> is the de facto standard. which makes *you* wrong.
You previously said he was wrong because angle brackets are "defined in
an RFC". Now you say they're "the de facto standard".
Since you're changing your argument you'll just have to admit you were
wrong the first time. Now, deep breath...
--
TimH
pull tooth to reply by email
[toc] | [prev] | [next] | [standalone]
Page 3 of 5 — ← Prev page 1 2 [3] 4 5 Next page →
Back to top | Article view | uk.comp.sys.mac
csiph-web