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

I don't want to display *dape-repl* window when dape start, but want create the *dape-repl* buffer #176

Open
jixiuf opened this issue Dec 2, 2024 · 0 comments

Comments

@jixiuf
Copy link

jixiuf commented Dec 2, 2024

Could you add an option for dape-repl? When the option is not nil, and dape-repl is included in dape-start-hook, the dape-repl buffer should be created when dape is started. Additionally, the application's output will be directed to the *dape-repl* buffer instead of the *Messages* buffer.

Currently, if I remove dape-repl from dape-start-hook, it does not achieve the desired outcome. At this point, the dape-repl buffer is not created, and the output is written to the Messages buffer instead, which does not align with my expectations.

Another point is that when I execute M-x: dape-repl, I expect the dape-repl window to be displayed. However, if dape-repl is already the current buffer, I expect the dape-repl window to be hidden when I execute M-x dape-repl.

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

1 participant