I'm using chrome with the extension vimium and set duckduckgo as my default search engine.It's really useful to get search results with duckduckgo bangs.But I can't use that through vimium's vomnibar.Is it possible to combine?
Go to Vimium settings
Inside "Custom search engines" text box, uncomment the line
containing duckduckgo mapping by removing the leading hashtag:
d: https://duckduckgo.com/?q=%s DuckDuckGo
Save changes
Now open vomnibar and type d followed by a space. This will
trigger
duckduckgo autocompletion.
Related
I've created a bunch of snippets in Sublime Text 2, but I cant remember them all off the top of my head. I've seen in a number of tutorials that as people start typing their snippets tab-triggers it will start to provide a list of the matching snippets. I don't see this.
Is there a setting somewhere for this? Or do I need to create a special file (completions file?). For most snippets I have the <scope> commented out as I may use in a PHP or HTML file for example depending what I am working on.
Most of my snippets tab triggers start the same elq- prefix, so it would be very helpful if it were to start showing me the options as I type.
The setting auto_complete_selector controls when Sublime automatically offers the popup for possible completions. The default value for this setting is:
// Controls what scopes auto complete will be triggered in
"auto_complete_selector": "source - comment",
This means that it will automatically pop up for any file that's considered a source code file, except within a comment.
The scopes for the file types that you mention in your question are text scopes and not source scopes, which stops the popup from appearing.
One way around that would be to manually invoke the auto complete panel by using the appropriate key binding, which by default is Alt+/ on Linux or Ctrl+Space on Windows/OSX. When you do that, the popup for possible completions at this point is manually displayed.
To allow this to work more automatically, you would need to modify the setting for auto_complete_selector to be more appropriate for your situation.
To do that you could select Preferences > Settings - User from the menu and add or modify the auto_complete_selector setting as follows:
"auto_complete_selector": "source - comment, text.html",
This says that the selector should always be displayed in source files except inside comments (like the default) and also within HTML files.
You could also use text instead of text.html if you want it to work in all text files of all types, although this would possibly get quite annoying while working with plain text files. Substitute an appropriate scope or set of scopes here as appropriate to dial in the places you want this to be automatically offered.
We are working with a custom top level domain per developer which points to it's localhost, so internally we would have url's like this
companywebsite.com.john
companywebsite.com.mike
subdomain1.companywebsite.com.john
..
subdomain99.companywebsite.com.john
The problem is that every time when we need to access a sub-domain for the first time(and we have a lot of them) chrome always redirects to a google search, then after a few attempts, asks if we actually mean
http://subdomain99.companywebsite.com.john/
So, my question is, how could I set up chrome to always parse that kind of url as a url not a search.
Thank's
In the end this is what we ended up doing:
1. go to **Settings**
2. in Search section click on **Manage search engines**
3. Scroll down to the bottom until you find an empty entry
4. Fill in these values: (noSearch, null, http://%s)
5. Scroll back up in the list, find it and click **Make default**
For my case I found an easy solution by chance, add a forawrd slash / at the end of your url and chrome will revert to url, in your example: companywebsite.com.john/
Check the screenshots below:
Before you add slash
when you add the slash at the end, Chrome will translate it to a url
My problem is simply that some of the Emmet snippets and abbreviations get overridden by the Sublime Text 3 default tags - for example, when I type 'link' and press TAB I don't end up with:
<link rel="stylesheet" href="">
as stated in the Emmet documentation (https://github.com/emmetio/emmet/blob/master/lib/snippets.json).
Instead I get:
<link rel="stylesheet" type="text/css" href="">
This which is the Sublime Text 3 default. The same goes for 'img' and a few other useful tags, and now I'm wondering: why is that and what can I do "fix" it? I want the Emmet snippets to have "first dibs", and not the other way around.
Open Preferences -> Package Settings -> Emmet -> Settings-User and add the following content (it should be empty upon opening it for the first time):
{
"remove_html_completions": true
}
Save the file, then restart Sublime.
For a look at all the options you can customize, open Preferences -> Package Settings -> Emmet -> Settings-Default. If you see anything that you'd like to change, copy the setting to Settings-User, making sure there's a comma , at the end of each line except the last one.
Just for the record I want to convey that I've finally found the solution to my problem. It would seem as if Emmet has this built in setting where you can specify in which scopes you want your code editors' defaults to override Emmet, and as a default this is set to "text.html". Hence what I needed to do to resolve my issue was just to change this setting to none by simply typing
{
"disabled_single_snippet_for_scopes": ""
}
In the Emmet user settings. Cheers!
It’s pretty hard for Emmet to play nice with native Sublime Text snippets due to lack of API. But Emmet tries to guess what you want to do as much as possible.
By default, when you type something in ST that matches native snippet you’ll likely see an autocomplete popup with snippets proposals. Which means you’ll likely want to expand native snippet by pressing Tab key. On the other hand, most Emmet abbreviations doesn’t look like predefined snippet, e.g. you won’t see autocomplete popup when typing abbreviation.
Thus, Emmet doesn’t expand abbreviations by Tab key when autocomplete popup is visible. It seems like a decent solution for native snippets problem (ST API can tell if popup is visible). I’m pretty sure in your link example there was autocomplete popup visible.
For hardcore Emmet users it’s possible to disable this behaviour and force Emmet to always expand abbreviations by Tab, event if autocomplete popup is visible. To do so, go to Preferences → Settings-User and add the following option:
"disable_tab_abbreviations_on_auto_complete": false
See https://github.com/sergeche/emmet-sublime/blob/master/Preferences.sublime-settings#L29
In Sublime Text 2 I have installed the trailing spaces plugin, however the highlighting is always set to disabled.
if I toggle the highlight regions, by doing the following:
edit -> trailing spaces -> highlight regions
I always get the following:
highlighting of trailing spaces is disabled!
I have restarted sublime since the package install, but the toggle doesn't seem to work, does anyone know how to fix this issue?
Work around fix - not the solution to the problem
As for others it seems, i couldn't seem to get this trailing spaces to highlight no matter what i did, so what i did was remove the trailing spaces automatically on save. Not ideal but used to it now, works nicely.
Go to SublimeText 2 > Preferences > User Settings (or just hit the Mac Standard cmd + ,). This should open your User Settings as a JSON file. Add the following to your file
"trim_trailing_white_space_on_save": true
That's it. You're good to go.
I had this problem in Sublime Text 3.
I fixed it by deleting my trailing_spaces.sublime-settings file in the Sublime Text user package settings folder (which for me was %APPDATA%\Sublime Text 3\Packages\User) and reinstalling the plugin.
Some more discussion about this issue can be found on the plugin GitHub page here.
It's a known bug - see their Issues page on GitHub.
I was able to get it working by starting Sublime with a non-blank string value for the setting trailing_spaces_highlight_color
Open Preferences > Package Settings > Trailing Spaces > Settings - User
Replace:
"trailing_spaces_highlight_color": ""
With:
"trailing_spaces_highlight_color": "invalid"
Restart Sublime.
Edit > Trailing Spaces > Highlight Regions should work as expected now.
If you restart Sublime, "trailing_spaces_highlight_color" must not be a blank string, otherwise it will stop working again. Repeat the steps above to fix.
As long as Sublime is started with a non-blank string value for trailing_spaces_highlight_color, the toggle highlight regions works.
It looks like the plugin is caching the value in the setting file when Sublime loads. If you make changes to the settings file and toggle highlighting, the original value is restored. Which is why you need to restart Sublime for setting changes to take effect.
I have ST2 installed on Win7 and for some reason the global 'Find in Files' (ctrl+shift+f) stopped working (it worked before). Now all i get is :
Searching 0 files for "capbSectionac"
0 matches across 0 files
The regular search in the currently opened file is working correctly.
I tried re-installing it but to no avail :(
Anyone encountered it? Any solution?
Note that it says "Searching 0 files".
In the second field "Where:", make sure you don't have a folder selected. You should see the placeholder text "Open files and folders" which means that it will search in the whole project. If you don't see this placeholder, even if the "Where" field is empty try clicking on the "..." button and then click on "Clear".
source: http://www.sublimetext.com/forum/viewtopic.php?f=3&t=12611
I had the same problem. At some time I noticed that the Where: field (below Find:) didn't show any placeholder text ("Open files and folders"), as it is supposed to when it's empty. It turns out that the Where: field wasn't empty and therefore the search was like happening nowhere. As I cleared this field, the search worked again.
Press ctrl F . then in left side of search bar, enable Wrap. with inverted reload sign
I am new to Sublime Text 3, so when I first tried to use Find In Files (shift+command+y) it yielded nothing but 0 search results.
I brought up Find (command + f) and I noticed alot of spaces before my search term.
I cleared out those extra spaces and left my search term. Brough back up Find In Files and the search worked properly.
I keep having this problem in Unbuntu. The solution I found was just to delete the folder
/home/<user>/.config/sublime-text-2/Packages/User/Package Control.cache
I think this happens because I have file synchronization on save but can't be sure.