NOTE: I just started to use awesome not very long ago, and don't really know the lua programming language.
I cloned HikariKnight's awesome theme and started to customize the hotkeys. I have a logitech keyboard that has some launcher keys that will open you default apps (on windows that is). I wanted to make them open the default apps here, so I edited the config. Now the help menu has the name of some of the keys repeated over and over for no apparent reason.
If anyone could help me fix this that would be awesome.
Possible Solution(?)
I might be able to use the new function to use the hide_without_description option. This wouldn't be ideal though as it would just remove the hotkey from the help menu.
I found the documentation for it here, but don't know how to use the new function.
https://www.reddit.com/r/awesomewm/comments/mgqq95/messed_up_help_menu/gszd5u0/?utm_source=reddit&utm_medium=web2x&context=3
To quote PlatformKnuckles:
I think I see the problem. Check the line in the keybindings file:
for i = 1, 9 do
You're starting the keybindings in a loop multiple times.
(I didn't look at your rc.lua at all. I just assume the answer above is correct.)
Related
I've been trying out APL. I'm running Windows 10 and I've installed Dyalog 18.0, and the APL Language and APL Backtick Symbols extentions for VS Code.
But even though I'm not running any of these programs, sometimes suddenly my keyboard is hyjacked! All my ctrl commands are replaced by APL symbols.
E.g. ctrl-Z (undo) becomes ⊂ and ctrl-A (select all) becomes ⍺. I have no idea why and how to disable this again. This makes it very hard to do my work!!!
I've been googling for this, but haven't found an answer so far. I've looked at the Windows keyboard settings, but it looks normal. The locale settings are also correct.
I'm now just de-installing everything, but that way I need to reinstall every time I want to try out APL.
Can somebody tell me what is happening and how to fix it? (And tell me who to complain to that this is a very hostile feature)
I am sorry that our Unicode IME is causing you confusion.
I do like using it, but there are some Windows settings which I set to make things easier.
Start button->Settings
In the "Find a setting" edit field, type Advanced keyboard settings
Click on the icon with that text on it
Under Switching input methods:
Tick the “Let me set a different input method for each app window”
Tick the "Use the desktop language bar when it's available". This option will show the orange D icon when our Dyalog Unicode IME is active.
On this same dialog, there is a Input language hot keys.
I find it convenient to select a hot key combination to activate our Unicode IME, and another one to go back to the default Windows keyboard layout.
Close this dialog with the X button in the top right.
If you have further problems or questions, you can always ask us at support#dyalog.com
By the way, we put links to advice pages about keyboards on our website under Resources->Fonts and Keyboards.
Regards,
Vince
When installing the standard Dyalog IME, there is a new keyboard input method on Windows. Have you checked WinKey+Space? This should cycle through available keyboard layouts and you should find your previous/default layout available there.
I personally agree that this is not a good way to handle keyboarding and causes many issues for newcomers to APL. Dyalog is aware and are looking into alternatives that can be comfortable for both new and existing users.
You can uninstall the standard IME without uninstalling the entire interpreter by running the Dyalog uninstaller (search "uninstall Dyalog" in your start menu) and selecting just the IME.
For now, I recommend the APL Wiki article on Typing Glyphs for some ideas for alternatives to the standard IME: https://aplwiki.com/wiki/Typing_glyphs#Windows
I personally use the abrudz keyboard with Alt Gr as the switching key.
I just wanted to add that your complaint has reached the people who need to be complained to. This is a difficult problem space, between changing technologies, multiple platforms, new or casual users of APL and the folks who use APL all the time and want to type APL symbols into e-mail messages, etc. It is most definitely time for an overhaul of the keyboard technologies that we use and this will be on the to do list for the next development cycle. Until then, I hope you manage to get by with the advice that has been offered so far!
Thanks for the shout,
Morten Kromberg, CTO, Dyalog
I have looked everywhere and I am still unable to switch off this 'feature'!
I've been using vi and, later, vim, since the 80's and I have never had need of multiple cursors, nor can I see a use for them.
:<range>s/search/replace/ does everything I need so this new feature is infuriating beyond words, especially as I've no idea how to switch it off when it seemingly-randomly appears.
Would someone be wonderful enough as to tell me how to banish, remove, consign-to-history the multiple cursors feature in VSCode Vim 1.12.4, please?
I believe this issue is specific to the plugin. I experienced it with the HTML plugin recently, and I'm assuming you have the same problem with HTML files, but the same principle should apply to other plugins as well. You just have to find the setting.
In the VS Code settings, there is an option that reads:
HTML: Mirror Cursor On Matching Tag
You can uncheck the box there to disable the feature. Or you can go to the settings.json in your local repo (inside the .vscode directory), or the equivalent global file, and add/modify the following field like so:
"html.mirrorCursorOnMatchingTag": false
That should take care of it for you.
I am using Visual Studio Code with English keyboard layout switched in Windows when programming, but when I am using my computer for general use I use Slovak keyboard layout. Sometimes it can get ridiculous when I switch from one to another multiple times in one minute. Is there a setting (or a plugin) that could set the keyboard layout in VS Code to English while Windows layout is still set to Slovak?
I will summarize for you the solution to this, hope it is still helpful for you or any other looking for this answer:
you have to press Ctrl+Alt+P
then in the display that will appear at the top, write the language you want in case it does not appear
once this is done, VSC will ask you to restart.
once restarted is done it should be fine.
It is the way to do it without changing windows configuration as you will see in ther similar posts.
Hope it helps
I've been searching for a way to do this. I use a slightly modified Colemak keyboard layout and I can't figure out how to add it as a supported input method in the new language selection in Windows 8. The installer that the Colemak guys distribute sort of works; you can choose the layout after installing it, but it forces the EN-us language, and can't be chosen for other languages.
If anyone knows how to do this properly, I'm sure the Colemak guys would appreciate hearing about it, and it would let me make the modifications I want to.
I don't know if this is the exact issue but there is a problem with MSKLC-generated layouts in Win8 (DP&CP).
You can choose the language if you make your custom keyboard layout with MSKLC: in the "Properties" part, or, if it does not work (though I'm sure it does), you can edit the .klc file manually.
Build it and setup with the executable. You are done.
Question: Is anyone out there familiar enough with Komodo Edit to shed some light on this macro? I need to figure out how to do buffer text selection in a macro when it is invoked via the tool panel.
Problem: I have a very simple macro in Komodo Edit javascript that works as expected, but only when invoked via a custom keybinding. If the user tries to invoke it from the standard "tool panel" the selectWordLeft invocation does nothing. My guess is the failure is caused by the edit buffer not having focus, but one would have thought that telling the macro to expressly give focus to the buffer would work.
komodo.view.setFocus();
komodo.doCommand('cmd_selectWordLeft'); /// this NO_WORKY
Background:
Komodo Edit, version 5.0.2, build 2604, platform win32-x86.
Built on Wed Nov 19 18:33:41 2008.
Answer: Did some more searching and came across this response to another question on a KE forum; which seems to fix the problem.
Instead of deleting the question, here's an answer in case anyone else out there has the same or similar problem.
There are currently some issues with komodo.docommand and some commands.
To work around this, change this line:
komodo.doCommand("cmd_selectWordLeft");
to this instead:
komodo.editor.wordLeftExtend();