Lots of random commands simply don't work. I don't have any extensions enabled or OS level keybinding apps like karabiner or anything. I checked keyboard settings on mac and disabled anything with SHIFT+CMD+L and I still can't get "Select All Occurrences of Find Match" working in the interactive playground.
Nevermind, had to restart my computer after disabling the hotkey from keyboard settings. All works well now.
Related
I'm on Windows 10 and recently updated to Spyder 5.3.3 standalone version and the keyboard shortcut to switch to the editor pane (default Ctrl+E) will not work no matter what I try, it simply has no effect.
I've tried reinstalling Spyder, resetting everything back to defaults multiple times, changing to different keyboard shortcuts than Ctrl+E, trying to switch to the editor pane while having various other panes selected (different contexts), but nothing helps. I can switch to all other panes (like the console with Ctrl+I, etc) just fine and so far all of the other key shortcuts I'm used to work but this one is the most impactful and I can't get it to work. I opened my previous version of Spyder 4.X and the Ctrl+E works fine from any context as expected.
Any ideas on what the issue could be?
Same issue here, and I think the issue started with the upgrade from 5.3.2 to 5.3.3 only. Before that it still worked.
The issue appears to be version-specific.
Have upgraded from 5.3.3 to 5.4.0, and the shortcut is working again.
We run some localization checks by taking screenshots in CircleCI. We compare new screenshots with images taken from what we expect - any differences are flagged.
The problem with CircleCI is MacOS Mojave changes the background on the time of day, so some of the images which contain part of the background are constantly flagged as different.
I have tried running all the commands I could find to remove or change the background:
via osascripts - it times out as I believe Mojave has the permission
popup. I haven't found a way to bypass it.
via sqllite - these commands don't seem to work with Mojave.
Ultimately this might not be exactly what CCI is built for, but it is necessary for us to run these tests in CI. Has anyone been able to disable desktop pictures? (Using xcode 11.1 image, which is MacOs Mojave)
For the record, I was able to get around this with a bit of a hack. CCI support were not helpful and unable to provide a solution, so I found opening safari was the only app I could find that would open mostly full screen. This then became the background.
Steps
Remove the dock, so any corner gaps still don't show the background
Open safari.app
There is still a thin sliver just above safari, but some python to put a block of solid colour there works for me.
Comparisons are then equal.
Code to do so:
defaults write com.apple.dock autohide -bool true && killall Dock
defaults write com.apple.dock autohide-delay -float 1000 && killall Dock
defaults write com.apple.dock no-bouncing -bool TRUE && killall Dock
defaults write com.apple.dock tilesize -float 1; killall Dock
open -a safari http://invalid.website # Not a real website, but shows an error. Otherwise create your own html page to open
I have a question about Xcode (Swift). Sometimes when I write an if statement. Something like this:
if(a == 2){
//do Sth
} else {
//do Sth
}
Xcode throws me an error: "Invalid character in source file"
I know it is no big deal and fixed by clicking on "Fix-it" but I want
to know what is the problem. That doesn't make sense to me...
My Xcode is on 7.2 and I am using Swift - I don't know if this is just a Swift problem.
For me it's the ESC key - it's completely reproducible! If I go to search and hit ESC in the search window I also find the occurrences marked - and can replace those with nothing. But it's not shown even with "Show invisible"!
final solution: Bind ESC keybinding to "Cancel". It's that simple.
I was having this problem. The way I solved it is by 1) copying whatever you have into Sublime Text or another code editor and having a look (you may need to enable viewing hidden characters). Mine had a code in there DC2 which is some sort of ASCII control character. For me it was caused by the fact that I had put the playground into manual execute and bound a keyboard shortcut to it that seemed to be entering that control character every time I executed it using the shortcut. I just changed the shortcut and removed the ASCII characters as I was able to see them in Sublime Text. (The link in the comments to the OP concerning left to right mode made no sense and didn't work for me.)
I encountered this problem when I was using a non-Apple keyboard with my iMac. Probably your case too. They add unnecessary control characters! One way to fix it in Xcode ischoose from the menu Editor>Show Invisibles and see if there are any unwanted characters where the error is being thrown and remove them.
Editor->Show Invisibles did not show the character that was causing a problem for me. No-break-space (u00a0) will be shown as a space with no "dot" indicator. However, that's really hard to see and I completely missed it the first time. Zoom helps.
One way I found to detect invalid characters is to use Visual Studio Code and enable the settings:
"editor.renderControlCharacters": true
"editor.renderWhitespace": "all"
This has the same visibility issue with no-break-space as Xcode, however it does show other special characters.
To make it more obvious and possibly detect more invalid characters, install the extension "ascii-unicode-escape" and follow the instructions.
I don't understand why Xcode allows these invalid characters, inserts them into your source files for no reason, and doesn't even give an option to detect them! I'm trying to write code, not secrets in invisible ink, damnit!! I guess it's less of an issue for compiled code, which will show an error, but not so convenient with shader code.
I'm having the same issue. I found a solution after extensive testing. Hopefully it could save others extensive hours of researching into this terrible Xcode experience.
The problem is I have a FILCO Minila keyboard, which has the 'App' key right next to 'left arrow'. I would accidentally hit 'App' when typing really fast, and it enters a 'DEL'(Data Link Escape, Unicode 0010) invisible character. It could only be seen when copy-pasted to Sublime. It's not even visible under Xcode's own 'Editor -> Show Invisibles'(Talking about good user experience...)
Magically this doesn't happen to Sublime or VSCode, only to Xcode. So no excuses for Xcode I guess?
The fix is to download Karabiner, an advanced keymapper for macOS, and invalidate the 'App' key or map it to something else. Karabiner would also invalidate your keymapping in the system default keyboard config. So you would have to remap stuff like 'cmd', 'alt' if you've customized them. If so, be sure to map both left & right modifier keys in Karabiner, because according to Karabiner's key event viewer, the system default keymap would map left_alt & left_cmd to right_cmd and right_alt... Just annoying as hell...
It took me 2 months to realize this problem and 2 hours to actually find out it's the 'app' key that's the culprit and fix it.
I'm using XCode 10.1.
With Xcode: Xcode does not help even after showing invisibles.
Then you can copy the code to Sublime Text => you will see these invisible characters which are the <0x0f>. Click the image to see in details.
With Sublime Text 3, it works!
=> Then you know where to remove the redundancies. Hope that helps!
Are you using the option ⌥ key for any keyboard shortcuts? This was my issue. It seems combining the option key with other keys can insert hidden characters.
For me, this happened when I used the ⌃+⌥+p shortcut in Xcode to resume the SwiftUI preview canvas. It added a 0x10 character. I discovered this, as other posters have recommended, by pasting the code from Xcode into Sublime Text.
(NB: I should have been using ⌘+⌥+p).
I'm trying to profile app startup after moving from static libraries to frameworks. We have 30 or so frameworks (fyi: cocoapods) so I want to check that it's not affecting performance. Anecdotal testing in the team says that it isn't, but I would like some numbers as well!
I've added the environment variables DYLD_PRINT_STATISTICS and DYLD_PRINT_LIBRARIES to see what the linker is doing, but all the output I get is from the DYLD_PRINT_LIBRARIES variable. I can see that the frameworks are loading correctly, but get no statistics from them.
I've tried restarting the device to make sure that the frameworks aren't in memory already but that hasn't helped.
Any other suggestions as to why I'm not getting any output from DYLD_PRINT_STATISTICS?
Looks like you can do it on device if you enable both environment variables in your scheme:
DYLD_PRINT_APIS = YES
DYLD_PRINT_STATISTICS = YES
Reference:
https://github.com/artsy/eigen/issues/586#issuecomment-118606377
While other flags, like DYLD_PRINT_BINDINGS work fine on the device, DYLD_PRINT_STATISTICS only seems to work on the simulator (for me, iOS 9.0).
In this (possibly unrelated) version of dyld.cpp, from osx 10.10.5 there doesn't seem to be any obvious exclusion of DYLD_PRINT_STATISTICS for devices, although there are conditionally compiled TARGET_IPHONE_SIMULATORs sprinkled throughout the code.
I guess it's a bug.
So this is the problem I have with my Outlaw:
My Corona SDK is in that adress:
C:\Program Files (x86)\Corona Labs\Corona SDK\Corona Simulator.exe
I'm going to Preferences --> Corona SDK simulator --> puts this adress.
once I'm trying to lunch my program, Outlaw says this:
"Windows cannot find 'C:\Program\". make sure you typed the name correctly, and then try again"
I've figures it doesn't recognise spaces (lamest thing ever). what the hell should I do? I don't want to mobilize my entire computer to non-spaced folders.
I've stumbled to the same problem trying to use Outlaw on Windows. I've tried adding quotes, tried options with PATH, but ultimately I've to just gave up.
Apparently author never tested his app under Windows :)
As a side note I can recommend ZeroBrane Studio as an excellent alternative. It's free and works great with Corona.
You need to use the Browse button in Prefs to point to the simulator exe; don't type in the pathname. I should probably make that field read-only so you have to use the Browse button.