Hi,
2018/8/24 Fri 1:19:18 UTC+9 Lifepillar wrote:
> On 23/08/2018 15:28, Jason Franklin wrote:
> > The documentation under term_start() was recently updated
> > to include this option.
>
> So, I have likely searched the help in a version without your patch,
> which, has led me to believe that
On 23/08/2018 15:28, Jason Franklin wrote:
The documentation under term_start() was recently updated
to include this option.
So, I have likely searched the help in a version without your patch,
which, has led me to believe that "cwd" was not supported.
Thanks for letting me know!
Life.
--
--
The documentation under term_start() was recently updated
to include this option. See my message below.
https://groups.google.com/forum/#!topic/vim_dev/WAFS5NrSrB4
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
On 22/08/2018 21:06, Bram Moolenaar wrote:
Currently, terminal jobs are always started in :pwd, AFAICT.
Is there a reason why the "cwd" option from job_start() is not inherited
by term_start()?
I though this was in the todo list, but I can't find it now.
Ah, it's implemented already and
> Currently, terminal jobs are always started in :pwd, AFAICT.
> Is there a reason why the "cwd" option from job_start() is not inherited
> by term_start()?
I though this was in the todo list, but I can't find it now.
> What is the recommended way to start a terminal job in a given
> working
Currently, terminal jobs are always started in :pwd, AFAICT.
Is there a reason why the "cwd" option from job_start() is not inherited
by term_start()?
What is the recommended way to start a terminal job in a given
working directory?
Thanks,
Life.
--
--
You received this message from the
