We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is it possible to configure atom-autocomplete-php so that the $ -sign is not selected when a built-in PHP function is inserted.
Example: $contents = file_get_contents($filename [, $flags, $context, $offset, $maxlen])
$contents = file_get_contents($filename [, $flags, $context, $offset, $maxlen])
The selected characters after inserting are |$filename|
|$filename|
What i would like is that only the name of the parameter will be selected: $|filename|
$|filename|
The "Non Word Characters" of the Editor (editor.nonWordCharacters) are the default characters: /()"':,.;<>~!@#$%^&*|+=[]{}`?-…
The "Non Word Characters" of language-php are the default characters plus the $-sign: /()"':,.;<>~!@#%^&*|+=[]{}`?-$
Both are apparently not considered.
(Atom Version 1.34.0)
Thank you for suggestions, ws
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is it possible to configure atom-autocomplete-php so that the $ -sign is not selected when a built-in PHP function is inserted.
Example:
$contents = file_get_contents($filename [, $flags, $context, $offset, $maxlen])
The selected characters after inserting are
|$filename|
What i would like is that only the name of the parameter will be selected:
$|filename|
The "Non Word Characters" of the Editor (editor.nonWordCharacters) are the default characters:
/()"':,.;<>~!@#$%^&*|+=[]{}`?-…
The "Non Word Characters" of language-php are the default characters plus the $-sign:
/()"':,.;<>~!@#%^&*|+=[]{}`?-$
Both are apparently not considered.
(Atom Version 1.34.0)
Thank you for suggestions,
ws
The text was updated successfully, but these errors were encountered: