[GH-ISSUE #151] [Feature Request] Add working directory of each process to processes table #94

New issue

Closed

opened 2026-05-05 03:25:16 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 03:25:16 -06:00

Owner

Originally created by @Darxeal on GitHub (Feb 7, 2025).
Original GitHub issue: https://github.com/XuehaiPan/nvitop/issues/151

Originally assigned to: @XuehaiPan on GitHub.

Required prerequisites

I have searched the Issue Tracker that this hasn't already been reported. (comment there if it has.)
I have tried the latest version of nvitop in a new isolated virtual environment.

Motivation

With jupyter notebook processes, the COMMAND column in the processes table looks for example like this:
/home/user/miniconda3/envs/env/bin/python -Xfrozen_modules=off -m ipykernel_launcher -f /home/user/.local/share/jupyter/runtime/kernel-....json
which doesn't tell you much about which process is which. The working directory of the process could be more descriptive.

Solution

Add a "working directory" column to the Processes table. Basically like running pwdx for each process.
Can be optional.

Alternatives

No response

Additional context

No response

Originally created by @Darxeal on GitHub (Feb 7, 2025). Original GitHub issue: https://github.com/XuehaiPan/nvitop/issues/151 Originally assigned to: @XuehaiPan on GitHub. ### Required prerequisites - [x] I have searched the [Issue Tracker](https://github.com/XuehaiPan/nvitop/issues) that this hasn't already been reported. (comment there if it has.) - [ ] I have tried the latest version of nvitop in a new isolated virtual environment. ### Motivation With jupyter notebook processes, the `COMMAND` column in the processes table looks for example like this: ```/home/user/miniconda3/envs/env/bin/python -Xfrozen_modules=off -m ipykernel_launcher -f /home/user/.local/share/jupyter/runtime/kernel-....json``` which doesn't tell you much about which process is which. The working directory of the process could be more descriptive. ### Solution Add a "working directory" column to the Processes table. Basically like running `pwdx` for each process. Can be optional. ### Alternatives _No response_ ### Additional context _No response_

gitea-mirror

2026-05-05 03:25:16 -06:00

closed this issue
added the
enhancement
label

gitea-mirror commented

2026-05-05 03:25:19 -06:00

Author

Owner

@XuehaiPan commented on GitHub (Feb 8, 2025):

Hi @Darxeal, always showing the CWD in the process list will cause the column to be too long. Have you tried to select process and press the e key. You can find the process working directory with the PWD environment variable.

@XuehaiPan commented on GitHub (Feb 8, 2025): Hi @Darxeal, always showing the CWD in the process list will cause the column to be too long. Have you tried to select process and press the `e` key. You can find the process working directory with the `PWD` environment variable.

gitea-mirror commented

2026-05-05 03:25:20 -06:00

Author

Owner

@Darxeal commented on GitHub (Feb 10, 2025):

I see, that's useful, thank you.
I would still like the additional column, on a large screen there's plenty of space. But it's not necessary.

@Darxeal commented on GitHub (Feb 10, 2025): I see, that's useful, thank you. I would still like the additional column, on a large screen there's plenty of space. But it's not necessary.

gitea-mirror commented

2026-05-05 03:25:21 -06:00

Author

Owner

@XuehaiPan commented on GitHub (Feb 10, 2025):

Both CWD and COMMAND can be very long. Aligned tables may contain many whitespace and scrolling the row can be annoying. Closing this, sorry.

@XuehaiPan commented on GitHub (Feb 10, 2025): Both `CWD` and `COMMAND` can be very long. Aligned tables may contain many whitespace and scrolling the row can be annoying. Closing this, sorry.

gitea-mirror referenced this issue

2026-05-05 03:26:55 -06:00

[PR #94] [MERGED] fix(api/libnvml): fix upstream changes for process info v3 APIs on 535.104.05 driver #156