Skip to content
New issue

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

Treat direnv-non-file-modes as possibly derived modes. #49

Merged
merged 2 commits into from
Jun 19, 2019

Conversation

stribb
Copy link
Collaborator

@stribb stribb commented Jun 19, 2019

Suppose we're in a Magit Status buffer, whose major-mode is magit-status-mode, which is derived from magit-mode.

With this change, if direnv-non-file-modes contains magit-mode, direnv-mode
will now treat it as a non-file mode.

Open question: do we add magit-mode to the default list?

Say major-mode is magit-status-mode, which is derived from magit-mode.
With this change, if direnv-non-file-modes contains magit-mode, direnv-mode
will still treat it as a non-file mode.
Copy link
Owner

@wbolster wbolster left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in general, looks good. minor question above

@wbolster
Copy link
Owner

thanks! whenever this is merged, another pr that adds magit to the defaults sounds fine

I'h having a hard time believing it but I had indent-tabs-mode t.
@wbolster wbolster merged commit 91d6fcc into wbolster:master Jun 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants