public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Luke Davis <ldavis@shellworld.net>
To: blinux-list@redhat.com
Subject: Re: linux, and audio.
Date: Sun, 25 Nov 2001 19:01:42 -0500 (EST)	[thread overview]
Message-ID: <Pine.BSF.4.42.0111251900220.51356-100000@server1.shellworld.net> (raw)
In-Reply-To: <Pine.LNX.4.40.0111251516580.862-100000@beethoven.wgaughan.net>

One thing you can do, is press "E" on those links that are unsupported.
It will then show the link text, and if it contains an URL, you can edit
it down to just that URL, you should be able to access it.

Luke


On Sun, 25 Nov 2001, Bill Gaughan wrote:

> Does anyone know of the direct audio feed address for "Dreamland" with
> Whitley Strieber? And, how come some live365 sites let you have access
> with "trplayer" thru "lynx" and others don't? How is it that some audio
> sites give you ads without invoking JavaScript. I am not a C++ programmer,
> but, we have simply got to find a way around this "unsupported url scheme"
> message we all get when we try to invoke JavaScript in lynx. I fear that
> lynx and maybe linux, will soon be useless to us all unless we gain full
> meaningful and understandable access to X-Windows and X applications like
> Netscape for Linux. I fear that, once again, we will be left behind, or
> forced to stumble thru the jumble of MS Windows software products.
>
> Until computers and the computer hardware and software industry develop
> national and international uniform standards, computers will continue to
> be useful toys. Just look at what a disaster internet radio has become
> with the folding of netradio.com last month. Not to speak of the disaster
> the dispute over royalty pay to announcers and advertising actors has done
> to internet radio. Many broadcasts have pulled content from the internet
> because of the fear of lawsuits, because the actors guild that records the
> advertisements wants to be payed twice on their royalties, once for
> conventional media (radio) and again for being broadcast on the internet.
>
>




  reply	other threads:[~ UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 cbowman
 ` philwh
   ` cbowman
 ` A. R. Vener
   ` cbowman
     ` L. C. Robinson
 ` Bill Gaughan
   ` Dave Hunt
   ` A. R. Vener
     ` Bill Gaughan
 ` Bill Gaughan
   ` Luke Davis [this message]
   ` L. C. Robinson
     ` Brent Harding
 ` brltty and simultaneous grade 2 translation Bill Gaughan
   ` Dave Mielke
     ` John J. Boyer
       ` Dave Mielke
         ` John J. Boyer
           ` Dave Mielke
             ` John J. Boyer
               ` Dave Mielke
                 ` John J. Boyer
                   ` Dave Mielke
                     ` John J. Boyer
                       ` Dave Mielke
                       ` Nicolas Pitre
                         ` John J. Boyer
                           ` Nicolas Pitre
                             ` John J. Boyer
                   ` Nicolas Pitre
         ` Bill Gaughan
           ` John J. Boyer
             ` Bill Gaughan
               ` John J. Boyer
           ` Nicolas Pitre
             ` John J. Boyer
           ` Dave Mielke
         ` Nicolas Pitre
 linux, and audio cbowman

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=Pine.BSF.4.42.0111251900220.51356-100000@server1.shellworld.net \
    --to=ldavis@shellworld.net \
    --cc=blinux-list@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).