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

This is better, but not exactly what I was looking for... #9

Open
kennonb opened this issue May 11, 2012 · 14 comments
Open

This is better, but not exactly what I was looking for... #9

kennonb opened this issue May 11, 2012 · 14 comments

Comments

@kennonb
Copy link

kennonb commented May 11, 2012

I wanted to say that this does ease some of the pain of creating new folders/files in Sublime Text 2. However, this doesn't do exactly what I was hoping for. What I'm looking for may have to be implemented by Jon himself. Not sure.

Reason why I'm posting this is just so it's out there somewhere, and this seems like a good enough place to put it.

My ideal workflow:

  • CTRL+0 -> Go into the sidebar.
  • Use keyboard nav to jump in and out of folders.
  • Use keyboard shortcuts to create files/folders based upon the selected folder level in the sidebar.

Some other advancements:

  • Auto "touch" files as they are created, so I don't have to manually save.
  • Don't create non-extension files for empty folders that are created.
  • Be able to create new folders/files when no files are open in the view.

I might think of more things, but these additions would make it a world better for me. I might take a stab at it myself, if I can get the time.

@megalithic
Copy link

yeah, i'm definitely in for this.

@skuroda
Copy link
Collaborator

skuroda commented Oct 31, 2012

I know you created this issue a while ago, but I've implemented 2/3 "advancements." I'm not quite sure what you mean by "Don't create non-extension files for empty folders that are created."

So, if you happen to see this, mind giving me an example?

@shyamsalimkumar
Copy link

Also may be a make in current/parent directory kinda functionality... For example if I were to hit Super + Alt + N from a file and then type ./file.ext it would make the file in the same directory as the file which it was opened from and not on the root folder of the project, and if it was ../file.ext it would be in the parent directory. Possible?

@skuroda
Copy link
Collaborator

skuroda commented Aug 22, 2013

You can enter a : at the beginning of the input field and it will begin at the current folder. Additionally, if you find yourself wanting the current folder more often than not, you can set the default_root setting to current. If instead you would rather . and .. act special when specifying a path, please open a new issue.

@kennonb
Copy link
Author

kennonb commented Aug 26, 2013

Not sure why I stopped getting notifications about this. I just happened to come back here, and I have to say that you did a fabulous job. Thanks for implementing those changes.

As for "Don't create non-extension files for empty folders that are created." Basically, I wanted to be able to create New Folders with this plugin as well. Best example I can give:

  • Hit CMD+OPT+N to bring up new file creation input.
  • Type in "test" without an extension.
  • Instead of creating an empty directory, it creates a blank file with no extension.

Now that I'm thinking about it, I don't know why I'd need to create a blank directory without also specifying a file to go in it. But that's what I was trying to allude to in the initial post.

Again, thanks for working on all this. It's a wonderful plugin! :)

@skuroda
Copy link
Collaborator

skuroda commented Aug 26, 2013

Not that you will ever need to create an empty directory, but if you want to, you can. You will need to add a trailing slash though.

@kennonb
Copy link
Author

kennonb commented Aug 26, 2013

👍 Thanks. It throws an error, but does create the empty folder.

@skuroda
Copy link
Collaborator

skuroda commented Aug 26, 2013

What's the error?

@kennonb
Copy link
Author

kennonb commented Aug 26, 2013

@skuroda
Copy link
Collaborator

skuroda commented Aug 26, 2013

Hmm, okay I'll try to look into that. I don't see the error. I can't recall if that's something that I addressed previously though. Can you make sure you are on the latest version. If you are cloning, the master branch is compatible with both ST2 and ST3.

@kennonb
Copy link
Author

kennonb commented Aug 27, 2013

Thanks, no problem. I'm on ST3 and I have the plugin installed using Package Control 2.0.

@skuroda
Copy link
Collaborator

skuroda commented Sep 1, 2013

Can you go to Package Control: List Packages and tell me what version number comes up (it'll just be a datetime). It's odd to me that you are getting that error. I'm having trouble reproducing it.

@kennonb
Copy link
Author

kennonb commented Sep 1, 2013

Sure. It's showing v2013.08.14.

http://d.pr/i/zjpV

@skuroda
Copy link
Collaborator

skuroda commented Sep 3, 2013

Is there any additional information in the ST console when this happens? Thanks for all the help trying to track this down.

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

4 participants