Hello,
I've searched in the docs but could not find how to show which linter reports the error in the quickfix/location window?

In my projects I usually run different linters, but I want to see which error is coming from which linter, so it would be nice to have the name of the linter somehow prepended to the error, eg.:

nuxt.config.js|1 col 45 error| <jshint> Missing semicolon.

Is t

Will add this item for tracking, as I am looking to do some changes to the docsite. The list so far is:

• check optional properties of getter functions and add stuff like ref with explanation.
• add similar examples for useCombobox as in useSelect in the docsite.
• Re-write the beginning of the Readme to better explain what Downshift is (component, hooks).

Correct the terminology used in code and documentation so that it is consistent with HTTPie and web standards. Examples:

• body parameter -> data field
• operator -> separator

now:
when i wirte"html + tab",this would happen:

But what I need is this:

What should I do?
Thank you very much for your help

Bug

• Codepen:
  https://codepen.io/timneyens/pen/VwYdbBK

• The steps to reproduce the issue, e.g.:

  1. Focus on the input field in FireFox
  2. Type c, and wait for suggestions to appear
  3. Press test button
  4. Click outside the container to close suggestions

  Observed behaviour: Suggestions stay open

  Expected behaviour: Suggestions should be closed

Do you want to request a feature or report a bug?

bug

What is the current behavior?

location button isn't working in the demo https://community.algoli

When serviceUrl has been changed a clearCache() method should probably be called to prevent incorrect results.

Possibly the other settings could trigger this as well.

You autocomplete looks good but are there any docs how to style it the way it fits to the respective design ? Would be helpful or better to set in the options

Thanks for this nice plugin

Right now query in the nodejs api is just a string. we should support gql-parsed strings too, so that if they are exported elsewhere, it can be used directly.

import gql from 'graphql-tag';

export const GRAPHQL_QUERY=gql`
  query {
    something {
      anotherthing
    }
  }
`;

Describe the bug
If the first element in the ng-select is a space, it seems like the height of the dropdown is calculated based on a smaller row-height than the rest of the elements.
This only happens if virtualScroll is true

Reproducbile example
https://stackblitz.com/edit/angular-wpjuge

Expected behavior
I expected the dropdown to have the same height as if the first elemen

Currently, if an argument group has an option and a nested sub-group, the usage help will only show the options that are directly in the group under the heading for that group.

Instead, the usage help should also include the options for the nested subgroups, unless this subgroup has its own heading.

kubectl takes several abbreviated alias like svc, ns rc etc. Kube-shell need to honour the operation with aliases when suggesting and auto-completion.

similarly options have short form like -n, -s etc they need to be honoured as well

Prerequisites

• [y] Have you tried launching atom . from the terminal in your project's directory?
• [y] Have you verified the output from go env is correct? If it is, please include the output in this issue.
• [y] Have you updated Atom to the latest version?
• [n] Have you tried using Atom Beta, which can be run side-by-side with Atom Stable? Is the behavior

The documentation states that

Select2 supports a bunch of options. These options may be set in data-* attributes.

In reality, only a subset of select2 options are handled. As far as i understand, this is the place where select2 is called: htt

Is there any demo sample code for accessing the remote data stored with TributeJs.

https://github.com/zurb/tribute#loading-remote-data

Any suggestions over this?

jsFiddle

Steps to replicate:

Select "ap" from select element and click show

ap will be added as the value of the input and horsey will show correctly

Click hide

Select "ba" from select element and click show

ba will be added as the value of the input and horsey will show incorrectly
the suggestion for apple is still showing, and

Bug
This plugin is super useful however it makes use of the method componentWillReceiveProps which is no longer supported by React. React continues to evolve in many directions and now they are getting rid of classes in preference to functions. I still have clients that are React heavy but more and more are moving to other frameworks due to the instability and constant breaking changes being in

Do you want to request a feature or report a bug?
Bug. Happens on 0.37 too.

What is the current behavior?
On Firefox and Chrome mobile I can't select a value from the autocomplete list. Whatever you choose, the result is always the first option.

**If the current behavior is a bug, please provide all the steps to reproduce and a minimal
JSFiddle example

Add missing tests for this library

I am using the vscode extension and there is no autocompletion for $path = $_SERVER['DOCUMENT_ROOT']."/directory".

Can I somehow specify the document root?

I found a (strange) issue in using this plugin.
Without the plugin, this is the autocomplete shown by ST3:

When "All Autocomplete" is active, this is the list of suggestions shown:
![2_allautocomplete](https://cloud.githubusercontent.com/assets/4546453/15106209/0485f510-15c8-1

Here's a completion in Atom with ide-rust

Here's the same completion in VSCode:

<img width="618" alt="screen shot 2017-11-04 at 2 00 56 pm" src="https://user-images.githubusercontent.com/1789/32409005-c8c1fee0-c168-11e7-855c-

Current behavior
I type text and press down arrow. It selects first item and after few seconds refresh dropdown list. I select item again.

Expected behavior
It shouldn't refresh list when I press arrow button.

Minimal reproduction of the problem with instructions (if applicable)
Examples from your demo (https://angular-mfppay.stackblitz.io): "Tags within an autocomplet