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

Purpose of *envrc-allow* and *envrc-deny* buffers #50

Open
doolio opened this issue Oct 21, 2022 · 1 comment
Open

Purpose of *envrc-allow* and *envrc-deny* buffers #50

doolio opened this issue Oct 21, 2022 · 1 comment

Comments

@doolio
Copy link

doolio commented Oct 21, 2022

What is the purpose of these special buffers? They are just empty buffers for me or am I missing something. Any direnv related messages are relayed to me via the *envrc* buffer and/or the echo area. Couldn't the *envrc* buffer serve as the DESTINATION argument of call-process?

@purcell
Copy link
Owner

purcell commented Oct 24, 2022

Yes, maybe! Needs some consideration, I think. I don't currently remember the original rationale. Probaby the idea was to display just the output of the single command that the user had explicitly run, but if the resulting buffer is empty (which is strange!) then that's not super helpful.

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

No branches or pull requests

2 participants