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

Investigate gem source code #2

Open
adamniedzielski opened this issue Mar 7, 2022 · 1 comment
Open

Investigate gem source code #2

adamniedzielski opened this issue Mar 7, 2022 · 1 comment

Comments

@adamniedzielski
Copy link

Hey @amrabdelwahab, I hope that you're doing well!

I've been using your approach for a while now in different projects. Thank you for showing it! I also applied some smaller tweaks to it. One thing I'm struggling with is investigating the source code of gems.

In the past I could do:

bundle show jekyll

and then open the directory with my Sublime Text code editor.

I can't find a way to do it now. The gem source code is in the Docker volume which you called bundle. I can see the path when I'm inside the container, but I can't run Sublime Text there. I have Sublime Text on the host, but I can't find the path to the directory with the gems there.

I went as far as:
Screenshot 2022-03-07 at 05 13 14

This is a premium feature of Docker Desktop on Mac. And yet, it requires you to save the directories which is not as convenient as what I had in the past.

Have you run into a similar problem? Do you have an idea how to improve that?

@amrabdelwahab
Copy link
Owner

Hey Adam, Thanks a lot for your awesome issue. I will take some time to investigate a better idea for this. What I personally usually did in the past was that in case I needed that I would just view the source code in GIthub and if I needed to add a break point or so I would then use vim from within the docker container.

However, I am almost certain there is a smart way somewhere to get it to work with bundle open and your host machine's editor. Let me play around with it for a couple of weeks

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