tools
/
josh
1
1
Fork 1
Code Issues 29 Pull Requests Releases Activity

Do not store duplicates in input history #74

New Issue
Closed
opened 2019-11-12 01:18:41 +01:00 by FWDekker · 0 comments
FWDekker commented 2019-11-12 01:18:41 +01:00
Owner
Copy Link

If the user executes the same command multiple times in sequence, then only one of those instances should be stored.

If the user executes the same command multiple times in sequence, then only one of those instances should be stored.
FWDekker self-assigned this 2019-11-12 01:18:41 +01:00
FWDekker added the
enhancement
 label 2019-11-12 01:18:41 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
Labels
Clear labels   
bug

Something isn't working

  
code-quality

Code changes without behavior changes

  
documentation

Improvement of addition of code or usage documentation

  
duplicate

This issue or pull request already exists

  
enhancement

Improvement of existing feature

  
feature

New feature or request

  
flair

Updates to the README and such

  
invalid

This doesn't seem right

  
on-hold

Will not be worked on until conditions change

  
release

Adjustment to existing or future releases

  
third-party bug

Something isn't working, but it's caused by a dependency

  
tooling

Configuration of and updates to analysis and build tools

  
wontfix

This will not be worked on

No Label
bug
code-quality
documentation
duplicate
enhancement
feature
flair
invalid
on-hold
release
third-party bug
tooling
wontfix
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
FWDekker
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: tools/josh#74
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?