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

mc-wrapper: don't cd to the same dir #3355

Closed
mc-butler opened this issue Dec 3, 2014 · 6 comments
Closed

mc-wrapper: don't cd to the same dir #3355

mc-butler opened this issue Dec 3, 2014 · 6 comments
Assignees
Labels
area: core Issues not related to a specific subsystem prio: low Minor problem or easily worked around
Milestone

Comments

@mc-butler
Copy link

Important

This issue was migrated from Trac:

Origin https://midnight-commander.org/ticket/3355
Reporter egmont (@egmontkob)

mc-wrapper.sh could be improved not to perform a cd if the shell is in the same directory.

This would make a subsequent "cd -" more convenient. If you don't alter the directory in mc, after exiting a "cd -" does nothing, whereas it could take you to the actual previous directory.

Note

Original attachments:

@mc-butler
Copy link
Author

Changed by egmont (@egmontkob) on Dec 3, 2014 at 16:38 UTC

Fix for sh (todo: csh needs to be fixed too)

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Jan 19, 2020 at 17:07 UTC (comment 1)

  • Status changed from new to accepted
  • Owner set to andrew_b
  • Blocked by set to #4050
  • Milestone changed from Future Releases to 4.8.25

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Jan 19, 2020 at 17:08 UTC (comment 2)

Fixed in 4050_cleanup branch.

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Feb 29, 2020 at 16:34 UTC

  • Blocked by #4050 deleted

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Feb 29, 2020 at 16:37 UTC (comment 4)

  • Status changed from accepted to testing
  • Resolution set to fixed

Fixed as [f57daa1].

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Feb 29, 2020 at 16:37 UTC (comment 5)

  • Status changed from testing to closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: core Issues not related to a specific subsystem prio: low Minor problem or easily worked around
Development

No branches or pull requests

2 participants