There is some evidence in the Intellij codebase they support ALT(/Meta)+CTL - (mnemonic) in Mac.
E.g: in platform/platform-api/src/com/intellij/openapi/MnemonicWrapper.java
if (SystemInfo.isMac && Registry.is("ide.mac.alt.mnemonic.without.ctrl")) {
And the corresponding resource value in ./platform/util/resources/misc/registry.properties is set to true :
ide.mac.alt.mnemonic.without.ctrl=true
However pressing those two modifier keys together with .. say .. F (for File in the main menu) does not work for me on Sierra with the latest 2017.1 intellij.
Is this supposed to work? Is there any other way to get mnemonics working on Mac.
Note: please do not comment/respond "mnemonics are not encouraged/supported on mac". I am more than well aware of this terrible shortcoming on OS/X. However in previous versions of Intellij it has been possible to use mnemonics on Mac: and it would be a big boost to have them working again.
Update A YouTrack issue was requested by the Intellij Jetbrains support lead. It is here https://youtrack.jetbrains.com/issue/IDEA-175624
CTRL-ALT-(Mnemonic) DOES work.
The JetBrains lead Serge Baranov also mentioned that ALT-(Mnenomic) is supposed to work. It did not / does not for any of my laptops on 2017.X.
The Jetbrains support team led by Serge Baranov worked diligently on this - but were unable to reproduce. I expressed surprise since a half dozen installations on my side - all do not work. Apparently for their testing team it does work. One of my Mac's was factory new in June 2017 with Sierra and I installed IJ Ultimate 2017.1 without any changes from defaults. It did not work.
It is unclear what conditions were required for the Alt-Mnemonics to work on 2017.X.
* Another update* . Jetbrains has provided a fix for this: see last answer.
Make sure mnemonics are not disabled in IntelliJ IDEA settings:
By default mnemonics should work with Ctrl+Alt and Alt on Mac.
If you prefer only Ctrl+Alt, add -Dide.mac.alt.mnemonic.without.ctrl=false in Help | Edit Custom VM Options (Processes Alt-based shortcuts for mnemonics in addition to Ctrl+Alt-based shortcuts. Affect MacOS only.)
There is also a bug in IntelliJ IDEA 2017.1.x versions which causes mnemonics to work via Alt in dialogs, but not in the menu. Adding -Dide.mnemonic.helper.old=true in Help | Edit Custom VM Options will workaround this issue. The fix will be available in 2017.2.x.
Thanks to Serge Baranov of JetBrains : we now have a solution
Add the following to Custom VM Options
-Dide.mnemonic.helper.old=true
In addition a fix will be added to 2017.2
Related
The results of the check error in my code using VisualStudio 2022 plugin Resharper version 2021.3.4 and Resharper in CLT 2021.3.4 are completely different. Used the same file .DotSettings
There are no bugs in the IDE VisualStudio 2022, but using the CLT there are over 2000.
I checked the results in TeamCity and they match with CLT.
Who have encountered, tell me how to solve the problem...
I had a very similar issue almost a year ago and contacted the JetBrains support. We had a very long back and forth, from which I took the following key aspects:
There are some existing issues, for example this one.
Make sure that no other settings layer (e.g. machine-wide config) comes into your way and overrides certain settings.
Enable solution-wide analyses (SWA), as it comes closer to what R# CLT does.
The whole picture becomes even more fuzzy when using Rider. For example, I had to enable File | Settings | Editor | Inspection Settings | " Enable computationally expensive inspections"
There are different results shown, depending on the used tool window.
Rider
SWA
Code → Inspect Code
VS
SWA
ReSharper → Inspect → Code Issues in Solution
So my key take-away was: it is super-hard to reach a 100% sync of VS and R# CLT, which gets even more complex when Rider comes into play. The almost inexhaustible number of options to configure R# makes it impossible to answer your general question.
What I can recommend: try to reduce the problem to a very small solution and get in contact to JetBrains.
Finally this was corrected in the new version of R# 2022.1.0 at JetBrains (using the Blazor component, files were created with the extension .razor, which R# checks did not take into VS)
That solved my problem
I have been having this problem for a week, I can not type "#" symbol on my editor. I had research on Google, but I could not find anyone who had this problem before. Did somebody have the same or a similar problem?
I can type "#" character in other parts of Intellij such as Project Structure tool etc.
I checked whether my keyboard configuration is changed. However, all other symbols work properly.
Here are the details of my Intellij version:
IntelliJ IDEA 2017.1.4
Build #IU-171.4694.23, built on June 6, 2017
JRE: 1.8.0_112-release-736-b21 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Mac OS X 10.12.5
It would be best to hear some advices.
Thanks.
Plugins can take certain hotkeys. This can be checked by trying to assign the same key to any action in IntelliJ IDEA Keymap settings, it will warn you about the conflicting action with the same hotkey. So you either remap that action to a different hotkey or disable the plug-in if you don't need it.
In my case Spotbugs plugin was using # sign as a shortcut. When I tried to assign option+Q(# sign in my keyboard) It warned me as #CrazyCoder said.
If you are using Mac go to Preferences -> Keymap and you will find out the plugin which is using this shortcut.
After recently updating my project to meteor 1.2 and including the new ecmascript package (to use ES2015 features), I realized that my server debug breakpoints will never run, no matter what I do.
After reading about different ES6 posts on meteor forums and jetbrains , I tried setting up file watchers to create sourcemaps, but:
meteor complains about the generated files(so you have to move them to special folders in order to keep going)
It still doesn't work :(
Setting up spy-js also didn't work (never tried before so maybe I did it wrong)
I could reproduce the problem with the basic TODOs application and debugging with default options.
It is fixed for now in EAP 11 builds.
Known issue, please follow WEB-18074 for updates. Unfortunately I can't offer any workarounds:(
When I tried to debug a small piece of code using AVR studio 4 I got this error:
Build failed... No build tools defined.
Could someone give me some advices?
In AVRStudio 4.19, Atmel made some serious changes from previous versions. Specially while using the toolchains. After you install WinAVR (the latest version, 2010...), open a new project in Avrstudio and from now on, everytime you make a new project you have to do this steps:
Go to "Project" tab
Go to "Configurations Options"
Then all the way down to "Custom Options".
Once you there, you'll see a checkbox called "Use AVR ToolChain", UNCHECK that option.(For some reason AVRStudio 4.19 does not link automatically the toolchain from WINAVR, so you have to do it manually).
After this, it enables the two options below.
For avr-gcc, you browse to the next direction: C:\ProgramFiles\WINAVR20100110\bin\avr-gcc.exe
For make, you browse to the next direction: C:\ProgramFiles\WINAVR20100110\utils\bin\make.exe
This directions depends on where did you installed WINAVR. I remember that the default location is "C:\" but when I installed WINAVR, I changed it to "ProgramFiles"
Click "OK".
After doing this steps, you should be able to compile and run your code.
Cheers, and hope it helped!
PD: I had that same problem, months ago. Check out, www.avrfreaks.net, very good webpage for newbies and pros at programming AVRs.
You need to install WinAVR or Atmel's "AVR Toolchain." If you already have one of these and still get this message, you may need to tweak the System Variables.
Connect the programmer first and then run avr studio.
I have that error when I try to open a project made in another version of AVR Studio (or upgraded to another version by someone else).
I've tried to use MonoDevelop 2.4 and 2.6 with Ubuntu 11.04, but neither of them seems to actually provide any way of running the project. (As the picture shows, the Run, Step, and Debug items are disabled -- both on the toolbar and inside the menus.)
This is true for all project types I've seen so far -- C#, Python, etc...
But mono-debugger is installed. Is there some post-setup task that I need to do manually, for this to work?
Looking over https://github.com/mono/monodevelop/blob/master/main/src/core/MonoDevelop.Ide/MonoDevelop.Ide.Commands/ProjectCommands.cs
Perhaps you haven't selected a 'Project'? Open up the Solution pad and click on the Test1 project (not the solution at the root of the tree, but the project just below it).
I'm just guessing here since I don't have Ubuntu and can't actually test anything.
Edit: actually, it looks like clicking on the Solution would work as well.
From looking at the code, another possibility is that you don't have a build target? Not sure how that would happen, but unless you only opened Main.cs and not actually Test1.sln, I don't know what to suggest.
When you opened the project, which file did you open? Test1.sln? Test1.csproj? Or Main.cs?
Try looking for mono-mdb and more packages in synaptic, this may fix this issue.
Don't remember exact names, Linux box at home...
Did you really open the project? It looks like you just opened Main.cs. It won't work that way.
Make sure you installed the compilers (mcs etc)