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

Open
#9 14 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

No files, tests, or implementation entry points are named. Begin by reviewing the Sublime Text plugin's sidebar and file/folder creation behavior, then determine which of the listed workflow improvements are in scope. Done would require an agreed subset of the requested keyboard navigation and creation behavior, with the additional empty-folder and unsaved-view cases addressed.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Python
Stars
832
Forks
96
Avg merge
1m
Merged PRs (30d)
5

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SublimeText/AdvancedNewFile

All issues in SublimeText/AdvancedNewFile

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.