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

Adding project command for GDB. #1497

Merged
merged 2 commits into from
Feb 6, 2020
Merged

Conversation

palikar
Copy link
Contributor

@palikar palikar commented Feb 6, 2020

When I am working on a big project and I have opened a file, deep into the directory structure, it's annoying to navigate the GDB execution to the build folder. (Lots of ../../). With the new function in this, GDB can be executed at the root of the project which allows an intuitive path for the build folder to be given.


  • The commits are consistent with our contribution guidelines
  • You've added tests (if possible) to cover your change(s)
  • All tests are passing (make test)
  • The new code is not generating bytecode or M-x checkdoc warnings
  • You've updated the changelog (if adding/changing user-visible functionality)
  • You've updated the readme (if adding/changing user-visible functionality)

@bbatsov
Copy link
Owner

bbatsov commented Feb 6, 2020

The addition is fine by me. It needs an entry in the changelog and potentially in the docs.

@palikar
Copy link
Contributor Author

palikar commented Feb 6, 2020

I update the changelog but I couldn't fine a place in the docs with a big listing of all interactive commands in projectile.

@bbatsov bbatsov merged commit 84be1da into bbatsov:master Feb 6, 2020
@bbatsov
Copy link
Owner

bbatsov commented Feb 6, 2020

Hmm, I thought we had this somewhere. Anyways, not a big deal.

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