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.

Sign up for GitHub

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

Jump to bottom

Redefine compile-command and gud-pdb-command-name to more sensible value #1693

Open
memeplex opened this issue Oct 11, 2019 · 2 comments · May be fixed by #1697
Open

Redefine compile-command and gud-pdb-command-name to more sensible value #1693

memeplex opened this issue Oct 11, 2019 · 2 comments · May be fixed by #1697
Labels
Enhancement

Comments

@memeplex
Copy link

The defaults:

compile-command = make -k
gud-pdb-command-name = pdb

doesn't make much sense.

Why not redefine them, in a very conservative fashion anyway:

compile-command = python
gud-pdb-command-name = python -m pdb

?
@galaunay
Copy link
Collaborator

Couldn't agree more.
I guess it belongs to the elpy-module-sane-defaults module.

@memeplex
Copy link
Author

memeplex commented Oct 12, 2019 •
edited
Loading

For compile-command you need a local variable, you might want to do something like:

  (set (make-local-variable 'compile-command)
       (concat "python " (shell-quote-argument buffer-file-name)))

And a shortcut for compile would be nice, you don't always want to eval an entire buffer into a running interpreter.

This was referenced Oct 13, 2019
Closed
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Redefine compile/debug commands to more sensible defaults (Fix 1693)
2 participants
@memeplex @galaunay