I mean to get completion of variable names, function names, function argument names, and keywords in Octave, similarly as in Eclipse CDT, e.g.
This works in the Command window, but not in the Editor, where only keywords and functions can be completed.
Official documentation indicates <Tab> and <M-?> should work.
If I press <Tab> I get a Tab character inserted.
And I do not know which is the Modifier key. Plus, I have a Spanish keyboard, so the question mark is obtained with <Shift>+', so I am not sure how will it work if I find the correct M key.
How can I enable it for the Editor?
Notes:
Help -> About shows
GNU Octave, version 4.4.1... configured for "x86_64-w64-mingw32"...
Using Octave portable under Win 10.
I found files <octave-dir>\etc\inputrc.default and <octave-dir>\share\octave\4.4.1\m\startup\inputrc
There is a file C:\Users\user1\.config\octave\qt-settings containing
...
[editor]
...
codeCompletion=true
...
codeCompletion_threshold=2
codeCompletion_keywords=true
codeCompletion_octave_builtins=true
codeCompletion_octave_functions=true
codeCompletion_document=false
codeCompletion_case=true
codeCompletion_replace=false
...
tab_indents_line=false
This refers to the speed of readline for Octave under Win. I have speed issues with readline of my Portable Msys2 under Win 10, but this is a different issue.
On the top of the editor widget, select Edit > Preferences.
Select the Editor tab.
Look for Auto Completion.
Select Match words in document.
There are essentially no references that mention completion specifically in the editor.
The only one I found, from 2014, stating that:
There is no editor completion on all known function names, nor on
parameter lists of known functions. There is an open bug report
requesting function name completion in the editor, see
http://savannah.gnu.org/bugs/?41371.
The GUI is an experimental new feature in the 3.8 release, please
consider helping to improve it for 4.0 by joining the maintainers
mailing list or participating on the bug tracker (even submitting
feature request bugs if you want).
So at that time it was not available.
Related
I've just installed Octave 7.1.0 and I noticed a strange sequence of error/warning messages which I had never seen before nor am able to decipher:
2022-05-06T16:59:34.366ZE [6832:ShellIpcClient] message_loop.cc:133:Run Run called on MessageLoop that's already been Quit!
2022-05-06T16:59:34.368ZE [12660:ShellIpcClient] message_loop.cc:133:Run Run called on MessageLoop that's already been Quit!
2022-05-06T16:59:34.369ZE [8132:ShellIpcClient] message_loop.cc:133:Run Run called on MessageLoop that's already been Quit!
2022-05-06T16:59:34.371ZE [15212:ShellIpcClient] message_loop.cc:133:Run Run called on MessageLoop that's already been Quit!
Since I haven't had the time to test this new version (a mere 1/2 hour has passed since I installed it) I cannot tell whether or not Octave's functionality is compromised.
Any ideas?
Wherever this message comes from, it is not from Octave. Someone reported the same issue last year on Octave's forum at Strange opening messages when opening Octave each time which links to a similar issue on the Far Manager bug tracker. The Far Manager devs suggest that this comes from Google drive:
When you open a context menu, all registered shell extensions are loaded into the Far process. These extensions implement custom context menu items, shown by various software. Sometimes the authors of these extensions add various debug logging messages to their code to see what is going on in various situations. Sometimes these authors are too lazy to implement a proper logging and they just print stuff to the standard output stream, connected to a console. Windows Explorer doesn't have a console attached to it, so all these messages go into the void. Far, on the contrary, does have a permanently attached console - you're looking at it. Therefore, any debug stuff these lazy people print in their extensions ends up in that console.
It's quite sad, but there's nothing we can do about it.
Please search for that string ("Run Run called on MessageLoop that`s already been Quit") in your Program Files folder and, once found, report to the corresponding product owners. I suspect that in your case it's Google Drive.
I am trying to modify Chromium browser's behavior in Chromium OS.
When I execute Chromium browser, I can handover arguments with '--enable-features=' flag.
And I found a argument (#enable-virtual-keyboard) from Available list in chrome://flags.
Then I executed Chromium browser like below.
example instruction # /opt/google/chrome/chrome --incognito --enable-features=enable-virtual-keyboard
And when I check the flags in chrome://version, I could see the arguments.
Command Line: /opt/google/chrome/chrome --blahblah --enable-features=enable-virtual-keyboard
But actually the virtual keyboard is not working.
When I enable the argument (virtual keyboard) from chrome://flags manually. It works well and I could see the Virtual Keyboard.
What is wrong? I would appreciate it if you guys advise me.
--enable-features actually takes the name of a feature, not the name of a flag. The Chromium documentation explains the difference, but to simplify somewhat, a flag is sort of a user-visible interface to a feature or a command-line switch.
Anyway, to do what you want, you need to find out what feature or command-line switch the enable-virtual-keyboard flag toggles. Searching for enable-virtual-keyboard in Chromium Code Search brings us to these lines in about_flags.cc:
{"enable-virtual-keyboard", flag_descriptions::kVirtualKeyboardName,
flag_descriptions::kVirtualKeyboardDescription, kOsCrOS,
SINGLE_VALUE_TYPE(keyboard::switches::kEnableVirtualKeyboard)},
That last line tells us what we're looking for: that this flag is actually backed by a command-line switch, not a feature. Clicking on kEnableVirtualKeyboard shows us its definition:
const char kEnableVirtualKeyboard[] = "enable-virtual-keyboard";
So, adding --enable-virtual-keyboard to your command line should have the same effect as flipping the flag. (I should note, though, that there are a number of things that can break the virtual keyboard, so you may have to do other things to get it working.)
For the sake of completeness, if you'd found that it was actually backed by a feature, like the gesture-properties-dbus-service flag, for example:
{"gesture-properties-dbus-service",
flag_descriptions::kEnableGesturePropertiesDBusServiceName,
flag_descriptions::kEnableGesturePropertiesDBusServiceDescription, kOsCrOS,
FEATURE_VALUE_TYPE(chromeos::features::kGesturePropertiesDBusService)},
Then clicking kGesturePropertiesDBusService takes us to its definition which specifies the feature name:
const base::Feature kGesturePropertiesDBusService{
"GesturePropertiesDBusService", base::FEATURE_DISABLED_BY_DEFAULT};
...so in that case you'd pass --enable-features=GesturePropertiesDBusService to enable the flag from your command line.
While I'm familiar with a few of the options Zsh provides for autocompletions (i.e. the standard Tab menu-complete and the Ctrl+i completion option), but I've been spoiled with the type of search/completion you can get out of PhpStorm.
For example, in a stock Laravel project in PhpStorm you are able bring up the Search Everywhere dialogue (Double Shift), type in wbp, and have the editor complete that to "welcome.blade.php". The closest I can get to that functionality with Zsh would be to type in wb, place the cursor between the two letters (w|b), and use Ctrl+i.
I have searched around and found a few custom completion scripts, but none that have this type of functionality.
So the big questions are:
1. Is it possible to have smart completion functionality in Zsh like it exists in PhpStorm?
2. If so, how does one go about enabling it?
If it's relevant, I'm using OhMyZsh on OS X 10.12.
The following setup works for me (put them in ~/.zshrc):
zstyle ':completion:*' matcher-list 'm:{a-zA-Z}={A-Za-z}' 'r:|[._-]=* r:|=*' 'l:|=* r:|=*'
unsetopt CASE_GLOB
zstyle ':completion:*' completer _complete _match _approximate
zstyle ':completion:*:match:*' original only
zstyle ':completion:*:approximate:*' max-errors 2 numeric
Reference: zprezto
I've installed a Javascript formatter into ST2. For some reason, the keyboard shortcut is not working suddenly. When I search in my keymaps for alt+ctrl+f I don't see anything. How can I figure out why this shortcut is no longer doing anything? You can see the poorly formatted js in the screenshot. If I call the command via Sh+Ctrl+P it works fine. Does the Ctrl+Alt+F on the right side in the screenshot indicate that that command is bound to that shortcut, or just that the package thinks that it is bound to that?
I would suggest you try to use FindKeyConflicts. This plugin will:
Assist in finding key conflicts between various plugins. This plugin
will report back shortcut keys that are mapped to more than one
package. This does not guarantee that the listed plugins are
necessarily in conflict, as details, such as context, are ignored.
This is simply a tool to help assist what plugins may be conflicting.
I think the SublimeText 2 editor has a lot of potential, but I'm struggling to learn the keyboard shortcuts, because unlike Vim it doesn't have comprehensive documentation, or a command to show you what each key combination is bound to.
It's frustrating going through the .sublime-keymap files and find that 4 different packages all rebind ctrl+t for their own purposes.
So, is there a way to view all the keybindings in an organised way: by key, by package, by command - with descriptions?
Currently my hack is a bash function that shows me all the keymap lines that mention a certain key. For example, *sublime_keys '+t'* finds me all the bindings that use the letter "t"
function sublime_keys {
find ~/.config/sublime-text-2/Packages \( -name 'Default (Linux).sublime-keymap' -or -name 'Default.sublime-keymap' \) -print0 | xargs --null ack-grep -C1 "\".*$*"
}
I've tried KeymapManager but it is very limited - only shows bindings from some of the top-level non-default packages without descriptions or package context. I suppose I could take time to improve on it.
Is there a package that does this better?
I am using a package called KeyCue on OSX. I find it very helpful because I have the same difficulty in remembering all the keystrokes.
http://www.ergonis.com/products/keycue/
On the Mac, when you press and hold the "Command" key for 1 sec, a pop up window will appear and show you all the keystroke for Sublime Text 2, and all other software also. I think it scans through all the menu and show you the keystrokes.
You can also add custom keystrokes. I have added for zencoding and color picker as the keystrokes are from installed package and KeyCue cannot pick those up automatically.
The package is not free (Euro20). Well worth the price as I use it frequently and saves me lots of time.