I have a mediawiki installation. When I double-click on text, mediawiki goes into edit mode. I don't like this, because I want to use double-click for selecting text. (I actually use triple-click for selecting a paragraph because I have a Mac and it just works.)
How do I disable double-click to edit?
I'm happy to disable it individual users, or disable it system-wide. I'm the only user.
It's unclear from your question if you want to disable this for you as a user, or change the default setting.
In the latter case, as an administrator, add this line to your LocalSettings.php:
$wgDefaultUserOptions['editondblclick'] = 0;
Though the default setting in a fresh MediaWiki install is '0', or 'false' (at least in the latest stable version, MediaWiki 1.34)
If you want to disable it for you as a logged-in user:
Go to the page Special:Preferences, click on 'Editing' and deselect 'Edit pages on double click'. Be sure to save.
If the default setting was '1' and you want to disable it for all existing users, you can use the script: UserOptions.php
Documentation on this setting can be found at: https://www.mediawiki.org/wiki/Manual:$wgDefaultUserOptions#Default_values
Related
I wanted to set $cfg['RowActionLinksWithoutUnique'] to TRUE so that I can edit the datas in phpMyAdmin without any Primary Keys present, but after checking over config.inc.php and both layout.inc.php in phpmyadmin/themes/
I can't find the mentioned configuration.
Does anyone know how where can I modify $cfg['RowActionLinksWithoutUnique'] ?
Currently using phpMyAdmin via XAMPP Control Panel v3.2.2.
There are default directives, and you only need to put something in config.inc.php if you are changing from the default. In fact, the official phpMyAdmin distribution doesn't come with a config.inc.php at all; if you need to change some value you have to create the file yourself. Since you're trying to change a setting that doesn't already exist in your configuration, you simply have to add it to config.inc.php. Just find a good section, anywhere will do really (I like to keep it near the top so it's visually separated from the server-specific settings), and add the complete line like $cfg['RowActionLinksWithoutUnique'] = true;
Save the file, logout and log back in so the changes are loaded, and you should be all set.
You can see more information in the phpMyAdmin manual.
Just open XAMPP and click on "Config" in the Apache module. Then select "phpMyAdmin (config.inc.php)".
Don't forget to set the semicolon ';' at the end of the variable.
$cfg['RowActionLinksWithoutUnique'] = true;
I'm pretty sure that on other computer when I've used 'Find in Path' or pressed Ctrl+Shift+F when I've previously selected directory, radio button 'Directory' in 'Scope' was checked by default. Now I must press Ctrl+Shift+F and press Alt+O additionally for searching in selected directory. Maybe that's some bug?
How to set my Find in Path dialog so it will be saving last search options? I see that it's saving options listed in 'Options' area in 'Find in Path' dialog. Scope is changing to 'Whole project' all the time.
I can't find that option in PhpStorm. I can't find similar problems/explanation of problem in google.
Maybe that's some bug?
No bug here -- works as designed.
I can't find that option in PHPStorm, I can't find similar problems/explanation of problem in google.
There is no such (global) setting.
Some of the options on that dialog window will be set accordingly to the context (where it was invoked from):
if invoked from Editor (focus was in Editor when you pressed Ctrl + Shift + F) then it will be "Whole Project". In most cases that's exactly what will be needed.
if invoked while having focus in Project View panel .. then it will select that particular directory as default scope/path.
You can follow this ticket for any progress on this matter: https://youtrack.jetbrains.com/issue/IDEA-87037
I realized, that if there is index update running, that's behaving in such way. When indexing is finished, everything works as I'm expecting (so, PHPStorm is searching in selected directory). I think it looks weird.
I would like to edit my default settings in Sublime Text 3 (beta build 3059) to not ignore the Vintage package - via Preferences > Settings - Default. I am running Sublime Text on Windows 7 Pro x64.
The Vintage package's documentation says to edit and save the default settings file to enable Vintage mode:
When I click the Settings - Default menu item, the default Preferences.sublime-settings file opens with expected content; but I cannot edit it. For example, deleting or backspacing to remove "Vintage" in "ignored_packages": ["Vintage"] does nothing.
I thought maybe the default settings file was marked readonly and tried to check it: C:\Users\me\AppData\Roaming\Sublime Text 3\Packages\Default\Preferences.sublime-settings does not exist. C:\Users\me\AppData\Roaming\Sublime Text 3\Packages\Default does not exist either.
To work around this, I tried to save the default settings file that Sublime Text opened for me - to see if that would create the Default directory and Preferences.sublime-settings in it. Instead Sublime Text gave the following error:
Unable to save C:\Users\me\AppData\Roaming\Sublime Text 3\Packages\Default\Preferences.sublime-settings
Error: The system cannot find the path specified.
Has anyone encountered this issue with Sublime Text 3 (specifically in trying to enable Vintage mode or otherwise) and worked around it...or found an authoritative explanation for it?
I reason that next I could try to add the missing Default directory myself, create an empty Preferences.sublime-settings text file in it, and try again to save the default settings file that Sublime Text opened for me; but this is starting to feel kludgy.
You should not edit the default settings. Add the files you want to ignore to the file Packages/User/Preferences.sublime-settings. You can open this file by going to Preferences - >Settings - User. Anything you set here will override the default settings.
I understand that you want to Not ignore the Vintage rather.
This still can be done using the Preferences.sublime-setting-User. AFAIK, any value given in this file overwrites the entries in Preferences.sublime-setting-Default.
Simply add this line with the "Vintage" removed in it to your User preferences and you'll be fine. (Remember to save the file after you did the edit and the change will happen instantly)
Also, not that VI mode in sublime is on edit more by default so make sure you press Esc first to make sure VI is activated.
// Settings in here override those in "Default/Preferences.sublime-settings",
// and are overridden in turn by file type specific settings.
{
"ignored_packages": []
}
Update
The latest format is,
{
"ignored_packages":
[
// Line below is commented out to enable Vintage.
//"Vintage"
],
// To start Sublime in Command moder
// rather than Insert mode.
"vintage_start_in_command_mode": true
}
Install 'PackageResourceViewer' from 'Install Package' in the Command Palette.
Then use 'PackageResourceViewer' command in the Command Palette.
Use that to extract/open the default packages you previously were unable to.
More information here : https://github.com/skuroda/PackageResourceViewer
I use Sublime Text3 recently in Windows 10. I'm trying to change the file: Packages/User/Preferences.sublime-settings. And met your problem "Enable to sa ve Preferences.sublime-settings".
I solve this by changing file Preferences.sublime-settings's property, in Security, edit "user"'s permissions. Allowed to modify.
And then I can edit and save Preferences.sublime-settings
When I install Sublime Text in Linux, I report the message NOTADIRECTORYERROR: [ERRNO 20] NOT A DIRECTORY. At first I thought it was because the Defalut folder was missing, but later I realized it wasn't. I then checked the Settings of my SublimeREPL. Sublime-setings and deleted the contents after bin, and found that the program worked fine.
old: "default_extend_env": {"PATH": "{PATH}:/home/bgnv5/anaconda3/bin/python"},
new: "default_extend_env": {"PATH": "{PATH}:/home/bgnv5/anaconda3/bin/"},
Spent a lot of time to find problems, I hope to help you.
I'm (trying to) using CSS Lint plugin for Sublime Text 2.
Once I've run it, I can't remove the highlight.
"Escape" just remove the console window.
Hitting again the command just "re-lints".
How can I remove the highlight?
Thanks
Changing the Preferences for a ST2 Plugin
Go to Preferences -> Package Settings -> CSS Lint
Choose Settings - Default to see the default settings for this
plugin.
If there are items in this section you would like to change, copy and paste the default settings in the Settings - User file, and then change them there.
This process will ensure that your changed settings are preserved if/when the plugin is updated.
Another Plugin Option
As a side note, I prefer using SublimeLinter. It includes cssLint and has a pretty robust set of settings options. You can find more information about this plugin on this SO question.
I am on Lion - and in the command line, when I open up my project using "subl ." in my project folder - it opens up the last project I had open before I quit Sublime.
I have the Max Preference "Restore windows when quitting" unchecked.
How to I prevent this behaviour? Is there a preference setting for this?
I think the behavior you want can be enabled by changing the hot_exit and remember_open_files settings. If you check out the "Global Settings - Default" preferences, there are some comments there describing these settings.
If you want to change them, you should override them in the "Global Settings - User" file to preserve your changes across updates.
If anyone is wondering how to do this in sublime text 3, copy and paste the following into settings - user:
"hot_exit": false,
"remember_open_files": false,
I could only get it to work by also setting "hot_exit": false in my preferences.
On Linux, I had an issue where I couldn't even start Sublime Text 3 because there were too many files open and it would hang before I got a chance to change the settings.
I did what Mike Wizowski suggested and edited my $HOME/.config/sublime-text-3/Packages/User/Preferences.sublime-settings to include those settings.
However, restarting Sublime Text after this did not seem to fix my problem because Sublime still opened all the files and folders.
I found that deleting the 2 ".sublime_session" files in $HOME/.config/sublime-text-3/Local/ made Sublime Text forget what the recently opened files/folders were, thus fixing my hanging text editor.