I'm new to xmonad and haskell. I try to create a xmonad config on my own, this is the current state: https://gist.github.com/sbechtel/7900440
My problem is the submap on line 45 for different search prompts. It compiles without problems but doesn't do anything. I belief it was working but now it isn't working anymore so my guess is some kind of side effect because I didn't change anything on that line?
Kind regards,
Sebastian
It looks correct on first sight to me. Beware though that there is no prompt for the search engine selection. To test it, you have to to press mod1 + s, then g for example. Only then google pops up.
Related
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.)
This problem really hit a nerve with me. I have both YouCompleteMe and UltiSnips installed on my vim 8.0 editor. It seems that both of these plugins use the tab key for doing the auto-completion and that has created an incompatibility that has been also addressed by this question. My question is more specific, though. When I write a piece of code like <html, there is a pop-up menu that shows me all related snippets for that code.
I use the tab key to navigate through that menu but when I hit ctrl+y to accept and therefore expand one of these snippets, nothing happens! I think this structure suggests that it's possible to somehow choose one of those snippets from the menu without trying to define a shortcut for UltiSnip. What am I doing wrong? How should I navigate and choose those snippets?
I also would not want to stuff my vim with any new plugins (like supertab, etc.).
The solution was actually a lot simpler than I expected. In the beginning, I felt stupid for not knowing it but when I find a similar question like this one, I thought that probably many were fallen into the same trap.
I don't know whether to name it a bug or not but it's how Ultisnips and YouCompleteMe work together. In order to expand a snippet, you have to write the initializer exactly as it's defined. Of course, this seems obvious, but when you see a pop-up menu of different snippets, you might think they can be chosen but it only works if you already wrote the snippet initializer exactly as it's defined.
So when a snippet is called "html5"---as it's shown in my question---writing an extra opening bracket (<) will cause it to stop working. It cannot be expanded.
Also, don't forget to check out Siegfried Gevatter configuration. It's not possible to use tab key both for navigating into the pop-up menu and expanding the snippets.
P.S. It was nice if navigating through the pop-up menu could change the whole word (including the angle bracket), not just what succeeds it. This feature works this way in most of the other editors I see and that's probably why I wasn't able to spot the problem in the beginning.
Some context
I've recently switched to ubuntu budgie (from unity), and I am really tired of the Plank/panel menu combo. I cannot find a setting that suits me, because depending on my screen setup, there's always something in the wrong place.
I am literally unable to show the menu on certain edges if I activate auto-hide, and if I don't activate it, it's not nice at all, to the point that I have removed the plank thing altogether. (Am I having strange bugs on this OS, or is it really messy?)
My idea
With great frustrations come new ideas. I thought again about one I had in the past. I would like to have a circle menu that pops around my mouse cursor when I press a given key combination (very much the kind of thing you would find in some games).
The main use case is to get "pined" application shortcuts easily when I need them, but perhaps other things would fit well with them (commands ...).
Questions
So my questions are:
Does such a thing already exist?
If it doesn't, is it difficult to realize? (How much time, complexity, ...)
What tools/libraries are needed for such a project? I know I'll find plenty of explanations on the gnome developer website but I could really use some more help.
Since you mention a buggy behaviour on Plank, depending on the screen configuration, I suspect you are suffering from this bug. In short: Plank's returned values for the space it needs are not always correct in multi monitor setup.
A neat option to replace at least part of the functionality is Ulauncher, by default called from a shortcut, but you could trigger it from anything that is capable of running its command.
Since Ulauncher's window simply identifies in the window list, you can easily write a script to move it to the current mouse position.
In case you'd need any help in that, just leave a comment.
Not sure if you are also referring to quick access of the window list, but for that you could use the Window Previews applet, or even the Workspace Overview applet, so life without Plank is possible.
I'm having a bit of an odd problem... recently I've been having some odd situations arising whilst using CoqIDE, namely:
I can't type the letter "v" without holding down the windows/super key.
Pressing backspace moves the focus to the previous tab if multiple windows are open, I can't delete things with it. CTRL+backspace works for deleting chunks though.
The first of the two (may have) happened after I changed my keymap from US to GB but switching back and forth hasn't solved the problem.
Running ARCH linux, everything is up to date and no other applications are affected, I don't have sticky keys on.
Thanks for any suggestions!
EDIT: Tried a reinstall, didn't help...
Solved Edit: Yep, you're completely right I seem to have done some super-fast rebind without noticing. I also learnt that package manager will essentially never touch .config files as they're generated by the app and so aren't under the manager's jurisdiction. Solved!
CoqIDE key bindings and other preferences are stored in .coq/ or .config/coq. They are not deleted on uninstall and are shared if you have various versions of Coq installed at the same time (and this may be a problem).
If you are not worried about losing any specific preferences that you configured, I would advise to just delete this directory and let CoqIDE create it fresh again.
If you are worried, then just have a look at the files (quite long but also quite readable). For instance:
cat .config/coq/coqide.keys | grep "tab"
yields the following on my machine:
; (gtk_accel_path "<Actions>/View/Previous tab" "<Alt>Left")
; (gtk_accel_path "<Actions>/View/Next tab" "<Alt>Right")
PS: your problem might have arisen because key bindings are so easy to redefine in CoqIDE that you can do it without noticing: just open a menu (example: View), hover some option (for instance: Previous tab), type something on the keyboard (for instance v) and voilà v is now a shortcut for Previous tab.
I'm using an install of Dreamweaver on my Macbook to code. When I type code on Dreamweaver the hint code still works but it is not perfect. For example, when I type $ it shows the tooltip to hint the code but when I continue to type $_S it does not show code that starts with $_S. (I want it to show tooltip start with $_SESSION.)
I almost feel that this is too obvious to be the answer, but... 'C' and 'S' are different letters. If you wanted it to suggest $_SESSION, you should begin typing $_S, not $_C.