You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I launch emacs with ESS via emacs -f R from the command line, and I'm sure it always used to offer the current shell folder as the "R starting project directory" - but now (probably since I reinstalled from github) it seems to look at if the current shell folder is under a git repository and offer that as the starting project directory.
For example with this structure:
fnord
├── bar
├── baz
│ └── .git
└── .git
starting from fnord offers that as the starting R directory, as does starting in fnord/bar (because that folder is under the fnord/.git repo, but starting in fnord/baz tries to start there since its a different repo.
Basically I'd like emacs -f R to start where I started it from.
I can't see this documented (although maybe I'm looking at the docs for the wrong branch or something) and if it can be switched off that would be great.
The text was updated successfully, but these errors were encountered:
We now start in project-current. But see inferior-ess--get-startup-directory, there's some legacy options like ess-startup-directory-function that might be useful for you to recover the original behaviour.
I launch emacs with ESS via
emacs -f R
from the command line, and I'm sure it always used to offer the current shell folder as the "R starting project directory" - but now (probably since I reinstalled from github) it seems to look at if the current shell folder is under a git repository and offer that as the starting project directory.For example with this structure:
starting from
fnord
offers that as the starting R directory, as does starting infnord/bar
(because that folder is under thefnord/.git
repo, but starting infnord/baz
tries to start there since its a different repo.Basically I'd like
emacs -f R
to start where I started it from.I can't see this documented (although maybe I'm looking at the docs for the wrong branch or something) and if it can be switched off that would be great.
The text was updated successfully, but these errors were encountered: