Issue installing Cox Rhapsody browser plugin

[sean.terrell-j9pdmedNgrk at public.gmane.org (Sean Terrell)]

All, 

Just bought into cox rhapsody, trying to install the browser plugin for

manager upon download of the .js file, and when I click install the
following error is presented :

Firefox could not install the file at 

http://static.realone.com/corhapsody/plugins/unix/rhapx/RhapsodyPlayerEngine_Inst_Linux.xpi

because: Install script not found
-204


Does anyone have rhapsody working on a linux distro? 


Thanks 



Sean Terrell 
SSN TWCS Post Development 
Systems Engineering Associates Corporation
62 Johnny Cake Hill
Middletown RI 02842
(401) 359-3045 (m)
(401) 847-2260 (o)
sterrell-+s5NDHfU3UFBDgjK7y7TUQ at public.gmane.org
www.seacorp.com 


-----Original Message-----
From: discuss-request-mNDKBlG2WHs at public.gmane.org
Reply-to: discuss-mNDKBlG2WHs at public.gmane.org
To: discuss-mNDKBlG2WHs at public.gmane.org
Subject: Discuss Digest, Vol 34, Issue 14
Date: Wed, 11 Aug 2010 12:00:03 -0400

Send Discuss mailing list submissions to
	discuss-mNDKBlG2WHs at public.gmane.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.blu.org/mailman/listinfo/discuss
or, via email, send a message with subject or body 'help' to
	discuss-request-mNDKBlG2WHs at public.gmane.org

You can reach the person managing the list at
	discuss-owner-mNDKBlG2WHs at public.gmane.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Discuss digest..."


Today's Topics:

   1. RE: VI annoyance (Edward Ned Harvey)
   2. Re: VI annoyance (Grant M)
   3. Re: VI annoyance (Ben Eisenbraun)
   4. Re: VI annoyance (Ian Stokes-Rees)
   5. Re: VI annoyance (Jerry Feldman)


----------------------------------------------------------------------

Message: 1
Date: Wed, 11 Aug 2010 09:19:07 -0400
From: Edward Ned Harvey <blu-Z8efaSeK1ezqlBn2x/YWAg at public.gmane.org>
Subject: RE: VI annoyance
To: "'Matt Shields'" <matt-urrlRJtNKRMsHrnhXWJB8w at public.gmane.org>
Cc: Boston LUG <discuss-mNDKBlG2WHs at public.gmane.org>
Message-ID: <000a01cb3957$cabf8c40$603ea4c0$@com>
Content-Type: text/plain; charset="us-ascii"

I use the following settings, regardless of putty, xterm, vnc, terminal, or
whatever.  These were carefully selected to eliminate problems like ...
Characters not appearing on the terminal when I was ssh'd in from a mac.
And weird characters appearing instead of actual highlighting when I'm
reading a man page.  And stuff like that.

 

In solaris, I use:

export LANG=en_US.UTF-8

export LC_ALL=C

export SUPPORTED=en_US:en

export TERM=xterm

 

In RHEL4/Centos4, I use:

export LANG=en_US

export SUPPORTED=en_US:en

export TERM=xterm

 

This is such an easy test, I would recommend trying it before dismissing it.
;-)

 





From: Matt Shields [mailto:matt-urrlRJtNKRMsHrnhXWJB8w at public.gmane.org] 
Sent: Wednesday, August 11, 2010 8:53 AM
To: Edward Ned Harvey
Cc: Boston LUG
Subject: Re: VI annoyance

 

On Wed, Aug 11, 2010 at 8:44 AM, Edward Ned Harvey <blu-Z8efaSeK1ezqlBn2x/YWAg at public.gmane.org>
wrote:

> From: discuss-bounces-mNDKBlG2WHs at public.gmane.org [mailto:discuss-bounces-mNDKBlG2WHs at public.gmane.org] On
> Behalf Of Matt Shields

>
> But, now I have a bunch of Ubuntu boxes I need to manage and I have
> this
> weird issue where I can go into insert mode but if I do anything other
> than
> type characters (like arrow keys, or delete) it stays in insert mode

You may be right about .vimrc goodies, but I don't guess so.  I think the
first thing you should look at is whether you're actually using vi, or vim.
For example in solaris, vi is the default, so I install vim, and then alias
vi=vim.  Because vim is better.

Also, if you don't have your terminal properly set up, it can cause really
weird behavior.  Is this behavior the same on the local physical console?
Or does this behavior only happen over the network via ssh?

In addition to all of the above, gvim is yet another step above and beyond
vim.  Assuming you have graphics.


See previous note about vi is actually a symlink to vim on all servers.  I
can reproduce the problem from Windows (SecureCRT), Linux (Gnome Term), OSX
(Terminal and ZOC) and from server's local terminal.

Term is set for "Linux" in all terminal instances.

By any other .vimrc goodies, I was wondering if anyone had any good
options/functions, etc that they use and would like to share.

