Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index 

Hi, Tom:  

        
          Thanks again for the reply.  


          I did “cd ~/Library/Application Support/LibreOffice”, then "mv 4 4352”.  That worked.  
However, I was unable to edit any of the paths in LibreOffice (LO4352) to anything that made sense 
to me, e.g., like to subfolders of “~/Library/Application Support/LibreOffice/4352/user”.  In 
LibreOffice: Preferences: LibreOffice: Paths, I can click on, e.g., AutoCorrect, than Edit.  This 
shows a path list of “/Users/sbgraves/Library/Application Support/LibreOffice/4/autocorr”.  I’d 
like to change “4” to “4352”.  I can’t find a way to do that.  Clicking on it doesn’t help.  I can 
click on of the paths, then click “Add”.  This opens in different places for different paths.  I’m 
new to Mac OS X, and I’ve so far failed to understand how to navigate to where I want with the 
alternatives I’m given.  


          I successfully did "mkdir -p libreoffice/builds”, as described in 
“https://wiki.documentfoundation.org/Installing_in_parallel/OS_X";.  Then “cd ~/Library/Application 
Support/LibreOffice” and "cp -r 4352 ~/libreoffice/builds/“ created copies of all the 
subdirectories of the former “4” subdirectory within the new "~/libreoffice/builds/“.  And I was 
able to redirect some but not all of the paths to the new subdirectories of 4352.  


          With this, I was able to install LO 4.3.4.1 and run it.  It seemed to work (though “quit 
unexpectedly” with Tools -> Solver;  however, that’s a separate issue).  


          Thanks again, 
          Spencer 
          


On Jan 21, 2015, at 2:17 PM, Tom Davies <tomcecf@gmail.com> wrote:

Hi :)
I think the intention is to unpack and build the program in the new
folder and then install or move the program to the place it should be.
Maybe.  However I haven't read through the rest of the instructions.
Regards from
Tom :)


On 21 January 2015 at 20:19, Spencer Graves <spencer.graves@prodsyse.com> wrote:

Hi, Tom:



On Jan 21, 2015, at 10:10 AM, Tom Davies <tomcecf@gmail.com> wrote:

Hi :)
These are unix commands so you find them much the same in Gnu&Linux
such as Ubuntu, openSuSE, RedHat, Mageia as well as in BSDs such as
FreeBSD, Mac and others.

cd = Change Directory
ls = LiSt   = roughly the same as "dir" it gives a list of what is in
the folder/directory you are in

I think the cd command is a little wrong but ended up doing the right
thing.  The aim was to get into the "home" folder and you started from
there anyway so when the instruction didn't give a folder to change
into you still ended up in the "home" folder.  I think the instruction
was meant to be

cd ~

or

cd /home/user-name




         Thanks for the reply.  I’m sorry I wasn’t clear:  Before I posted that comment, I 
tested “cd” from different directories and found it to be equivalent to “cd ~” on OS X 10.10.1.  
I just checked and found that Ubuntu 14.04 LTS produced the same result.



but it doesn't matter.  The command;

mkdir -p libreoffice/builds

should MaKe a new directory/folder.  Actually it should create 2 new
folders.  It should create a folder called "libreoffice" and inside
that create a sub-folder called "builds”.



         Yes, except that I’m not sure if that was intended to be taken literally:  LibreOffices 
Preferences:  LibreOffice:  Paths says the default path for Documents under OS X is 
“~/Documents” and for everything else is subdirectories of “~/Library/Application 
Support/LibreOffice/4/user”.  With LO 4.3.4.1 under Windows 7, it’s essentially the same except 
that everything else is in subdirectories of “~\AppData\Roaming\LibreOffice\4\user”.


         This suggests to me that I should cd to the “LibreOffice” directory under 
“~/Library/Application Support on my Mac (or “~\AppData\Roaming” under Windows 7) and create 
rename “4” to something like “4352”, then open LO4352 and change all those paths from “4” to 
“4352” to match.


         Does this make sense?  I haven’t tried it yet, but I plan to if I don’t hear something 
to the contrary first.


         Thanks again,
         Spencer



There are a lot of guides to help with unix commands but Gnu&Linux
tends to have a wider range of commands and some of them are slightly
different from the BSD ones so they just wont work in Mac.  I doubt
they would cause harm but it's probably worth being cautious.  I think
you can get a quick-help / cheat-sheet to get an idea of what a
command does by typing "--help" after the command or "-h".  So now you
know the 3 commands above you can try;

cd --help

cd -h

ls --help

ls -h

Errr, i'd be cautious about the mkdir command in case it ends up
creating a folder called "--help" although that probably would not be
hugely bad anyway.

Regards from
Tom :)



On 21 January 2015 at 17:05, Spencer Graves <spencer.graves@prodsyse.com> wrote:



On Jan 21, 2015, at 7:54 AM, Stephan Bergmann <sbergman@redhat.com> wrote:

On 01/21/2015 10:09 AM, Alex Thurgood wrote:

Le 21/01/2015 10:02, Stephan Bergmann a écrit :

If you want to later use LO4352, when you start it up, it should only
use the LO4352 user configuration folder (assuming you have named them
the same). I don't thin you can have both running at the same time.


Where did you get that idea from?  The location of the user profile is


Probably because that is how it used to work.


Are you really sure that it ever worked that if you rename LibreOffice.app to Foo.app it will 
then locate its user profile under ~/Library/Application Data/Foo/ instead of 
~/Library/Application Data/LibreOffice/?  That would surprise me.



        See, “https://wiki.documentfoundation.org/Installing_in_parallel/OS_X”, referenced in 
an earlier email from Alex in this thread:  This describes “New Method” and “Old Method”.  
“Old Method” says, "Up to and including the 3.3.x series, the way to separate configurations 
on the Mac simply involved renaming your existing installation user configuration folder to 
the same name as the name of the LibreOffice application.”  That doesn’t mean it ever worked, 
but that seems to be what is described under “Old Method” ;-)


        I’m still having other problems parsing the “New Method”:  A first step says to “cd”, 
then run “mkdir -p libreoffice/builds"
in a terminal.


        Is this correct?  When I “cd” then “ls”, I get the following:


Applications    Documents       Library         Music           Public
Desktop         Downloads       Movies          Pictures


        I don’t see “libreoffice”.  Or is “libreoffice” in “mkdir -p libreoffice/builds” 
simply a shorthand for the local LibeOffice installation directory?  If that’s true, then how 
do I find the local LibreOffice installation directory?


        Thanks so much for all your help.  Sorry for being so dense.


        Best Wishes,
        Spencer


--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted





-- 
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.