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

Restarting Terminal on OS X does not restore working directory #926

Closed
bjhomer opened this issue Jul 22, 2013 · 4 comments
Closed

Restarting Terminal on OS X does not restore working directory #926

bjhomer opened this issue Jul 22, 2013 · 4 comments
Milestone

Comments

@bjhomer
Copy link

bjhomer commented Jul 22, 2013

On OS X, turn on the setting to restore an application's windows when restarting the app. Make sure fish is your default shell. Then do the following:

  1. Open a new window in Terminal.app
  2. cd ~/Documents
  3. Cmd-Q
  4. Open Terminal.app
  5. Note that the working directory is ~, not ~/Documents

I'm running this built from brew, version 2.0.0.

@wwwjfy
Copy link
Contributor

wwwjfy commented Jul 23, 2013

JFYI, I use iTerm2, and it works fine except first tab in each window is at $HOME. I can live with that though.
Maybe it's not the shell's problem?
I didn't try, but does bash work well?

@zanchey
Copy link
Member

zanchey commented Jul 23, 2013

We don't support this yet - see #87, #906. The series of control characters is the same on both Terminal.app and gnome-terminal (thankfully).

@RSully
Copy link

RSully commented Feb 1, 2014

Noticing something like this:

  • Open Terminal.app (default shell set to fish 2.1.0, installed via homebrew)
  • In one window cd Movies/
  • In another window cd Documents/
  • Force quit terminal
  • Open terminal

Terminal opens both windows, shows some of the old session history followed by a "[Restored]", but then I am just placed in a new shell. History in each window is global.

@zanchey zanchey modified the milestones: fish 2.2.0, fish-future Jul 31, 2015
@zanchey
Copy link
Member

zanchey commented Jul 31, 2015

This is fixed in 2.2.0, hooray!

@zanchey zanchey closed this as completed Jul 31, 2015
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 18, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants