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

History in projectile-run-project lists all duplicates #1654

Closed
doctordesh opened this issue Mar 3, 2021 · 2 comments
Closed

History in projectile-run-project lists all duplicates #1654

doctordesh opened this issue Mar 3, 2021 · 2 comments

Comments

@doctordesh
Copy link

doctordesh commented Mar 3, 2021

(disclaimer, I don't know if this is a bug or intentional behaviour, but since this was a bug template I used it)

Expected behavior

  • Given a history of different commands run with projectile-run-project, where some commands have been used multiple times in a row (like: <cmd1>, <cmd1>, <cmd1>, <cmd2>, <cmd1>, <cmd1> ...)
  • When using M-p and M-n to move in the history
  • Then projectile should only move between "unique" entries and ignores the duplicates

Informal example

I made 1 call to do go mod vendor then ~15 calls to go run main.go. I had to use M-p 15 times to get back to go mod vendor

Actual behavior

Projectile keeps all the commands in the history, regardless of uniqueness.

Steps to reproduce the problem

  • Run <cmd1> 1 time
  • Run <cmd2> 10 times
  • Use M-p 10 times to move up to

Environment & Version information

Projectile version information

Projectile version: 20210104.1216

Emacs version

27.1

Operating system

macOS

@bbatsov
Copy link
Owner

bbatsov commented Apr 7, 2021

Projectile simply delegates to complilation-mode for the command execution. Perhaps there's some way to instruct it to keep only unique commands in its history.

@stale
Copy link

stale bot commented Apr 16, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contribution and understanding!

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

No branches or pull requests

2 participants