Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

how to inherit father terminal bash env

Open
#655 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
bash, lua, neovim
Domain
cli, tooling

Research direction

Start with plenary.nvim/lua/plenary/job.lua around line 108 and review the Job:new invocation shown in the issue, especially vim.fn.environ(), env, command, and cwd. Reproduce the bitbake launch from Neovim and compare it with the working terminal environment; done means the job can locate and run bitbake without the reported executable-not-found error.

Written by the indexing model from the issue text.

Description

i use code:
-- Get the current environment and modify it if needed
local myenv = vim.fn.environ()
-- Use plenary.job to capture output
local Job = require('plenary.job')
Job:new({
command = 'bitbake ',
args = { foldname },
cwd = project_root,
env = myenv, -- Inherit and extend the current environment
on_exit = function(j, return_val)
-- Send output to Quickfix
vim.fn.setqflist({}, ' ', {
title = 'Bitbake Output',
lines = j:result(),
})
-- Open Quickfix window
vim.cmd('botright copen 6')
end,
}):start()

run result:
E5108: Error executing lua: .../site/pack/packer/start/plenary.nvim/lua/plenary/job.lua:108: bitbake : Executable not found

the bitbake command is load in the terminal; how can i fix this problem

Dominant language
Lua
Stars
3.5k
Forks
340
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nvim-lua/plenary.nvim

All issues in nvim-lua/plenary.nvim

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.