Vintageous mode #125

Closed
leemhenson opened this Issue Mar 24, 2014 · 7 comments

Comments

Projects
None yet
3 participants
@leemhenson

So, it looks like this issue:

#120

now prevents me (a Vintageous user) from doing things like :10 to jump to a specific line in the git-status page if I want to stage/unstage a particular file. It looks like I need to use the cursor keys/pointer to get to that line, which is pretty slow. Is there any way we can make git-status disabling of Vintageous an optional thing?

@miquella

This comment has been minimized.

Show comment
Hide comment
@miquella

miquella Apr 7, 2014

Haha, this one caught me as well. I typically use j/k to move through the status list so I can examine each file individually.

miquella commented Apr 7, 2014

Haha, this one caught me as well. I typically use j/k to move through the status list so I can examine each file individually.

@miped

This comment has been minimized.

Show comment
Hide comment
@miped

miped Feb 2, 2015

Contributor

Well this kinda leaves us stuck between a rock and a hard place. What would your suggested fix be, taking into account that from SublimeGit's side it's more a less an all-or-nothing decision to allow or disallow vintageous mode?

Contributor

miped commented Feb 2, 2015

Well this kinda leaves us stuck between a rock and a hard place. What would your suggested fix be, taking into account that from SublimeGit's side it's more a less an all-or-nothing decision to allow or disallow vintageous mode?

@miquella

This comment has been minimized.

Show comment
Hide comment
@miquella

miquella Feb 2, 2015

Would it be possible to go halfway and have a setting that allows Vintageous behaviors, but otherwise disables it?

miquella commented Feb 2, 2015

Would it be possible to go halfway and have a setting that allows Vintageous behaviors, but otherwise disables it?

@miped

This comment has been minimized.

Show comment
Hide comment
@miped

miped Feb 2, 2015

Contributor

That's my current thinking on it. Something like a git_disable_vintageous settings which defaults to true should do it trick. Then power users can just flip it.

Contributor

miped commented Feb 2, 2015

That's my current thinking on it. Something like a git_disable_vintageous settings which defaults to true should do it trick. Then power users can just flip it.

@miquella

This comment has been minimized.

Show comment
Hide comment
@miquella

miquella Feb 2, 2015

Sounds great!

miquella commented Feb 2, 2015

Sounds great!

@miped

This comment has been minimized.

Show comment
Hide comment
@miped

miped Feb 8, 2015

Contributor

Just released 1.0.34 which introduces this setting. See the default settings file.

Contributor

miped commented Feb 8, 2015

Just released 1.0.34 which introduces this setting. See the default settings file.

@miped miped closed this Feb 8, 2015

@leemhenson

This comment has been minimized.

Show comment
Hide comment

🍻

@leemhenson leemhenson referenced this issue in divmain/GitSavvy Mar 11, 2015

Closed

play nice with vintageous #65

miped added a commit that referenced this issue Feb 2, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment