Re: Remotely Edit Perl: Syntax check barfs on 'use' other Remote file
Thanks for all the ideas. In a little more detail, I manage a fairly low-traffic site. I know I could copy everything to a sandbox directory and test in there, but then I've got to also direct my client apps to use the sandbox. Time-consuming. Sometimes when I need to make a relatively small change I'd like to download the live script, edit a little, and then do a syntax check to insure that -- oh, maybe I've got a 80% chance of it working before uploading. Just enough to catch the really stupid stuff. Anyhow, I understand the limitations and workarounds now. Just now, I was able to finally get a clean syntax check after downloading a few files and also spending about 10 minutes with CPAN. It's not an ideal world, but I get by. Thanks again, Jerry -- You received this message because you are subscribed to the BBEdit Talk discussion group on Google Groups. To post to this group, send email to bbedit@googlegroups.com To unsubscribe from this group, send email to bbedit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/bbedit?hl=en If you have a feature request or would like to report a problem, please email supp...@barebones.com rather than posting to the group.
Re: Remotely Edit Perl: Syntax check barfs on 'use' other Remote file
Anyhow, I understand the limitations and workarounds now. Just now, I was able to finally get a clean syntax check after downloading a few files and also spending about 10 minutes with CPAN. It's not an ideal world, but I get by. Do you have ssh access to the server? If you do you can try MacFuse / sshfs / Macfusion and treat the remote disk as a local volume that way. I do this from time to time, I even use projects that way. The downside is BBEdit can take a long time to scan the files on opening a project, but it has its uses. -- You received this message because you are subscribed to the BBEdit Talk discussion group on Google Groups. To post to this group, send email to bbedit@googlegroups.com To unsubscribe from this group, send email to bbedit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/bbedit?hl=en If you have a feature request or would like to report a problem, please email supp...@barebones.com rather than posting to the group.
Re: Remotely Edit Perl: Syntax check barfs on 'use' other Remote file
At 6:55 PM -0700 on 05/08/2010, Jerry Krinock wrote about Re: Remotely Edit Perl: Syntax check barfs on 'use' other R: Thanks for all the ideas. In a little more detail, I manage a fairly low-traffic site. I know I could copy everything to a sandbox directory and test in there, but then I've got to also direct my client apps to use the sandbox. Time-consuming. Sometimes when I need to make a relatively small change I'd like to download the live script, edit a little, and then do a syntax check to insure that -- oh, maybe I've got a 80% chance of it working before uploading. Just enough to catch the really stupid stuff. Anyhow, I understand the limitations and workarounds now. Just now, I was able to finally get a clean syntax check after downloading a few files and also spending about 10 minutes with CPAN. It's not an ideal world, but I get by. Thanks again, Jerry What I do when I have a situation of this type is to create a duplicate copy of the file and use that to edit/view/etc. In your case, since you want to update a script, I would suggest that you duplicate a file that uses the script and the script itself. Rename the duplicate script and page to new names and update the duplicate page to use the duplicate script under its new name. Update the script and then upload both files. Test and edit until everything works to your satisfaction. NOW upload the files under the original names and you are done without affecting the original files during the testing. -- Robert A. Rosenberg RAR Programming Systems Ltd. -- You received this message because you are subscribed to the BBEdit Talk discussion group on Google Groups. To post to this group, send email to bbedit@googlegroups.com To unsubscribe from this group, send email to bbedit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/bbedit?hl=en If you have a feature request or would like to report a problem, please email supp...@barebones.com rather than posting to the group.
Remotely Edit Perl: Syntax check barfs on 'use' other Remote file
My favorite BBEdit feature is the ability to access documents on FTP servers in the File menu. But syntax checking is broken for perl scripts if they have 'use' directives other scripts on the server. It quits with Can't find in INC I believe the reason is that BBEdit makes a local copy of the file in a temporary directory. If I start to open the 'used' files from the server also, then the error changes to Can't find a different file, and often I end up needing a perl file which I don't have access to because I use a shared web host. Opening 25 files to do a syntax check wouldn't be any fun anyhow. Is there any way to tell BBEdit's perl syntax checker to ignore 'use' directives or something? I tried the #bbpragma but that seems to be only for HTML. Thank you, Jerry Krinock -- You received this message because you are subscribed to the BBEdit Talk discussion group on Google Groups. To post to this group, send email to bbedit@googlegroups.com To unsubscribe from this group, send email to bbedit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/bbedit?hl=en If you have a feature request or would like to report a problem, please email supp...@barebones.com rather than posting to the group.
Re: Remotely Edit Perl: Syntax check barfs on 'use' other Remote file
On Sun, May 02, 2010 at 06:12:08PM -0700, Jerry Krinock wrote: My favorite BBEdit feature is the ability to access documents on FTP servers in the File menu. But syntax checking is broken for perl scripts if they have 'use' directives other scripts on the server. It quits with Can't find in INC I believe the reason is that BBEdit makes a local copy of the file in a temporary directory. If I start to open the 'used' files from the server also, then the error changes to Can't find a different file, and often I end up needing a perl file which I don't have access to because I use a shared web host. Opening 25 files to do a syntax check wouldn't be any fun anyhow. Is there any way to tell BBEdit's perl syntax checker to ignore 'use' directives or something? I tried the #bbpragma but that seems to be only for HTML. I would presume that BBEdit's Perl syntax checker uses the actual perl executable to check whether your script compiles. perl can't check whether your script compiles without executing the 'use' statements. Ronald -- You received this message because you are subscribed to the BBEdit Talk discussion group on Google Groups. To post to this group, send email to bbedit@googlegroups.com To unsubscribe from this group, send email to bbedit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/bbedit?hl=en If you have a feature request or would like to report a problem, please email supp...@barebones.com rather than posting to the group.
Re: Remotely Edit Perl: Syntax check barfs on 'use' other Remote file
Jerry, I suggest that you use CPAN and install the modules you need on your local machine. This allows you to not only do syntax checking, but functionality checking locally as well. Matt On May 2, 2010, at 9:12 PM, Jerry Krinock wrote: My favorite BBEdit feature is the ability to access documents on FTP servers in the File menu. But syntax checking is broken for perl scripts if they have 'use' directives other scripts on the server. It quits with Can't find in INC I believe the reason is that BBEdit makes a local copy of the file in a temporary directory. If I start to open the 'used' files from the server also, then the error changes to Can't find a different file, and often I end up needing a perl file which I don't have access to because I use a shared web host. Opening 25 files to do a syntax check wouldn't be any fun anyhow. Is there any way to tell BBEdit's perl syntax checker to ignore 'use' directives or something? I tried the #bbpragma but that seems to be only for HTML. Thank you, Jerry Krinock -- You received this message because you are subscribed to the BBEdit Talk discussion group on Google Groups. To post to this group, send email to bbedit@googlegroups.com To unsubscribe from this group, send email to bbedit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/bbedit?hl=en If you have a feature request or would like to report a problem, please email supp...@barebones.com rather than posting to the group.
Re: Remotely Edit Perl: Syntax check barfs on 'use' other Remote file
Good afternoon, On 2/05/10 at 6:12 PM -0700, Jerry Krinock je...@ieee.org wrote: My favorite BBEdit feature is the ability to access documents on FTP servers in the File menu. But syntax checking is broken for perl scripts if they have 'use' directives other scripts on the server. It quits with Can't find in INC Your script is useing modules you don't have installed locally. You either need to install the modules locally (you can use CPAN for that) or do a syntax check on the server. I believe the reason is that BBEdit makes a local copy of the file in a temporary directory. If I start to open the 'used' files from the server also, then the error changes to Can't find a different file, and often I end up needing a perl file which I don't have access to because I use a shared web host. Opening 25 files to do a syntax check wouldn't be any fun anyhow. Opening all the used files from the server won't work and is a sure path to madness. I suggest just doing the syntax check on the server. You won't get BBEdit's friendly error browser, but at least you'll know whether the script compiles cleanly. And that's what you really want to know anyway. Just because the script compiles cleanly locally doesn't mean it will compile the same on the server. To check scripts on the server (assumes you have ssh or similar access) $ perl -c path/to/script.pl And if you've got access via ssh, you could create a local shortcut using something like: $ ssh u...@host perl -c path/to/script.pl And I think that output could be passed to BBEdit to create an error browser, but I don't recall details for doing that. Is there any way to tell BBEdit's perl syntax checker to ignore 'use' directives or something? I tried the #bbpragma but that seems to be only for HTML. Nope, you can't ignore them. If you don't use the the needed modules the script won't be able to compile. Note, it's not BBEdit that's doing the syntax check; it's perl doing the heavy lifting. BBEdit is just automating that process for you and giving you a friendly 'syntax ok' dialog or an error browser. Charlie -- Ꮚ Charlie Garrison ♊ garri...@zeta.org.au O ascii ribbon campaign - stop html mail - www.asciiribbon.org 〠 http://www.ietf.org/rfc/rfc1855.txt -- You received this message because you are subscribed to the BBEdit Talk discussion group on Google Groups. To post to this group, send email to bbedit@googlegroups.com To unsubscribe from this group, send email to bbedit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/bbedit?hl=en If you have a feature request or would like to report a problem, please email supp...@barebones.com rather than posting to the group.