-matt





------------------------------

Message: 2
Date: Wed, 11 Aug 2010 09:27:28 -0400
From: Grant M <gmongardi-cGmSLFmkI3Y at public.gmane.org>
Subject: Re: VI annoyance
To: blug <discuss-mNDKBlG2WHs at public.gmane.org>
Message-ID: <4C62A540.4060901-cGmSLFmkI3Y at public.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1

If you actually type "vim filename" does it behave differently? I seem
to recall that it did on some platform I worked on. On whatever that
particular OS was, if you typed "vi filename" it behaved like the
original "vi", but if you typed "vim filename" it had all of the
features of a recent vim version. Both commands ran the same vim binary,
but somehow using 'vi' changed the behavior.

Grant M.
-- 
Grant Mongardi
Senior Systems Engineer
NAPC

gmongardi-cGmSLFmkI3Y at public.gmane.org
http://www.napc.com/
blog.napc.com
781.894.3114 phone
781.894.3997 fax

NAPC | technology matters




------------------------------

Message: 3
Date: Wed, 11 Aug 2010 10:32:31 -0400
From: Ben Eisenbraun <bene-Gk2boCrsRs1AfugRpC6u6w at public.gmane.org>
Subject: Re: VI annoyance
To: Matt Shields <matt-urrlRJtNKRMsHrnhXWJB8w at public.gmane.org>
Cc: Boston LUG <discuss-mNDKBlG2WHs at public.gmane.org>
Message-ID: <20100811143231.GP25629-94UyQDRuE6+6C/VWWv79Iw at public.gmane.org>
Content-Type: text/plain; charset=us-ascii

Hi Matt,

On Wed, Aug 11, 2010 at 08:42:21AM -0400, Matt Shields wrote:
> Just to add further notes.  I looked at the differences between my
> RHEL/CentOS/Fedora systems and my Ubuntu systems and tried some of the
> settings that were in /etc/vimrc and /etc/vim/vimrc (respectively).  I tried
> a few of the differences out on one Ubuntu system and "set nocompatible"
> seems to make vi act like I'm used to.

You answered your own question.  Vim, with 'set compatible', will act like
vi, which doesn't understand the arrow keys as movement characters.  To
turn it off, just use 'set nocompatible'.

http://vimdoc.sourceforge.net/htmldoc/options.html#%27compatible%27

-ben

--
faced with the choice between changing one's mind and proving that there
is no need to do so, almost everyone gets busy on the proof.
                                                <john kenneth galbraith>


------------------------------

Message: 4
Date: Wed, 11 Aug 2010 11:12:48 -0400
From: Ian Stokes-Rees <ijstokes-/2FeUQLD3jedFdvTe/nMLpVzexx5G7lz at public.gmane.org>
Subject: Re: VI annoyance
To: Boston LUG <discuss-mNDKBlG2WHs at public.gmane.org>
Message-ID: <4C62BDF0.9010403-/2FeUQLD3jedFdvTe/nMLpVzexx5G7lz at public.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1


>> Also, does anyone have any .vimrc goodies?
>>

You can get pretty far with a look around the VIM scripts area:

http://www.vim.org/scripts/

(then Browse All, and sort by ranking or downloads)

I have a fairly basic .vimrc file:

syn on
set ts=4
set sw=4
set expandtab

filetype plugin on
set bg=dark

I find that if I *don't* have these settings on some new system or
account, I pretty quickly scp over this .vimrc.

Ian


------------------------------

Message: 5
Date: Wed, 11 Aug 2010 11:24:30 -0400
From: Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org>
Subject: Re: VI annoyance
To: discuss-mNDKBlG2WHs at public.gmane.org
Message-ID: <4C62C0AE.5050704-mNDKBlG2WHs at public.gmane.org>
Content-Type: text/plain; charset="iso-8859-1"

On 08/11/2010 09:27 AM, Grant M wrote:
> If you actually type "vim filename" does it behave differently? I seem
> to recall that it did on some platform I worked on. On whatever that
> particular OS was, if you typed "vi filename" it behaved like the
> original "vi", but if you typed "vim filename" it had all of the
> features of a recent vim version. Both commands ran the same vim binary,
> but somehow using 'vi' changed the behavior.
>
> Grant M.
>   
That is because it uses the name it was called by to set its behavior.
For instances, if you type 'ex filename' you will be in ex mode, but the
executable will still be vim.  The grep and egrep commands work the same
way. /bin/egrep is symlinked to /bin/grep, but the behavior is as if you
typed 'grep -E'. This is a technique that has been used in Unix for the
past 40 years (except Unix generally hard links the commands where Linux
normally symlinks). Remember that the first argument (in C argv[0]) is
always the name of the command that was typed on the command line or
executed through X. The command then sets its behavior based on that.
So, if you type 'view filename' the behavior will be that 'filename' is
edited as read-only.