I've been a happy user of cmd-key-happy for running emacs -nw on my Mac. After upgrading to 10.6.6 and rebooting, cmd-key-happy seems to run, but doesn't seem to function. There isn't much in the way of support or mailing lists for the tool itself, so I figured I'd at least post here to see if the problem is a general one or mine. Does anyone know if cmd-key-happy has a problem with 10.6.6?
Working fine for me on 10.6.6.
Is there anything in the logs that indicates a problem:
grep cmd-key-happy /var/log/*
No, it's not broken by 10.6, but it may have a conflict with Google Chrome. I had similar symptoms (had been running fine for a long time, then noticed it wasn't functioning even though the process was running, and cmd-key-happy-restart didn't fix it), but restarting Google Chrome fixed cmd-key-happy. Thanks to Drew R.'s comment on a different answer here for pointing that out.
Related
Not a programming problem per se, but rather a programming environment problem that I have been unable to find a solution to.
The problem relates to Adobe's Extendscript Toolkit (both 3.5 and 4), but so far I haven't been able to solve the problem, so here I am...
The error I get has appeared more or less over night. I didn't experience this problem yesterday, nor this morning. But exactly WHAT has happened is beyond me. I have removed preferences, I have uninstalled, reinstalled, created a new user, restored old preferences from Time Machine and I'm now pretty much lost for options.
Basically, nothing works in ESTK anymore. Just opening ESTK and entering alert('Hello') won't work. Neither will $.writeln(). Everything running from within ESTK seems to give the same error;
Cannot execute script in target engine 'main'
With details:
Cannot execute script in target engine 'main'!
(#1116) Can't start debug session.
Below is a screenshot taken from the new user I created to test, same problem.
The "funny" thing is that all the scripts (InDesign CS5, still hanging on to it for reasons) still work perfectly in the applications' script panels. So there is nothing wrong with the scripts (heck, they haven't changed one bit, and still refuses to run in ESTK).
As mentioned, I've tried installing the ESTK CC (version 4) as well, but the very same problem occurs there. Which leads me to think the problem lies somewhere else, but I do not know where, and why.
So, if anyone can shed any light on this issue, at all, I would be very happy. Debugging is basically the only thing ESTK is good for in my book, but now that even that functionality is gone, I don't know how to efficiently debug the scripts which is kind of hampering the workflow.
For reference, I'm running InDesign CS5 (from the old Creative Suite) on a 2008 Mac Pro with 10.11.6 (El Capitan) installed. Well aware that it's pretty out of date, but that is beside the point here.
In the above mentioned forum, Adobe has published a stable workaround!You just have to correct a setting inside the estk application:
Open the file(Mac): “/Applications/Adobe ExtendScript Toolkit CC/ExtendScript Toolkit.app/Contents/SharedSupport/Required/cdic/11BTBackend.jsx”
Search for the value: 604800000 (line reads bt.timeout = 604800000)
Replace that value with 604800 and save
Quit ExtendScript Toolkit and relaunch.
I can confirm that it works.
From the adobe Forum :
"we have found a first workaround: just change your date to any date before 20-nov-2018"
https://forums.adobe.com/message/10761440#10761440
Seems like a date issue :(
I just published a quick update about this on the Adobe Tech Blog.
For the time being, if you dismiss the dialog, you can still run your script via ESTK and step through code as usual.
Alternatively, if you really want to avoid the dialogs, and you don’t mind setting your clock back, you can sidestep the issue by setting your system clock back to November 19, 2018 or before. On most systems, changing the system time can have unintended side effects, so this isn’t recommended unless you’re really certain about it.
I recently decided to use emacs as I am starting to learn common lisp. But here is a problem that I feel that I must have done something wrong. After googling around for the past several hours, I still couldn't figure out why.
I am using windows 7. Installing the most recent emacs (24.5) with quicklisp, slime, sbcl etc are all fine. Then I started to install gtk+3 according to http://www.gtk.org/download/win32_tutorial.php. And it went well: I can run gtk3-demo. The problem is that after I put the path in the system environment, emacs was not responsive anymore: When I run runemacs.exe, it starts a window, then hang with a blank window (the menu appears). It can start fine after I remove the /dir-to-gtk-bin/ from the path.
I believe that there must be something wrong with my system setup, since emacs should work smoothly with gtk+ devleopment. Could you please give me a hint on where to start checking? Thanks very much for your help.
I believe this is similar to the thread: Canon SDK 2.11 on OSX
However the solution there did not work for me. I'm perplexed because I'm not sure how to figure out what has changed. I had some working software, did not work on it over the holiday and now when I open it up to work it fails. Not only my software but the demo app included with the SDK, which I have never changed and indeed used to work just fine.
I have tried with two different cameras (5DmII and 5DmIII) with the same result.
when I try and run the application, the camera is recognized but, as it attempts to open a session it receives a EXC_BAD_ACCESS signal. In each program it happens when a call is made to EdsOpenSession() with this message...
*** -[NSConcreteData release]: message sent to deallocated instance 0x8157af0
Interestingly, when I tried to use the EOS Utility that would crash also. So I updated and now that works great. I followed the suggestion in the above thread and copied the EDSDK.framework from the working bundle to my program and recompiled but I get the same results.
I'm trying to figure out how to contact Canon to get some information but they don't make it easy to get help so I'm appealing to the one group I know is responsive.
The only thing I can think is that sometime over the holiday I updated some critical library without knowing it.
Has anyone else run into and been able to solve this?
I'm running OS X 10.7.5, xcode 4.1, and EDSDK 2.11.3
Solved this. It did turn out to be the same solution as the mentioned link. However, what I was missing was that I needed to also copy the new EDSDK.framework into /Library/Frameworks not just have it in my source directory. This may be because I don't have everything setup correctly in XCode.
(I'd be very sorry to hear this is a stupid question, but I've done already some considerable googling and can't make a sense out of it.)
If I try to develop some software that uses RPC, I do not only find out that the RPC Portmapper is not yet running on my system, but also I can't find nor start it. While I could not find any trace about this, this is a clear sign for me that Apple decided to either withdraw support for the good only ONC RPC, or they switched to something else, that I cannot find tho.
https://www.cs.rutgers.edu/~pxk/rutgers/notes/rpc/step3.html (they don't seem to be all that outdated) still notes that is just has to be done with launchctl start com.apple.portmap but that one clearly does not exist for me anymore: launchctl start error: No such process
I can only confirm that portmap is not available with 10.8 (Mountain Lion) anymore while I could verify it is still existing on 10.6 (Snow Leopard). I don't know what's the state in 10.7 (Lion).
(It's amazing how at the beginning I thought of Stackoverflow as a very clever thing, yet, everytime I ask a question, it starts with apologies and me admitting my stupidity)
turns out my question was at least half stupid. I still can't find any documentation on this, but launchctl start rpcbind seems to float my boat. And that is the more BSD variant of doing it.
Let's hope this is at least helpful to somebody else in some documentation way. And thanks for being my teddy bear.
FWIW on the page you linked to, where it lists the command for OS X as launchctl start com.apple.portmap it also lists the command for BSD as /usr/sbin/rpcbind, which is there in Mtn Lion and would probably explain why launchctl start rpcbind works.
How can I find what's hanging all new installations on a Windows box?
While testing an installation script on Windows (XP Pro, if it matters) I've run into a situation wherein any and all attempts to install anything on the system hang waiting on who knows what. When the system is restarted, all queued up attempts at installation then go through their exit paths with pop-ups that report the installation is being aborted due to system shutdown having been requested. Of course, reboots do not cure the problem. The system otherwise runs fine.
So... How can I determine what part of the OS I've wedged? (Something in the registry, I suppose, but I'm a real greenhorn when it comes to Windows.) Most likely, something from a preceding install attempt went awry and is now blocking even though I saw no errors reported. Once I figure this out, I want to put in a check for this sort of thing, possibly at both ends of my install scripts, if that seems reasonable.
Thanks for your input.
UPDATE:
Unfortunately for me, rebuilding from scratch to get to the point the system's in now is about 9 hours. I'd like to unwedge it from where it is now rather than reload (again). Procmon seems great but I haven't got SP2 installed, only SP1! -frown- So, other ideas are welcome.
I assume you've tried logging the install to see where things go wrong?
Try rolling back to before things went wrong using "System Restore", if that doesn't solve it and the MSI log files show nothing useful then I'd take the plunge and reload before wasting any more time on it.
That said, if you're developing installers then taking an image of this PC in it's crappy state could be a worthwhile exercise. Some point in the future when you have more time to debug you can try and figure out what the problem is.
P.S. I'm assuming you're asking this question from the point of view of someone developing an installer and not as a tech-support question... otherwise this question should probably be closed as not-programming-related ;)
Try using Procmon to figure out where the installer is having problems, if you set a filter it will report all file and registry activity for that process.