Command history improvements

Open
#148 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
cli

Research direction

Start by reading issue #37 and the planned cmd2 upgrade referenced here. Check whether that upgrade already provides the requested history listing and saveHistory behavior; done means both command-history capabilities are available in PyDV.

Written by the indexing model from the issue text.

Description

enhancement Medium Priority

From Tom Brunner:

Command history: If you could say “history” and see a list of your history, that could be cool. It might be interesting to say “saveHistory [m:n] filename.” to save a set of commands to a named file.

The upgrade to cmd2 will resolve this (see #37 )

Dominant language
Python
Stars
15
Forks
6
PR merge metrics
No merged PRs in 30d

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 llnl/PyDV

All issues in llnl/PyDV

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.