On 10/09/2014 10:58 AM, Dan Lewis wrote:
Actually there seems to be an important hint in the Paths section of
Tools > Options > LibreOffice > Paths.
You could see this also by looking at the sub folders within the "user"
folder. This folder's sub folders divide the configuation into
individual parts: autocorr, autotext, backup, etc. Specifically, one
folder is named uno_packages. So, would it make sense to have a Python
folder as a sub folder of "user" if you are using python? After all
python properties don't seem to fit in any of the other sub folders. The
seemingly only question would be whether to capitalize this sub folder
or not. This is just an educated guess.
Dan
I knew where it went under vers 3.xxx. I thought I set it up under 4.xx
the same way and wondered why it did not work. The problem was I
mistakenly named it Python not python. Once I fixed that it worked.
Regards, Jim
On 10/09/2014 10:23 AM, Jim Byrnes wrote:
I don't it ever was an option. I have 3.5xx on my desktop and it is
not there either. I think it strictly an internal setting.
Regards, Jim
On 8 October 2014 15:41, Jim Byrnes <jf_byrnes@comcast.net> wrote:
On 10/08/2014 08:38 AM, Jim Byrnes wrote:
On 10/08/2014 06:01 AM, Tom Davies wrote:
Hi :)
Something like
Tools - Options - Paths
is probably too obvious but it's often the obvious things that get
missed
so it's worth getting that out of the way before looking for
something
more
complicated.
Regards from
Tom :)
That's what I thought also, but looking on the working version it
is not
there. Must get it some place internally.
Regards, Jim
Turns out to be an error on my part. Despite what I wrote about the
directory structure, I actually had the folder named Python not python.
Now it works.
Regards, Jim
On 8 October 2014 02:44, Jim Byrnes <jf_byrnes@comcast.net> wrote:
I upgraded my notebook to Ubuntu 14.04 as a test bed before
upgrading my
desktop. I copied over some spreadsheets from my desktop LO 3.xxx
system.
Python did not appear in the organize macros menu item. Some
goolgling told
me I had to install a python script handler. I did that and Python
showed
up in the organize macros menu item, but the individual macros did
not show
up under the MyMacros.
On my desktop LO 3.xxx version I have my Python macros stored in:
/.config/libreoffice/3/user/Scripts/python and they show up in
MyMacros.
So on LO 4.2.6.3 I put them in:
/.config/libreoffice/4/user/Scripts/python, but they don't show
up in
MyMacros.
I must have a path problem but don't know how to correct it.
Does anyone have python macros working in LO 4.2?
Thanks, Jim
--
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
--
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.