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
Tab complete is broken on macOS. On linux, you are able to expand cd d/s/p<tab> to cd documents/SAP/presentations. Not the case in macOS. Might be due to the cd alias stuff we have going on.
Accepting suggestions from the history is unintuitive. The separation between historical suggestions, and context based ones is useful, but hard to understand without an explicit explanation.
So it should certainly not offer a historical suggestion that contains a relative path if the pwd's are different.
A command might implicitly also take a relative path. npm run serve for example implicitly depends on the existence of not only a package.json in the pwd, but also the existence of package.json.scripts.serve.
Could machine learning infer these relationships?
The text was updated successfully, but these errors were encountered:
Tab complete is broken on macOS. On linux, you are able to expand cd d/s/p to cd documents/SAP/presentations. Not the case in macOS. Might be due to the cd alias stuff we have going on.
Accepting suggestions from the history is unintuitive. The separation between historical suggestions, and context based ones is useful, but hard to understand without an explicit explanation.
So it should certainly not offer a historical suggestion that contains a relative path if the pwd's are different.
A command might implicitly also take a relative path. npm run serve for example implicitly depends on the existence of not only a package.json in the pwd, but also the existence of package.json.scripts.serve.
Some thoughts
Tab complete is broken on macOS. On linux, you are able to expand
cd d/s/p
<tab>
tocd documents/SAP/presentations
. Not the case in macOS. Might be due to thecd
alias stuff we have going on.Accepting suggestions from the history is unintuitive. The separation between historical suggestions, and context based ones is useful, but hard to understand without an explicit explanation.
So it should certainly not offer a historical suggestion that contains a relative path if the pwd's are different.
A command might implicitly also take a relative path.
npm run serve
for example implicitly depends on the existence of not only apackage.json
in thepwd
, but also the existence ofpackage.json.scripts.serve
.Could machine learning infer these relationships?
The text was updated successfully, but these errors were encountered: