This repository has been archived by the owner on Jun 20, 2023. It is now read-only.
forked from jeremyramin/terminal-plus
-
Notifications
You must be signed in to change notification settings - Fork 161
Can't open terminal into current directory. #633
Labels
Comments
You can, it works right click dir and open with atom. Then when you open the terminal panel its in that dir. Also open folder in Atom does similar, again then open the terminal panel. |
When you open atom it usually has previous projects and folder open in it. So it wont work with preloaded folders/projects. So In order for me to open terminal in that place, i have to remove all projects/folders that are there in the atom already and re add them?! It does not seem like a productive way of doing it. |
@MrAmbiG I agree in part, but cant do anything myself at this time, though if you can, feel free to design and implement a menu entry solution and submit a pull request. =). |
I appreciate the reply. It being the most used plugin in this category, i
am pretty sure the author has a lot of requests in pipeline. I would if i
could but i guess i will wait.
Thanks and Regards,
https://ambig.one/2/
*Gajendra D Ambi *|AWS-CSAA, VCAP6-DCA, 2xVCA, 7xVCP, VCE-CIA, EMC-ISA,
Comptia Server+/A+, MCSE, 2xMCTS vExpert (2017/2018) |
…On Sat, Feb 16, 2019 at 8:52 PM the-j0k3r ***@***.***> wrote:
@MrAmbiG <https://github.com/MrAmbiG> I agree in part, but cant do
anything myself at this time, though if you can, feel free to design and
implement a menu entry solution and submit a pull request. =).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#633 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AK2jqeKAPJh_kwJ0JzTBX4qQjc5Sf6-zks5vOCIzgaJpZM4Zmzxf>
.
|
Read #543 which means the author is out. Its up to the community now. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Everytime the terminal open in directory "C:\WINDOWS\System32\WindowsPowerShell\v1.0" instead of the current working directory.
The text was updated successfully, but these errors were encountered: