Date/time: 2018-05-10 06:25:07 +0000
Sublime Text version: 3170
Platform: osx
CPU architecture: x64
OS info: 'Darwin-16.7.0-x86_64-i386-64bit'
This has been happening for a while (last 8 months or so) started with ST 2, so I upgrade to ST 3. No dice. I enabled logging level 2 without much luck.
If I restart sometimes it magically starts working. However, once it begins to crash ST3, I can't get it to stop until I reboot one or more times. It almost seems like its running the command without passing the filename as an argument. Any help in testing this theory would be welcome.
I tried changing my perltidy path to /bin/echo just to see what command it was running. Below is that output. I have to use an older version of perltidy unfortunately.
PerlTidy: Checking for perltidy (user): "/bin/echo"
PerlTidy: Using perltidy: "/bin/echo"
PerlTidy: Checking for perltidyrc: "/Users/jaime/Projects/Tally/trunk/.perltidyrc"
PerlTidy: File not found: "/Users/jaime/Projects/Tally/trunk/.perltidyrc"
PerlTidy: Checking for perltidyrc: "/Users/jaime/Projects/Tally/trunk/perltidyrc"
PerlTidy: File not found: "/Users/jaime/Projects/Tally/trunk/perltidyrc"
PerlTidy: No perltidyrc found in project.
PerlTidy: Running command: "/bin/echo" "-b" "-ole=unix"
PerlTidy: Command exited with code: 0
Running perltidy manually works fine btw.
my perltidy path: /Users/jaime/perl5/perlbrew/perls/perl-5.16.0/bin/Perltidy
so running /Users/jaime/perl5/perlbrew/perls/perl-5.16.0/bin/Perltidy -b /path/to/my/perl.pl runs fine. Any help is greatly appreciated.
In case anyone is having this issue.. modifying PerlTidy adding
use lib qw(/Users/<user-name>/perl5/lib/perl5);
just before use Perl::Tidy; solved it for me.
Date/time: 2018-05-10 06:25:07 +0000 Sublime Text version: 3170 Platform: osx CPU architecture: x64 OS info: 'Darwin-16.7.0-x86_64-i386-64bit'
This has been happening for a while (last 8 months or so) started with ST 2, so I upgrade to ST 3. No dice. I enabled logging level 2 without much luck.
If I restart sometimes it magically starts working. However, once it begins to crash ST3, I can't get it to stop until I reboot one or more times. It almost seems like its running the command without passing the filename as an argument. Any help in testing this theory would be welcome.
I tried changing my perltidy path to /bin/echo just to see what command it was running. Below is that output. I have to use an older version of perltidy unfortunately.
PerlTidy: Checking for perltidy (user): "/bin/echo" PerlTidy: Using perltidy: "/bin/echo" PerlTidy: Checking for perltidyrc: "/Users/jaime/Projects/Tally/trunk/.perltidyrc" PerlTidy: File not found: "/Users/jaime/Projects/Tally/trunk/.perltidyrc" PerlTidy: Checking for perltidyrc: "/Users/jaime/Projects/Tally/trunk/perltidyrc" PerlTidy: File not found: "/Users/jaime/Projects/Tally/trunk/perltidyrc" PerlTidy: No perltidyrc found in project. PerlTidy: Running command: "/bin/echo" "-b" "-ole=unix" PerlTidy: Command exited with code: 0
Running perltidy manually works fine btw. my perltidy path: /Users/jaime/perl5/perlbrew/perls/perl-5.16.0/bin/Perltidy so running
/Users/jaime/perl5/perlbrew/perls/perl-5.16.0/bin/Perltidy -b /path/to/my/perl.pl
runs fine. Any help is greatly appreciated.