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

Current directory is not retained after applying update #581

Closed
chriscollinsboxuk opened this Issue Mar 14, 2016 · 5 comments

Comments

Projects
None yet
3 participants
@chriscollinsboxuk

chriscollinsboxuk commented Mar 14, 2016

Scenario:
I open ConEmu up in a specific directory.
I am prompted that a new update is available.
I confirm I would like to apply the update and restart ConEmu.

Expected behaviour:
The update is applied and ConEmu restarts in the directory I was working in previously.

Actual behaviour:
The update is applied and ConEmu restarts in a different directory.

@chriscollinsboxuk

This comment has been minimized.

Show comment
Hide comment
@chriscollinsboxuk

chriscollinsboxuk Mar 14, 2016

I've read the manual, thanks.

According to the manual, enabling the "inject ConEmuHk" feature should be enough to ensure that the current working directory is maintained for a cmd window. I already do this, but my working directory isn't retained.

I'm not talking about the default startup; as described above, the issue I'm experiencing is specific to when an update is applied.

chriscollinsboxuk commented Mar 14, 2016

I've read the manual, thanks.

According to the manual, enabling the "inject ConEmuHk" feature should be enough to ensure that the current working directory is maintained for a cmd window. I already do this, but my working directory isn't retained.

I'm not talking about the default startup; as described above, the issue I'm experiencing is specific to when an update is applied.

@Maximus5

This comment has been minimized.

Show comment
Hide comment
@Maximus5

Maximus5 Mar 14, 2016

Owner

There is no difference between "normal" restart and "restart on update".
https://conemu.github.io/en/SettingsStartup.html

Owner

Maximus5 commented Mar 14, 2016

There is no difference between "normal" restart and "restart on update".
https://conemu.github.io/en/SettingsStartup.html

@chriscollinsboxuk

This comment has been minimized.

Show comment
Hide comment
@chriscollinsboxuk

chriscollinsboxuk Mar 14, 2016

Yes, that's what I'm saying :)

When restarting after an update, the shell points at at the default location. It would be nice if it remembered the directory that was in use prior to closing.

e.g.

  • ConEmu configured to open in "C:\myDefaultDir" by default.
  • Open ConEmu in "C:\someDirectory" via explorer integration (i.e. not the default directory).
  • Prompted to update.
  • ConEmu restarts in "C:\myDefaultDir", when it would be nice if it actually opened "C:\someDirectory".

I don't need it to remember the last directory that was in use all the time, as that is not useful to me - just specifically in the case of updates. As you release so many updates (which is great!), it's a minor annoyance having to close down the new ConEmu window that is restarted every day as it is in the wrong directory.

chriscollinsboxuk commented Mar 14, 2016

Yes, that's what I'm saying :)

When restarting after an update, the shell points at at the default location. It would be nice if it remembered the directory that was in use prior to closing.

e.g.

  • ConEmu configured to open in "C:\myDefaultDir" by default.
  • Open ConEmu in "C:\someDirectory" via explorer integration (i.e. not the default directory).
  • Prompted to update.
  • ConEmu restarts in "C:\myDefaultDir", when it would be nice if it actually opened "C:\someDirectory".

I don't need it to remember the last directory that was in use all the time, as that is not useful to me - just specifically in the case of updates. As you release so many updates (which is great!), it's a minor annoyance having to close down the new ConEmu window that is restarted every day as it is in the wrong directory.

Maximus5 added a commit that referenced this issue Mar 16, 2016

@chriscollins

This comment has been minimized.

Show comment
Hide comment
@chriscollins

chriscollins Mar 30, 2016

Many thanks for this change, I noticed it this morning. Much appreciated 👍

chriscollins commented Mar 30, 2016

Many thanks for this change, I noticed it this morning. Much appreciated 👍

@Maximus5 Maximus5 closed this Mar 30, 2016

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