You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This creates a conflict with other modes that also support PHP, e.g. mmm-mode. Issue #32 points out how this can create problems between such modes.
A first step is to make the file patterns for PHP files configurable via defcustom. This will also require redefining php-speedbar-config, as it has a hard-coded assumption about file patterns. After that a couple of options come to mind:
PHP Mode could prompt the user about what to do whenever it is about to clobber an existing auto-mode-alist entry for PHP files.
We could always refrain from affecting existing auto-mode-alist associations unless the user explicitly allows PHP Mode to do so (e.g. through a customizable flag).
There are other ways we could approach this, but the overall idea is to make PHP Mode less intrusive and assuming about what it does to auto-mode-alist.
The text was updated successfully, but these errors were encountered:
Some other modes stake a claim to PHP files, e.g. mmm-mode. PHP Mode
blasts over auto-mode-alist and depending on the order in which a user
loads each PHP Mode may usurp association with PHP files from the
other modes, and that can be annoying to users of those other modes.
This patch appends the file patterns for PHP Mode to the end of
auto-mode-alist so that they will not over-shadow any existing
associations which may already exist.
GitHub-Issue: #32
GitHub-Issue: #105
GitHub-Issue: dgutov/mmm-mode#32
PHP Mode always attempts to establish itself as the major mode for various file patterns. Specifically we do this:
This creates a conflict with other modes that also support PHP, e.g. mmm-mode. Issue #32 points out how this can create problems between such modes.
A first step is to make the file patterns for PHP files configurable via
defcustom
. This will also require redefiningphp-speedbar-config
, as it has a hard-coded assumption about file patterns. After that a couple of options come to mind:auto-mode-alist
entry for PHP files.auto-mode-alist
associations unless the user explicitly allows PHP Mode to do so (e.g. through a customizable flag).There are other ways we could approach this, but the overall idea is to make PHP Mode less intrusive and assuming about what it does to
auto-mode-alist
.The text was updated successfully, but these errors were encountered: