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

Drop support for separate console history file #678

Open
mvz opened this issue Dec 28, 2019 · 1 comment
Open

Drop support for separate console history file #678

mvz opened this issue Dec 28, 2019 · 1 comment
Milestone

Comments

@mvz
Copy link
Contributor

mvz commented Dec 28, 2019

Summary

Aruba console uses its own history file. I don't think it should.

Expected Behavior

History for aruba console should be appended to the general IRB history.

Current Behavior

Aruba console stores its history in ~/.aruba_history.

Possible Solution

Remove the code setting the relevant IRB options, as well as Aruba's configuration option.

Context & Motivation

Having this history separate makes it harder to re-use existing history from general IRB use. Other special-purpose consoles (e.g., rails console) also do not keep a separate history.

@mvz mvz added this to the 2.0.0 milestone Jan 1, 2020
@mvz mvz modified the milestones: 2.0.0, 3.0.0 Aug 1, 2021
@mvz
Copy link
Contributor Author

mvz commented Oct 2, 2021

We may even drop the whole aruba console feature, and the aruba CLI.

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

1 participant