The app doesn't need to be installed, in the usual sense. Copy it to your 
Applications folder (cmd-shift-a), but that's more of a housekeeping thing than 
a requirement. Just launch the app to use it, like any other app on the Mac.
> On Nov 6, 2014, at 1:01 PM, Janina Sajka <[email protected]> wrote:
> 
> Janina Sajka writes:
>> Argh.
>> 
>> So, I downloaded the .zip file from colloquy.info, but there's no
>> readme, or any other kind of installation instruction. I'm also not
>> finding any installation instruction on their page.
>> 
>> Looking at the file structure of the exploded .zip, I see the top level
>> directory is colloquy.app, inside of which is a directory called
>> Contents, and inside that a few more. These look very similar to what I
>> see under /Library/"Application Support"/
>> 
>> Do I simply copy this tree to that folder in order to install Colloquy?
>> Do I leave the .app as part of the directory name, or not? i.e. is it:
>> 
>> /Library/Application Support/colloquy.app        or
>> /Library/Application Support/colloquy
>> 
>> Does it matter?
>> 
>> I know I've done this once or twice before, but don't recall the
>> specifics, so appreciate any guidance.
>> 
>> tia
>> 
>> Janina
>> 
>> 'Chris Blouch' via MacVisionaries writes:
>>> Not all apps are in the iTunes store. Some don't want to bother with the
>>> whole submission/review process for various reasons, especially the free
>>> open-source apps.
>>> 
>>> CB
>>> 
>>> On 11/5/14, 4:00 PM, Janina Sajka wrote:
>>>> This was also James Craig's suggestion to me, when I asked him last
>>>> week. However, he did indicate there were still issues.
>>>> 
>>>> Also, when I tried to find it on iTunes, I came up empty.
>>>> 
>>>> Janina
>>>> 
>>>> 'Chris Blouch' via MacVisionaries writes:
>>>>> Years ago I remember hearing that Colloquy was accessible but I think it
>>>>> relied on Growl to speak incoming messages. It's an OSX (not terminal) app
>>>>> and free so might be worth giving it a try.
>>>>> 
>>>>> http://colloquy.info
>>>>> 
>>>>> CB
>>>>> 
>>>>> On 11/5/14, 2:30 PM, Janina Sajka wrote:
>>>>>> Hi, Deedra:
>>>>>> 
>>>>>> I'm not so sure it's an actual plus, just a reasonable work around when
>>>>>> you need one. But, I've not tried actually working with irssi in the
>>>>>> terminal in real time yet. I just came up with the approach and brewed
>>>>>> it up this past Monday following a disasterous week trying to use the
>>>>>> vms on my air during the annual W3C technical plennary conference.
>>>>>> 
>>>>>> My intent is to log in during my next few teleconferences and see how it
>>>>>> tracks. I will still have my Linux desktop as my primary IRC session, so
>>>>>> the IRC session on my Air will be a second, expirimental login to the
>>>>>> W3C IRC channel.
>>>>>> 
>>>>>> I'll be interested to see how well VO keeps up as text scrolls on
>>>>>> screen. I may try to look for something, just to see how effective that
>>>>>> might be. But, come to think of it, I usually depend on Scroll Lock to
>>>>>> freeze the screen when I look for something further back in the
>>>>>> transcript, and I'm not so sure we have that on the Air. Anyone know?
>>>>>> 
>>>>>> So far, my impression of VO in the Terminal is that it will work, if you
>>>>>> need it to work, but it would never be my first choice. It's no Speakup
>>>>>> for sure.
>>>>>> 
>>>>>> Janina
>>>>>> 
>>>>>> Deedra Waters writes:
>>>>>>> Janina, that sounds like a plus there. how much of the terminal actually
>>>>>>> works with voiceover and how well? I'd still be using a lot of terminal
>>>>>>> apps accept for certain things that i want the gui for. so i'd like a
>>>>>>> good idea as to what to expect from the terminal  and ways to make it
>>>>>>> work the best.
>>>>>>> 
>>>>>>> 
>>>>>>> -- 
>>>>>>> Website: http://deedra.the-brannons.com
>>>>>>> blog: http://deedra.the-brannons.com/blog
>>>>>>> 
>>>>>>> -- 
>>>>>>> You received this message because you are subscribed to the Google 
>>>>>>> Groups "MacVisionaries" group.
>>>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>>>>> an email to [email protected].
>>>>>>> To post to this group, send email to [email protected].
>>>>>>> Visit this group at http://groups.google.com/group/macvisionaries.
>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>> -- 
>>>>> ¯\_(ツ)_/¯
>>>>> 
>>>>> -- 
>>>>> You received this message because you are subscribed to the Google Groups 
>>>>> "MacVisionaries" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>>>> email to [email protected].
>>>>> To post to this group, send email to [email protected].
>>>>> Visit this group at http://groups.google.com/group/macvisionaries.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>> 
>>> -- 
>>> ¯\_(ツ)_/¯
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "MacVisionaries" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to [email protected].
>>> To post to this group, send email to [email protected].
>>> Visit this group at http://groups.google.com/group/macvisionaries.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> -- 
>> 
>> Janina Sajka,        Phone:  +1.443.300.2200
>>                      sip:[email protected]
>>              Email:  [email protected]
>> 
>> Linux Foundation Fellow
>> Executive Chair, Accessibility Workgroup:    http://a11y.org
>> 
>> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
>> Chair,       Protocols & Formats     http://www.w3.org/wai/pf
>>      Indie UI                        http://www.w3.org/WAI/IndieUI/
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "MacVisionaries" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected].
>> To post to this group, send email to [email protected].
>> Visit this group at http://groups.google.com/group/macvisionaries.
>> For more options, visit https://groups.google.com/d/optout.
> 
> Hi, All:
> 
> I wanted to ask whether I just missed something during the upgrade from
> Mavericks to Yosemite, or whether others have seen what I experienced.
> 
> I followed up on my emailed invitation from Apple to upgrade. I did my
> best to pay careful attention to all the prompts. I attained a
> successful install eventually, or so I believed.
> 
> Imagine my surprise, then, when I was unable to log in. The familiar
> login screen where I select my user, then tab and VO+Down to enter my
> password didn't come up. In fact, the only way I knew my machine wasn't
> dead was that the battery was warm.
> 
> Once I got sighted assistance, it transpired that my ssd had been
> encrypted. I don't recall agreeing, and it turns out that mattered a
> lot.
> 
> The old login screens no longer apply, it seems, when your drive is
> encrypted. In fact, VO can't really work at the login screen to an
> encrypted drive. Instead, apple provides some pre-recorded prompts that
> are played when you Command+F5.
> 
> You can tab and hear a prompt for username, but there's no echo as you
> type.
> 
> You can tab again and hear a prompt for password, and you do get a click
> per keystroke, though with much more lag than usual.
> 
> If you tab again and successfully log in, you (usually) get three beeps.
> Thought I didn't always hear those three beeps, they indicate successful
> log in. One beep means "put in your username," and two means "put in
> your password."
> 
> If the machine decides that you've been mis-entering your password,
> you're dumped into a screen that offers to let you reset your password.
> This turns out to have its own set of gotchya's. You may, or may not, be
> able to Esc out to ausername plus password login screen.
> 
> Last Friday evening I found myself alone in my hotel room unable to get
> out of that screen. I tried changing my password, but this took me into
> screens for which there were no recorded prompts. I had to go find
> sighted assistance.
> 
> Once I got past part of the inaccessible "change password" screen, I was
> given the message that my new password didn't match what was stored in
> my Keychain file. To clear that hurdle, I had to enter my old password.
> Imagine that.
> 
> Well, I got through all that, and got the machine booted. But, I haven't
> dared shutdown or reboot unless I have someone sighted at hand just in
> case. This just ain't right. Am I the lone stranger with this situation?
> 
> Janina
> 
> -- 
> 
> Janina Sajka, Phone:  +1.443.300.2200
>                       sip:[email protected]
>               Email:  [email protected]
> 
> Linux Foundation Fellow
> Executive Chair, Accessibility Workgroup:     http://a11y.org
> 
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Chair,        Protocols & Formats     http://www.w3.org/wai/pf
>       Indie UI                        http://www.w3.org/WAI/IndieUI/
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "MacVisionaries" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/macvisionaries.
> For more options, visit https://groups.google.com/d/optout.


--
Have a great day,
Alex Hall
[email protected]

-- 
You received this message because you are subscribed to the Google Groups 
"MacVisionaries" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/macvisionaries.
For more options, visit https://groups.google.com/d/optout.

Reply via email to