remove "prev" command in 1.3

[tjwebb]

what are everyone's thoughts on this? I personally find it more confusing than helpful, and prone to off-by-one situations

[jbnicolai]

I personally like it to be quite honest 😄

I would like to further suggest implementing n - as an alias for n prev, in a similair version cd - wil change to the previous directory and git checkout - will checkout the previous branch, tag or commit.

Would a PR for this be welcome?

[tjwebb]

n - already is an alias for n rm. I'm more inclined to consider API addition/removal than a re-defining an existing command to mean something else.

[jbnicolai]

Wasn't aware of that, you're completely right that we shouldn't use - then. I would suggest even removing that command, as it's very unintuitive.

I'd leave prev though :)

[tjwebb]

I'd consider that as well. I don't have much use for aliases anyway. There shouldn't be lots of ways to do one thing, especially in such a simple tool.

[jbnicolai]

👍

[ghost]

👍

I never use prev. I would just switch to the version number. It's not like we are typing that much more to achieve the same outcome.

[maxrimue]

👍 Same over here

[ghost]

I am going to submit a PR to remove this.

I ran into an interesting case that breaks the state of n when using prev.

n 0.12.0
n 0.12.1 - prev store 0.12.0
n rm 0.12.0
n prev - script runs and nothing is copied. Active is not set to a value.
n - select comes up and nothing works. Only another call to n prev will fix it.

[tjwebb]

I think prev is weird also
On Mar 30, 2015 2:00 PM, "tedgaydos" [email protected] wrote:

I am going to submit a PR to remove this.

I ran into an interesting case that breaks the state of n when using prev.

n 0.12.0

installs 0.12.0
n 0.12.1
installs 0.12.1 and prev store 0.12.0
n rm 0.12.0
removes 0.12.0
n prev
script runs and nothing is copied. Active is not set to a value.
n
select comes up and nothing works. Only another call to n prev will fix it.

—
Reply to this email directly or view it on GitHub
#184 (comment).

[tjwebb]

This would have to constitute a new major version, though. Because semver

[knownasilya]

I use n prev, mainly for cleanup in https://github.com/Strider-CD/strider-node. Also when switching, and forgetting to check what it was before.

[ghost]

I just took a look at your project. I have to say it is very impressive. Good work.

As for the way you are using n prev, if you want leave the original environment intact, you can use n (io) use to execute under a specific node/io.js version. That way you do not have to worry about cleanup at all.

[ghost]

prev was pulled in 2.0.0.